03-February-2026 Below you will find a collection of news published yesterday. This news consists of Microsoft’s Roadmap when it is updated it will be below with items. Then there will be a section with the message center, if there is anything new there, this will be automatically included. And it contains a piece from blogs that I follow myself and would like to share with you. If I miss something in the blogs that do have an RSS feed, please let me know.
This entire post was automated via Microsoft Flow
have fun reading!
Office 365 Roadmap Updated: 2026-02-02
Additions : 0
Updates : 1
More Details At: www.roadmapwatch.com
| Updated Features | Current Status | Update Type | ||
|---|---|---|---|---|
| Microsoft Copilot (Microsoft365): Graph API – Copilot for Microsoft 365 usage | Launched | Title |
Office 365 Roadmap Updated: 2026-02-03
Additions : 3
Updates : 13
More Details At: www.roadmapwatch.com
Items from the MessageCenter in Microsoft 365
| (Updated) DNS Provisioning ChangeCategory:Exchange OnlineNummer:MC1048624Status:planForChange | Updated February 2, 2026: We have updated the timeline. Thank you for your patience. We’re making some changes to DNS provisioning of A records for all new Accepted Domains provisioned after July 1st, 2026 (previously February 1st). Between early and late July 2026 (previously February), we will gradually switch provisioning of all A records for new Accepted Domains into the new subdomains under mx.microsoft. We are doing this to reduce the friction of adopting DNSSEC in the long run. DNSSEC is a set of extensions to DNS that provides cryptographic verification of DNS records, preventing DNS spoofing and adversary-in-the-middle attacks to DNS. [How this will affect your organization:] After July 1, 2026 (previously February 1), all A records for new Accepted Domains will be provisioned into the new subdomains under mx.microsoft. July 1, 2026 (previously February 1) if not secured with DNSSEC at the domain level (ex. contoso.com), then DNS resolution will work as usual. If an Accepted Domain you add to the EAC after July 1, 2026 (previously February 1) is secured with DNSSEC, then DNSSEC will extend to the mx.microsoft DNS record automatically and you will get the benefits of DNSSEC without having to take any further action. Any issues with DNSSEC can be addressed by disabling DNSSEC for the Accepted Domain (ex. contoso.com) via your DNS provider. [What you need to do to prepare:] If you have any automation in place, for example in workflows for Domain Setup, for MX record creation that expects A records for newly provisioned Accepted Domains to be provisioned in mail.protection.outlook.com, this automation needs to be updated by July 1, 2026 (previously February 1) to use List serviceConfigurationRecords Graph API (List serviceConfigurationRecords). Use List serviceConfigurationRecords to retrieve the mailExchange value for your MX record. After July 1, 2026 (previously February 1), List serviceConfigurationRecords Graph API will be the only source of truth for your Accepted Domains’ MX record value. You will not be able to rely on the Accepted Domain’s A record being provisioned in mail.protection.outlook.com after July 1, 2026 (previously February 1). If you are using automation that expects the record to end with mail.protection.outlook.com, when you add a new Accepted Domain to the Exchange Admin Center after July 1, 2026 (previously February 1), mail flow may not work upon initial configuration and you will have to update your MX record to match what the Exchange Admin Center says for the domain or use the mailExchange value returned by List serviceConfigurationRecords Graph API. If you expect this change to cause any issues for your organization, please share that feedback. |
| (Updated) New Tools feature coming to the Microsoft Copilot Chat prompt boxCategory:Microsoft 365 suite Microsoft Copilot (Microsoft 365)Nummer:MC1122153Status:planForChange | Updated February 2, 2026: We have updated the timeline. Thank you for your patience. Beginning in October, we’re introducing a new Tools feature in the Copilot Chat prompt box. Tools acts as a lightweight entry point into high-value, task-specific Copilot features and capabilities directly from the prompt box. By selecting Tools, users get a menu where they can easily discover and trigger the right Copilot feature or capability for their current task, while also providing consistent interactions across tools. Based on the user’s license, Tools provides easy access to features and capabilities like Researcher, Analyst, Pages, and image generation. This message is associated with Microsoft 365 Roadmap 497298. When this will happen General Availability (Worldwide): We will begin rollout in October 2025 (previously late September 2025) and expect to complete by end of February 2026 (previously end of January). How this affects your organization Once this update is rolled out, users will see a new Tools button in the Copilot Chat prompt box. Selecting this button opens a menu of AI-powered features tailored to the user’s license. This enhancement improves discoverability and usability of Copilot capabilities, helping users complete tasks more efficiently. This feature is on by default and does not require admin configuration. What you can do to prepare No admin action is required. However, you may want to:
Compliance considerations No compliance considerations identified, review as appropriate for your organization. |
| (Updated) Microsoft Copilot Analytics: Data export public preview for Copilot metrics in the Copilot dashboardCategory:Microsoft Viva Microsoft Copilot (Microsoft 365)Nummer:MC1173208Status:stayInformed | Updated February 2, 2026: We have updated the timeline. This post has also been updated to remind customers that this feature is default-on for Copilot Dashboard users with full company-level data access. The export output remains de-identified, with each user represented by a hashed ID. Please review and take any actions as appropriate for your organization. Thank you for your patience. This MC post is associated with Roadmap ID 500872. [Introduction:] To support deeper analysis of Copilot adoption, Microsoft is introducing a new export capability in the Copilot Dashboard. This feature allows dashboard users with company-level access to download de-identified Copilot usage metrics, aggregated by user and week, from the past six months. Organizations can use this data to track adoption trends, optimize licensing, and support AI transformation strategies. This feature requires at least 50 Microsoft 365 Copilot licenses and applies to the Viva Insights web app. [When this will happen:]
[How this affects your organization:] Who is affected: Copilot Dashboard users with full company-level data access, including senior leaders (as identified in Entra ID), admin-assigned company-level users, delegates with company-level access, as well as global analysts and admins. Note: Group managers with data access limited to their own teams will not have access to this feature. What will happen:
Screenshot 1 – View of the new Microsoft Copilot dashboard:
Screenshot 2 – Example of output:
[What you can do to prepare:]
Learn more: Microsoft Viva Feature access management | Microsoft Learn Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn [Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| (Updated) Microsoft PowerPoint: “Reuse Slides” feature will retire starting 2026Category:Microsoft 365 appsNummer:MC1179161Status:stayInformed | Updated February 2, 2026: We have updated the content. Thank you for your patience. [Introduction] Starting in January 2026, Microsoft will move back to legacy behavior of the Reuse Slides feature from PowerPoint for Windows and Mac desktops, only allowing users to reuse slides from local files. This change is part of ongoing efforts to simplify the PowerPoint experience and remove features that duplicate existing capabilities. [When this will happen:]
[How this affects your organization:]
[What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| Microsoft SharePoint: Retirement of IDCRL authentication protocol and enforcement of OpenID Connect and OAuth protocolsCategory:SharePoint Online Microsoft OneDriveNummer:MC1184649Status:planForChange | Updated February 2, 2026: We are updating this post as a reminder. Thank you for your patience. [Introduction:] As part of the Microsoft Secure Future Initiative (SFI) and in alignment with the “Secure by Default” principle, we’re retiring the legacy IDCRL (Identity Client Run Time Library) authentication protocol in SharePoint Online and OneDrive for Business. This change helps strengthen your organization’s security posture by enforcing modern authentication standards—OpenID Connect and OAuth—which reduce exposure to outdated and vulnerable authentication methods. [When this will happen:]
[How this affects your organization:] Who is affected:
[What you can do to prepare:] We recommend migrating from legacy authentication protocols to modern authentication as soon as possible. To prepare for this retirement:
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| (Updated) Microsoft 365 Copilot: Email triage with pin, flag, archive, and mark readCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1193695Status:stayInformed | Updated February 2, 2026: We have added a link to a support article. Thank you for your patience. [Introduction:] Managing email just got easier. Microsoft 365 Copilot now supports natural language commands to help users pin or unpin important messages, flag or unflag items, mark tasks complete, archive clutter, and mark emails as read or unread. This enhancement is designed to streamline inbox management and help users stay focused on what matters most. A Microsoft 365 Copilot license is required to access this feature. [When this will happen:]
[How this affects your organization:] Who is affected: Users with Microsoft 365 and Copilot licenses who use Outlook for email management. What will happen:
[What you can do to prepare:]
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| Microsoft Purview DLM: Retirement of SharePoint online information management and in-place records management featuresCategory:SharePoint OnlineNummer:MC1211579Status:planForChange | Updated February 2, 2026: We have updated the content. Thank you for your patience. [Introduction] We’re retiring several legacy SharePoint Online features to streamline compliance and data lifecycle management. Starting April 2026, support for the following features will no longer be provided even though the feature will continue to work.
[When this will happen:] Support for the features will no longer be provided starting April 2026[How this affects your organization:] Who is affected: Organizations using Information Management Policies, In-Place Records Management, or related deletion policies in SharePoint Online. What will happen:
[What you can do to prepare:] Microsoft won’t automatically migrate your older information management and SharePoint records management features in SharePoint Online. If you choose not to migrate to supported features, the older features will no longer be supported. Between now and April 2026, you have the flexibility to migrate your scenarios on your own schedule. To prepare:
[Compliance considerations:] No compliance considerations identified, review as appropriate for your organization. |
| (Updated) Microsoft 365 Copilot: Create and view Outlook rulesCategory:Microsoft Copilot (Microsoft 365)Nummer:MC1223821Status:stayInformed | Updated February 2, 2026: We have updated the timeline. Thank you for your patience. [Introduction] Outlook is adding new Microsoft 365 Copilot capabilities that let users create and view Inbox rules using natural language. This update helps users stay organized more efficiently by allowing them to ask Copilot to set up new rules or list existing rules directly in chat, without navigating Outlook settings. A Microsoft 365 Copilot license is required to access this new feature. [When this will happen] General Availability (Worldwide): We began rolling out in early February 2026 (previously late January) and expect to complete by mid-March 2026 (previously early March). [How this affects your organization] Who is affected: Users who have access to Microsoft 365 Copilot in Outlook. What will happen:
[What you can do to prepare] No action is required from administrators. If your helpdesk or documentation references Outlook rule creation, you may wish to update it to reflect natural‑language rule management through Copilot. [Compliance considerations] No compliance considerations identified. Review as appropriate for your organization. |
| Microsoft Power Automate – Use Power Platform Environment variables in desktop flowsCategory:Microsoft Power AutomateNummer:MC1226018Status:stayInformed | We are announcing the ability to retrieve Power Platform Environment variables directly through desktop flows in Microsoft Power Automate. This feature will reach general availability on February 28, 2026. How does this affect me? Makers will be able to retrieve Power Platform Environment variables directly within their desktop flows, eliminating the need to pass them as inputs to the flow. What action do I need to take? This message is for awareness, and no action is required. |
| Dynamics 365 Customer Service – Edit schedule bookings with drag and dropCategory:Dynamics 365 AppsNummer:MC1226029Status:stayInformed | We are announcing the ability to edit agent schedule bookings using drag-and-drop interactions in Dynamics 365 Customer Service. This feature will reach general availability on February 16, 2026. How does this affect me? Supervisors will be able to adjust agent bookings directly within the “Schedule People” view, using intuitive drag-and-drop functionality. This update reduces the time and effort needed to modify schedules and allows for faster, more efficient updates during both planning and intraday operations. What action do I need to take? To use this feature, you must install the Workforce Management for Customer Service package from the Power Platform admin center. |
| Dynamics 365 Customer Service – Generate long-term forecasts up to three yearsCategory:Dynamics 365 AppsNummer:MC1226042Status:stayInformed | We are announcing the ability to generate long-term forecasts of up to three years in Dynamics 365 Customer Service. This feature will reach general availability on February 27, 2026. How does this affect me? Supervisors will be able to create forecast scenarios with durations up to 1095 days (three years), extending the previous 6-month limitation. This enhancement supports more accurate long-term workforce planning, budgeting, and strategic decision-making with daily granularity predictions. It enables improved visibility into demand for annual and multi-year planning. What action do I need to take? To use this feature, you must install the Workforce Management for Customer Service package from the Power Platform admin center. |
| Dynamics 365 Customer Service – Generate short‑term forecast duration up to one yearCategory:Dynamics 365 AppsNummer:MC1226053Status:stayInformed | We are announcing the ability to generate short‑term forecast scenarios with a duration of up to 365 days (one year) in Dynamics 365 Customer Service. This feature will reach general availability on February 27, 2026. How does this affect me? This enhancement removes the previous 6-week short-term forecasting limitation, allowing supervisors to create forecasts for staffing needs up to one year in advance. This will help improve long-term planning for operational demand. What action do I need to take? To use this feature, you must install the Workforce Management for Customer Service package from the Power Platform admin center. |
| (Updated) SharePoint 2013 workflow retirementCategory:SharePoint Online Microsoft OneDriveNummer:MC542767Status:planForChange | Updated February 2, 2026: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 2 months from now (April 2, 2026). Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond. With the continued investment in Power Automate as the universal solution to workflow, Microsoft is retiring SharePoint 2013 workflows. [When this will happen:]
[How this will affect your organization] If your organization still uses SharePoint 2013 workflows, they will no longer function after April 2nd, 2026. We recommend customers to move to Power Automate or other supported solutions. [What you need to do to prepare] You will want to notify your users, workflow developers and site owners. Update your user training and prepare your help desk. For admins
Note: There will not be an option to extend SharePoint 2013 workflow beyond April 2nd 2026.
Learn more:
|
| (Updated) Azure ACS retirement in Microsoft 365Category:SharePoint OnlineNummer:MC693863Status:planForChange | Updated February 2, 2026: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 2 months from now (April 2, 2026). Since the first use of Azure Access Control Services (ACS) by SharePoint in 2013, Microsoft has evolved the authorization and authentication options for SharePoint Online via Microsoft Entra ID (a.k.a. Azure AD). Using Microsoft Entra ID as auth platform for your SharePoint Online customizations will provide your applications the most secure, compliant and future proof model. With our continued investment in Microsoft Entra ID, Microsoft is retiring the use of Azure ACS as auth platform for SharePoint Online. [Key Points:]
[How this will affect your organization] If your organization still uses Azure ACS to grant custom developed or third party applications access to SharePoint Online, they will no longer have access after April 2nd, 2026. We recommend customers to update their customizations to use Microsoft Entra ID and ask their solution vendors to do the same. [What you need to do to prepare] You will want to notify your Azure ACS users and developers. Update your user training and prepare your help desk. For admins
Learn more
|
| (Updated) SharePoint Add-In retirement in Microsoft 365Category:SharePoint OnlineNummer:MC693865Status:planForChange | Updated February 2, 2026: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 2 months from now (April 2, 2026). Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint extensibility using SharePoint Framework (SPFx) enabling you to write applications that can be used in Microsoft SharePoint, Viva Connections and Microsoft Teams. With our continued investment in SharePoint Framework, Microsoft is retiring SharePoint Add-Ins. [Key Points:]
[How this will affect your organization:] If your organization still uses SharePoint Add-Ins, they will no longer function after April 2nd, 2026. We recommend customers to port their customizations to SharePoint Framework (SPFx) and ask their solution vendors for updated solutions. [What you need to do to prepare] You will want to notify your Add-In users and developers. Update your user training and prepare your help desk. For admins
New: How to disable SharePoint Add-Ins on your tenant Admins can disable SharePoint Add-Ins with the Set-SPOTenant SharePoint Management Shell PowerShell command.
After SharePoint Add-Ins are disabled, users will not be able to add SharePoint Add-Ins to their sites, and admins cannot add new SharePoint Add-Ins to the tenant and site collection app catalogs. SharePoint Add-Ins already added to sites will stay available and can still be used by the site’s users. New: SharePoint Add-Ins will not be available from the public marketplace After July 1, 2024, users browsing the public marketplace (AppSource) will see SharePoint Add-In, but if they select Get it now, a message will explain that SharePoint Add-Ins are retired and cannot be added. If you still require a specific SharePoint Add-In, contact the Add-In creator to understand the possible options. Learn more
|
| (Updated) SharePoint Framework domain isolated web parts retirementCategory:SharePoint OnlineNummer:MC792601Status:planForChange | Updated February 2, 2026: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 2 months from now (April 2, 2026). After careful consideration and extensive review of usage data and feedback Microsoft has decided to retire the domain isolated web parts feature in the SharePoint Framework (SPFx).
[When will this happen:]
[How this will affect your organization:] If your organization still uses domain isolated web parts, after the change has rolled out these will render an error message and stop functioning. We recommend customers to update the impacted web parts as regular web parts and redeploy them. [What you need to do to prepare:] To understand whether you have installed domain isolated web parts and granted permissions you can verify if the SharePoint admin center API access page contains permissions listed under the Isolated grouping. If you see permissions listed under Isolated then you can use the instructions described on the domain isolated web part retirement page to discover the solutions, their domain isolated web parts and where those web parts are used. This resource will also contain the needed steps to update the web parts to not use domain isolation. Note: There will not be an option to extend domain isolated web parts beyond April 2, 2026. Learn more:
|
