from 09/29/2025 to 10/05/2025
33 Office 365 Message Center Items were changed and
37 Office 365 Message Center Items were added
Please note: Only common Message Center messages are in this list you should always check your Message Center for additional messages
Subscibe to cloudscout.one Enterprise plan to get individual reports for your Office 365 tenant
Changes
MC Action Required By changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1048624 | (Updated) DNS Provisioning Change | 07/01/2025 09:00:00 | 2026-02-01T08:00:00Z | 02/01/2026 |
MC End Time changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1025217 | (Updated) Microsoft Teams: In channels, the "Shared" tab (formerly the "Files" tab) will have new capabilities | 11/10/2025 08:00:00 | 2026-01-05T08:00:00Z | N/A |
| MC1037767 | (Updated) Microsoft Teams: Share Teams apps and agents from their profile or the Teams side panel | 01/05/2026 08:00:00 | 2026-02-02T08:00:00Z | N/A |
| MC1045227 | (Updated) Microsoft Viva Connections cards in SharePoint agents | 12/08/2025 08:00:00 | 2025-10-06T09:00:00Z | N/A |
| MC1085574 | (Updated) Copilot Dashboard: Updated meeting metrics for Intelligent Recap | 01/05/2026 08:00:00 | 2026-02-02T08:00:00Z | N/A |
| MC1104306 | (Updated) Microsoft Teams: Users can save chats and channel messages for later | 10/25/2025 09:00:00 | 2025-12-01T08:00:00Z | N/A |
| MC1127233 | (Updated) Feature retirement: deploy Shifts to your frontline teams at scale in Teams Admin Center | 10/27/2025 08:00:00 | 2025-11-03T08:00:00Z | N/A |
| MC1129716 | (Updated) Microsoft Outlook Mobile adds support for DLP policy tips and enforcement | 10/04/2025 09:00:00 | 2026-03-31T09:00:00Z | N/A |
| MC1130385 | (Updated) Retirement of inline SVG images in Microsoft Outlook | 10/27/2025 08:00:00 | 2025-12-01T08:00:00Z | N/A |
| MC1134174 | (Updated) Outlook Mobile for iOS and Android: Draft messages now minimize automatically when closed | 04/02/2026 09:00:00 | 2025-12-08T08:00:00Z | N/A |
| MC1142620 | Microsoft Defender Core Service coming to Windows Server 2012 R2 and Windows Server 2016 | 10/29/2025 08:00:00 | 2025-11-10T08:00:00Z | N/A |
| MC1143280 | (Updated) Microsoft Copilot dashboard (in Viva Insights): Adoption metrics for Microsoft 365 Copilot Chat | 03/24/2026 09:00:00 | 2026-02-02T09:00:00Z | N/A |
| MC1146822 | (Updated) Microsoft Viva: Copilot Analytics - Unified Exclusion list | 11/08/2025 09:00:00 | 2025-12-08T09:00:00Z | N/A |
| MC796790 | Update: Microsoft 365 and Microsoft Teams: Unified management of Teams apps in Teams, Outlook, and the Microsoft 365 app | 11/30/2026 08:00:00 | 2026-12-28T08:00:00Z | N/A |
| MC921752 | (Updated) Retirement of the SharePoint SendEmail API | 11/24/2025 09:00:00 | 2025-12-01T09:00:00Z | N/A |
| MC981462 | (Updated) Multiple account access to Copilot in Microsoft 365 desktop and mobile apps | 08/18/2025 09:00:00 | 2025-12-31T08:00:00Z | N/A |
MC How Affect changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1048624 | (Updated) DNS Provisioning Change | After October 1st, 2025 (previously August 1st), all A records for new Accepted Domains will be provisioned into the new subdomains under mx.microsoft. DNS resolution will safely fallback to "plain" DNS if a domain is not DNSSEC enabled. If an Accepted Domain you add to the Exchange Admin Center after October 1st (previously August 1st) is 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 October 1st (previously August 1st) 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. |
After February 1st, 2025 (previously October 1st), all A records for new Accepted Domains will be provisioned into the new subdomains under mx.microsoft.February 1st, 2025 (previously October 1st) is 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 February 1st, 2025 (previously October 1st) 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. | 02/01/2026 |
| MC1117814 | (Updated) Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft | The sender domain for Viva Engage emails will change as follows: From @yammer.com to @engage.mail.microsoft for U.S. and global regions. From @eu.yammer.com to @eu.engage.mail.microsoft for European regions. These new domains are secured with industry-standard authentication protocols (e.g., SPF) to help prevent spoofing and ensure reliable delivery. To enhance security and reduce cross-tenant spam, sender addresses will now include a tenant-specific prefix. You may see emails from: noreply_tenant@engage.mail.microsoft (digests and delegate notifications) notifications_tenant@engage.mail.microsoft (community, storyline, and activity notifications) |
The sender domain for Viva Engage emails will change as follows: From @yammer.com to @engage.mail.microsoft for U.S. and global regions. From @eu.yammer.com to @eu.engage.mail.microsoft for European regions. These new domains are secured with industry-standard authentication protocols (e.g., SPF) to help prevent spoofing and ensure reliable delivery. To enhance security and reduce cross-tenant spam, sender addresses will now include a tenant-specific prefix. You may see emails from: noreply_tenant@engage.mail.microsoft (digests, delegate, leader identification, community expert and other notifications) notifications_tenant@engage.mail.microsoft (community, storyline, and activity notifications) announcements_tenant@engage.mail.microsoft (leadership announcements) These changes apply to all Viva Engage tenants, regardless of license tier (e.g., Viva P1, P2), and affect all Viva Engage emails, including notifications, announcements, and digests. Third-party integrations (e.g., journaling, archiving, or routing systems) that rely on the @yammer.com domain for classification or authentication may be impacted. Any such configurations should be reviewed and updated to recognize the new domains. An example of a new Viva Engage email notification sent from the updated @engage.mail.microsoft domain |
N/A |
| MC1148543 | (Updated) Microsoft Teams: Collaborative Notes in Chats | Users will see a new Notes tab in group chats, allowing them to create and collaborate on Loop components such as agendas and action items. These components are editable inline, supporting synchronous collaboration directly within Teams. This feature is on by default for all tenants. Users do not need to install anything to begin using it. What you can do to prepare You can manage this feature via the Teams Admin Center. If desired, Collaborative Notes can be disabled at the tenant level. Review internal documentation and training materials to ensure users are aware of the new Notes tab and its capabilities. Compliance considerations No compliance considerations identified, review as appropriate for your organization. |
Users will see a new Notes tab in group chats, allowing them to create and collaborate on Loop components such as agendas and action items. These components are editable inline, supporting synchronous collaboration directly within Teams. This feature is on by default for all tenants. Users do not need to install anything to begin using it. What you can do to prepare You can manage this feature via the Teams Admin Center. If desired, Collaborative Notes can be disabled at the tenant level. Review internal documentation and training materials to ensure users are aware of the new Notes tab and its capabilities. Admins can manage the feature via the Teams Admin Center under: Messaging → Messaging Settings → Messaging Notes Alternatively, it can be configured using the PowerShell cmdlet: Set-CsTeamsMessagingConfiguration Compliance considerations No compliance considerations identified, review as appropriate for your organization. |
N/A |
| MC1156359 | (Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online | Who is affected: Organizations currently using the Visualize the List or Visualize the Library feature in SharePoint Online. What will happen: Users will no longer be able to create new reports directly from SharePoint lists or libraries using the legacy integration. Previously published reports created using this integration will no longer be accessible. The Export to Power BI feature and Power BI Desktop connectivity remain supported and unchanged. What you can do to prepare: No admin action is required. However, we recommend the following steps: Notify users who rely on the Visualize the List or Visualize the Library feature. Update internal documentation to reflect the retirement and guide users to supported alternatives. Share these resources with users: Export to Power BI from SharePoint list Create a report on a SharePoint list in Power BI Desktop Learn more: Deprecation of Power BI Integration within SharePoint Lists and Libraries | Microsoft Power BI Blog | Microsoft Power BI |
Who is affected: Organizations currently using the Visualize the List or Visualize the Library feature in SharePoint Online. What will happen: Users will no longer be able to create new reports directly from SharePoint lists or libraries using the legacy integration. Previously published reports created using this integration will no longer be accessible. The Export to Power BI feature and Power BI Desktop connectivity remain supported and unchanged. What you can do to prepare: No admin action is required. However, we recommend the following steps: Notify users who rely on the Visualize the List or Visualize the Library feature. Update internal documentation to reflect the retirement and guide users to supported alternatives. Inform users that they can view the list of published reports directly from the same Integrate menu of the list or library. More information in: Create a report quickly from a SharePoint list or library in the Power BI service - Power BI | Microsoft Learn Share these resources with users: Export to Power BI from SharePoint list: Create a semantic model from a SharePoint List - Power BI | Microsoft Learn Create a report on a SharePoint list in Power BI Desktop: Create a report on a SharePoint List in Power BI Desktop - Power BI | Microsoft Learn |
N/A |
| MC1162288 | (Updated) Microsoft Outlook: Declarative Agents in Copilot Chat coming to classic Outlook for Windows | Who is affected: Organizations using classic Outlook for Windows with Microsoft 365 Copilot Chat Admins managing Copilot extensibility and agent deployment What will happen: Declarative Agents will be available in Copilot Chat within classic Outlook for Windows Users will see a right-side panel in Outlook showing: Agents previously installed by the user Agents deployed by the admin Entry points to browse agents in the app store Option to create a new agent Declarative Agents in Copilot Chat are enabled by default for Microsoft 365 tenants with Copilot licenses No admin opt-in is required to use agents in Copilot Chat Advanced agent capabilities (access to SharePoint or Graph connectors) require explicit admin opt-in and billing setup Admins can manage agents through the Integrated apps section of the Microsoft 365 admin center, including: Enabling or disabling Declarative Agents for the organization Assigning access to specific users or groups Blocking or removing agents from the organizational catalog Managing agent visibility and availability Licensing tiers: Copilot Chat (Mainline): Requires a Microsoft 365 Copilot license. Users get full access to Declarative Agents, including those integrated with plugins, enterprise connectors, and advanced orchestration features Copilot Chat Starter: Designed for non-AI SKU users (users without the Copilot license). These users can still access Copilot Chat and build knowledge-only Declarative Agents, but with limited capabilities |
Who is affected: Organizations using classic Outlook for Windows with Microsoft 365 Copilot Chat Admins managing Copilot extensibility and agent deployment What will happen: Declarative Agents will be available in Copilot Chat within classic Outlook for Windows Users will see a right-side panel in Outlook showing: Agents previously installed by the user Agents deployed by the admin Entry points to browse agents in the app store Option to create a new agent Declarative Agents in Copilot Chat are enabled by default for Microsoft 365 tenants with Copilot licenses No admin opt-in is required to use agents in Copilot Chat Advanced agent capabilities (access to SharePoint or Graph connectors) require explicit admin opt-in and billing setup Admins can manage agents through the Integrated apps section of the Microsoft 365 admin center, including: Enabling or disabling Declarative Agents for the organization Assigning access to specific users or groups Blocking or removing agents from the organizational catalog Managing agent visibility and availability Licensing tiers: Microsoft 365 Copilot: Requires a Microsoft 365 Copilot license. Users get full access to Declarative Agents, including those integrated with plugins, enterprise connectors, and advanced orchestration features Copilot Chat: Designed for users without the Copilot license. These users can still access Copilot Chat and build knowledge-only Declarative Agents, but with limited capabilities |
N/A |
| MC796790 | Update: Microsoft 365 and Microsoft Teams: Unified management of Teams apps in Teams, Outlook, and the Microsoft 365 app | Before this rollout, managing Teams apps that work in Outlook and the Microsoft 365 app was fragmented between the Integrated apps page in the Microsoft 365 admin center for Outlook and the Microsoft 365 app, and the Teams admin center for Teams. This sometimes resulted in different settings for the same app in the two admin centers. With Unified agent app management, you will be able to manage apps on the Integrated apps page in the Microsoft 365 admin center or in the Teams admin center, and any changes made in either admin center will synchronize. What you can expect: You'll gain a consolidated view of agent and Microsoft 365 app availability across both Microsoft 365 and Teams admin centers. Changes made in either admin center to the agent and app availability will automatically apply across all supported hosts. Organization-wide defaults for both admin centers will be in sync and govern app availability across Teams, Outlook, and the Microsoft 365 copilot app. What you need to do to prepare To ensure a smooth transition, review your tenant-level and individual agent/app settings (app allow/block & user availability) in both the Microsoft 365 Admin Center and the Teams Admin Center. If different departments within your organization manage these settings, we suggest coordinating efforts to complete the review collaboratively. This update will be rolled out automatically by the stated date, and no immediate action is required. However, it's a good time to update any internal documentation related to agent and app management policies. |
Before this rollout, managing Teams apps that work in Outlook and the Microsoft 365 app was fragmented between the Integrated apps page in the Microsoft 365 admin center for Outlook and the Microsoft 365 app, and the Teams admin center for Teams. This sometimes resulted in different settings for the same app in the two admin centers. With Unified agent app management, you will be able to manage apps on the Integrated apps page in the Microsoft 365 admin center or in the Teams admin center, and any changes made in either admin center will synchronize. What you can expect: You'll gain a consolidated view of agent and Microsoft 365 app availability across both Microsoft 365 and Teams admin centers. Changes made in either admin center to the agent and app availability will automatically apply across all supported hosts. Organization-wide defaults for both admin centers will be in sync and govern app availability across Teams, Outlook, and the Microsoft 365 copilot app. What you need to do to prepare To ensure a smooth transition, review your tenant-level and individual agent/app settings (app allow/block & user availability) in both the Microsoft 365 Admin Center and the Teams Admin Center. If different departments within your organization manage these settings, we suggest coordinating efforts to complete the review collaboratively. This update will be rolled out automatically by the stated date, and no immediate action is required. However, it's a good time to update any internal documentation related to agent and app management policies. Learn more: Unified agent and app availability management across Microsoft 365 and Teams Admin Centers - Microsoft Teams | Microsoft Learn |
N/A |
MC Messages changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1025217 | (Updated) Microsoft Teams: In channels, the "Shared" tab (formerly the "Files" tab) will have new capabilities | Updated August 20, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft Teams: In channels, we will rename the Files tab as the Shared tab to enable users to view content shared in posts and content in the document library in one place. Note: The Shared tab in chats will not be affected by this change. This message applies to Teams for Windows desktop and Teams for Mac desktop. This message is associated with Microsoft 365 Roadmap ID 470597. [When this will happen:] Targeted Release: We will begin rolling out early October 2025 and expect to complete by mid-October 2025. General Availability (Worldwide): We will begin rolling out mid-October 2025 and expect to complete by late October 2025 |
Updated September 29, 2025: We have updated the timeline. Thank you for your patience. Coming soon for Microsoft Teams: In channels, we will rename the Files tab as the Shared tab to enable users to view content shared in posts and content in the document library in one place. Note: The Shared tab in chats will not be affected by this change. This message applies to Teams for Windows desktop and Teams for Mac desktop. This message is associated with Microsoft 365 Roadmap ID 470597. [When this will happen:] Targeted Release: We will begin rolling out early November 2025 and expect to complete by mid-November 2025. General Availability (Worldwide): We will begin rolling out mid-November 2025 and expect to complete by late November 2025. |
N/A |
| MC1037767 | (Updated) Microsoft Teams: Share Teams apps and agents from their profile or the Teams side panel | Updated August 27, 2025: We have updated the timeline. Thank you for your patience. Coming soon: Users can share Microsoft Teams apps or agents from the app or agent profile and from the app side panel in Teams. This message applies to Teams for Windows desktop, Teams for Mac desktop and Teams on the web. A Microsoft 365 Copilot license is not required to share agents as described in this message. If a user has access to the agents, the users will be able to share them. This message is associated with Microsoft 365 Roadmap ID 483355. [When this will happen:] Targeted Release: We will begin rolling out mid-October 2025 and expect to complete by late October 2025. General Availability (Worldwide): We will begin rolling out early November 2025 and expect to complete by late November 2025 |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. Coming soon: Users can share Microsoft Teams apps or agents from the app or agent profile and from the app side panel in Teams. This message applies to Teams for Windows desktop, Teams for Mac desktop and Teams on the web. A Microsoft 365 Copilot license is not required to share agents as described in this message. If a user has access to the agents, the users will be able to share them. This message is associated with Microsoft 365 Roadmap ID 483355. [When this will happen:] Targeted Release: We will begin rolling out early November 2025 and expect to complete by mid-November 2025. General Availability (Worldwide): We will begin rolling out mid-November 2025 and expect to complete by early December 2025 |
N/A |
| MC1045227 | (Updated) Microsoft Viva Connections cards in SharePoint agents | Updated July 11, 2025: We have updated the timeline below. Thank you for your patience. Microsoft SharePoint agents will now bring Viva Connections cards to conversations. When a card is relevant for a specific topic, it will surface in the conversation chat, allowing users to interact with it directly from SharePoint agents without interrupting their flow. This message is associated with Microsoft 365 Roadmap ID 412621. [When this will happen:] Public Preview: We will begin rolling out on late March 2025 and expect to complete by late June 2025. General Availability (Worldwide): We will begin rolling out on late September 2025 (previously late June) and expect to complete by late October 2025 (previously late August). |
Updated September 29, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. Microsoft SharePoint agents will now bring Viva Connections cards to conversations. When a card is relevant for a specific topic, it will surface in the conversation chat, allowing users to interact with it directly from SharePoint agents without interrupting their flow. This message is associated with Microsoft 365 Roadmap ID 412621. [When this will happen:] Public Preview: We will begin rolling out on late March 2025 and expect to complete by late June 2025. General Availability (Worldwide): We will communicate via Message center when we are ready to proceed. |
N/A |
| MC1048624 | (Updated) DNS Provisioning Change | Updated August 22, 2025: We have updated the content. Thank you for your patience. We're making some changes to DNS provisioning of A records for all new Accepted Domains provisioned after October 1st, 2025 (previously August 1st). Between early and late October 2025 (previously early August and late August), 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. |
Updated October 2, 2025: 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 February 1st, 2025 (previously October 1st). Between early and late February 2026 (previously early October and late October), 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. |
02/01/2026 |
| MC1068905 | Microsoft Project for the web and Project in Teams will retire and redirect to Planner for the web and Planner in Teams | Updated September 23, 2025: We have updated the timeline. Thank you for your patience. The new Microsoft Planner for the web (https://planner.cloud.microsoft) brings together the simplicity of Microsoft To Do, the collaboration of Planner, and the advanced capabilities of Microsoft Project into one platform. Planner for the web offers a comprehensive and scalable solution, whether users are managing individual tasks or overseeing professional-grade projects. All users with an existing Project for the web license will have access to Planner. (A Microsoft Teams license is also required to use Planner in Teams.) Starting early August 2025, we will retire Project for the web and will redirect its users to Planner for the web and Planner for Teams, for a smooth transition. Premium plans from Project for the web automatically will be available in Planner, ensuring users experience a seamless migration without losing any data. We will add these capabilities to Planner before the redirect goes into effect: Users will be able view and manage non-default environment plans in Planner. We will rename Project Power app to Planner power app (and the button to open the plan in Project will be replaced with a button to open the plan in Planner). Project settings in the Microsoft 365 admin center will move to the Planner page in the admin center. Tenants with only Project licenses will be able to access basic plan functionality in Planner. We will roll out the new Planner to GCC High. User experience in Project and Roadmap for the web and Teams When launching Project for the web or Roadmap for the web, users will see a page directing them to open Planner for the web, they will not be able to dismiss this screen or use Project or Roadmap for the web. Existing Project tabs in Teams will no longer open the associated project, and instead will show users a page to inform them to re-pin their tab using the Planner tab for Teams Existing Roadmap tabs in Teams will no longer open the associated roadmap, and instead will show a page directing users to the Planner app in Teams Users will no longer have access to view or create Roadmaps in Project for the web, but their Roadmap data will remain in Dataverse We will remove the Project tab and Roadmap tab apps from the Teams app store. [When this will happen:] For Worldwide: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. For GCC: We will begin rolling out mid-August 2025 and expect to complete by late August 2025. For GCC High: We will begin rolling out late August 2025 and expect to complete by late September 2025 (previously mid-September). |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. The new Microsoft Planner for the web (https://planner.cloud.microsoft) brings together the simplicity of Microsoft To Do, the collaboration of Planner, and the advanced capabilities of Microsoft Project into one platform. Planner for the web offers a comprehensive and scalable solution, whether users are managing individual tasks or overseeing professional-grade projects. All users with an existing Project for the web license will have access to Planner. (A Microsoft Teams license is also required to use Planner in Teams.) Starting early August 2025, we will retire Project for the web and will redirect its users to Planner for the web and Planner for Teams, for a smooth transition. Premium plans from Project for the web automatically will be available in Planner, ensuring users experience a seamless migration without losing any data. We will add these capabilities to Planner before the redirect goes into effect: Users will be able view and manage non-default environment plans in Planner. We will rename Project Power app to Planner power app (and the button to open the plan in Project will be replaced with a button to open the plan in Planner). Project settings in the Microsoft 365 admin center will move to the Planner page in the admin center. Tenants with only Project licenses will be able to access basic plan functionality in Planner. We will roll out the new Planner to GCC High. User experience in Project and Roadmap for the web and Teams When launching Project for the web or Roadmap for the web, users will see a page directing them to open Planner for the web, they will not be able to dismiss this screen or use Project or Roadmap for the web. Existing Project tabs in Teams will no longer open the associated project, and instead will show users a page to inform them to re-pin their tab using the Planner tab for Teams Existing Roadmap tabs in Teams will no longer open the associated roadmap, and instead will show a page directing users to the Planner app in Teams Users will no longer have access to view or create Roadmaps in Project for the web, but their Roadmap data will remain in Dataverse We will remove the Project tab and Roadmap tab apps from the Teams app store. [When this will happen:] For Worldwide: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. For GCC: We will begin rolling out mid-August 2025 and expect to complete by late August 2025. For GCC High: We will begin rolling out late August 2025 and expect to complete by early October 2025 (previously mid-September). |
N/A |
| MC1085574 | (Updated) Copilot Dashboard: Updated meeting metrics for Intelligent Recap | Updated June 27, 2025: We have updated the timeline below. Thank you for your patience. Copilot Dashboard users can now view metrics that reflect both summarized and recapped meeting activity, offering a more complete view of Copilot's impact in Teams. These updates replace previous Copilot Assisted Hour calculations and meeting metrics with unified "summarized or recapped" metrics, helping leaders better understand usage across their organization. The updated metrics are available in both the Copilot Dashboard and the M365 Copilot Impact report in Advanced Insights, with additional query support for Intelligent Recap meeting metrics. This change is associated with Microsoft 365 Roadmap ID: 494687 [When this will happen:] Public Preview: We will begin rolling out this change late September 2025 (previously late July) and expect to complete by late October 2025 (previously late September). General Availability (Worldwide): We will begin rolling out this change late October 2025 (previously late September) and expect to complete by late November 2025 (previously late October). |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. Copilot Dashboard users can now view metrics that reflect both summarized and recapped meeting activity, offering a more complete view of Copilot's impact in Teams. These updates replace previous Copilot Assisted Hour calculations and meeting metrics with unified "summarized or recapped" metrics, helping leaders better understand usage across their organization. The updated metrics are available in both the Copilot Dashboard and the M365 Copilot Impact report in Advanced Insights, with additional query support for Intelligent Recap meeting metrics. This change is associated with Microsoft 365 Roadmap ID: 494687 [When this will happen:] Public Preview: We will begin rolling out this change late September 2025 (previously late July) and expect to complete by late October 2025 (previously late September). General Availability (Worldwide): We will begin rolling out this change late November 2025 (previously late October) and expect to complete by late December 2025 (previously late November). |
N/A |
| MC1104306 | (Updated) Microsoft Teams: Users can save chats and channel messages for later | Updated July 10, 2025: This feature will not be available for tenants in the Education (EDU) segment. We're introducing a new user feature in Microsoft Teams that allows individuals to save any message-whether it's a post, reply, or chat-and access it later from the Saved view in their Chat or Teams list. Clicking a saved message will open the full conversation in the right pane, enabling users to review or respond directly. This helps users quickly return to important information without scrolling through long threads. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. This message is associated with Microsoft 365 Roadmap ID 496369. [When this will happen:] Targeted Release: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late August 2025 and expect to complete by early September 2025. |
Updated September 29, 2025: We have updated the timeline. Thank you for your patience. We're introducing a new user feature in Microsoft Teams that allows individuals to save any message-whether it's a post, reply, or chat-and access it later from the Saved view in their Chat or Teams list. Clicking a saved message will open the full conversation in the right pane, enabling users to review or respond directly. This helps users quickly return to important information without scrolling through long threads. This message applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android. This message is associated with Microsoft 365 Roadmap ID 496369. [When this will happen:] Targeted Release: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late August 2025 and expect to complete by late October 2025. |
N/A |
| MC1117814 | (Updated) Microsoft Viva Engage | Email sender domain migration from @yammer.com to @engage.mail.microsoft | Updated August 22, 2025: We have updated the content. Thank you for your patience. Introduction As part of the final phase of the Viva Engage rebranding, we're updating the email sender domains used for Viva Engage communications. This change ensures a consistent and secure brand experience across all surfaces and completes the transition from Yammer to Viva Engage. This update was previously communicated in MC679739, "Yammer Rebranding to Viva Engage Domain Migration Update," in October 2023. When this will happen The email sender domain rollout will begin in early September 2025 (previously late August) for U.S. and EU tenants currently receiving messages from @yammer.com and @eu.yammer.com respectively. The entire rollout is expected to complete by the end of October 2025. A fallback/coexistence period will be in place between September (previously August) and the end of October, during which both the old and new domains will be supported. During this time, some users within a tenant may receive emails from the old domain while others receive them from the new domain. |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. Introduction As part of the final phase of the Viva Engage rebranding, we're updating the email sender domains used for Viva Engage communications. This change ensures a consistent and secure brand experience across all surfaces and completes the transition from Yammer to Viva Engage. This update was previously communicated in MC679739, "Yammer Rebranding to Viva Engage Domain Migration Update," in October 2023. When this will happen The email sender domain rollout will begin in early September 2025 (previously late August) for U.S. and EU tenants currently receiving messages from @yammer.com and @eu.yammer.com respectively. The entire rollout is expected to complete by Q1 CY2026 (previously late October). A fallback/coexistence period will be in place between September (previously August) and by Q1 CY2026 (previously late October). during which both the old and new domains will be supported. During this time, some users within a tenant may receive emails from the old domain while others receive them from the new domain. |
N/A |
| MC1124558 | (Updated) Microsoft Entra: Cross-cloud synchronization now available | Updated September 12, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing cross-cloud synchronization in Microsoft Entra to help organizations streamline user lifecycle management across Microsoft's commercial, US Government, and China cloud environments. This feature automates creating, updating, and deleting users across supported cloud pairs and is currently in public preview. It is off by default and must be explicitly enabled by administrators. When this will happen General availability (Worldwide, GCC, GCCH, DoD): The capability is currently in public preview and will be rolled out to general availability between late September 2025 (previously early September) and mid-October 2025 (previously mid-September). |
Updated October 2, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing cross-cloud synchronization in Microsoft Entra to help organizations streamline user lifecycle management across Microsoft's commercial, US Government, and China cloud environments. This feature automates creating, updating, and deleting users across supported cloud pairs and is currently in public preview. It is off by default and must be explicitly enabled by administrators. When this will happen General availability (Worldwide, GCC, GCCH, DoD): The capability is currently in public preview and will be rolled out to general availability between late September 2025 (previously early September) and early October 2025 (previously mid-October). |
N/A |
| MC1127233 | (Updated) Feature retirement: deploy Shifts to your frontline teams at scale in Teams Admin Center | Updated September 10, 2025: We have updated the timeline. Thank you for your patience. Introduction We're retiring the Deploy Shifts to your frontline teams at scale feature in Microsoft Teams Admin Center. Starting September 5, 2025, this functionality will no longer be available. We recommend using the Teams web or desktop app to manage Shifts, where ongoing investments will continue to enhance scheduling capabilities. When this will happen The retirement will begin and complete on September 25, 2025 (previously September 5). |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. Introduction We're retiring the Deploy Shifts to your frontline teams at scale feature in Microsoft Teams Admin Center. Starting September 5, 2025, this functionality will no longer be available. We recommend using the Teams web or desktop app to manage Shifts, where ongoing investments will continue to enhance scheduling capabilities. When this will happen The retirement will begin September 25, 2025. |
N/A |
| MC1129716 | (Updated) Microsoft Outlook Mobile adds support for DLP policy tips and enforcement | Updated August 7, 2025: We have updated the timeline. Thank you for your patience. Introduction Outlook Mobile for iOS and Android will soon support Data Loss Prevention (DLP) policy tips and enforcement. This update helps users avoid accidental data leaks by providing inline alerts or pop-ups when sensitive content is detected-based on admin-configured DLP rules. This enhancement brings DLP behavior in Outlook Mobile in line with Outlook for desktop and web, ensuring consistent compliance enforcement across platforms. This message is associated with Microsoft 365 Roadmap ID 496146. When this will happen General Availability rollout will begin in early August 2025 (previously mid-August) and is expected to complete by early September 2025. |
Updated September 29, 2025: After further review, we need to roll this back. We apologize for any inconvenience. Introduction Outlook Mobile for iOS and Android will soon support Data Loss Prevention (DLP) policy tips and enforcement. This update helps users avoid accidental data leaks by providing inline alerts or pop-ups when sensitive content is detected-based on admin-configured DLP rules. This enhancement brings DLP behavior in Outlook Mobile in line with Outlook for desktop and web, ensuring consistent compliance enforcement across platforms. This message is associated with Microsoft 365 Roadmap ID 496146. When this will happen We will communicate via Message center when we are ready to proceed. |
N/A |
| MC1130385 | (Updated) Retirement of inline SVG images in Microsoft Outlook | Introduction We're retiring support for inline SVG images in Outlook for Web and the new Outlook for Windows starting early September 2025. This change enhances security and aligns with current email client behavior, which already restricts inline SVG rendering. When this will happen Worldwide rollout: Begins early September 2025, expected to complete by mid-September 2025. GCC, GCC-H, DoD rollout: Begins mid-September 2025, expected to complete by late September 2025. |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. Introduction We're retiring support for inline SVG images in Outlook for Web and the new Outlook for Windows starting early September 2025. This change enhances security and aligns with current email client behavior, which already restricts inline SVG rendering. When this will happen When this will happen Worldwide rollout: Begins early September 2025, expected to complete by mid-September 2025. GCC, GCC-H, DoD, Gallatin rollout: Begins mid-September 2025, expected to complete by mid-October 2025 (previously late September). |
N/A |
| MC1134174 | (Updated) Outlook Mobile for iOS and Android: Draft messages now minimize automatically when closed | Updated September 3, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing a new behavior in Outlook Mobile that improves draft handling. When users close a draft message in progress, it will now automatically minimize instead of closing completely. This allows users to quickly resume editing via a new button in the message list, enhancing productivity and reducing accidental draft loss. When this will happen General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in late September 2025 (previously early September) and is expected to complete by early March 2026. |
Updated October 2, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing a new behavior in Outlook Mobile that improves draft handling. When users close a draft message in progress, it will now automatically minimize instead of closing completely. This allows users to quickly resume editing via a new button in the message list, enhancing productivity and reducing accidental draft loss. When this will happen General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in late September 2025 (previously early September) and is expected to complete by late October 2025 (previously early March 2026). |
N/A |
| MC1141945 | (Updated) Executable name update for Microsoft 365 Copilot app for Windows | Updated September 24, 2025: We have updated the timeline. Thank you for your patience. To better reflect the identity and functionality of the Microsoft 365 Copilot app, we are updating the executable name on Windows devices. This change improves clarity for IT admins, developers, and users managing diagnostics or process monitoring. When this will happen: This update will roll out to affected users with the next app update after late September 2025 (previously September 20). |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. To better reflect the identity and functionality of the Microsoft 365 Copilot app, we are updating the executable name on Windows devices. This change improves clarity for IT admins, developers, and users managing diagnostics or process monitoring. When this will happen: This update will roll out to affected users with the next app update after late October 2025 (previously late September). |
N/A |
| MC1143280 | (Updated) Microsoft Copilot dashboard (in Viva Insights): Adoption metrics for Microsoft 365 Copilot Chat | Updated September 25, 2025: After further review, we will announce a revised GA date after we have had an opportunity to collect feedback from the public preview. Thank you for your patience. Introduction We're introducing a new feature: M365 Copilot Chat adoption metrics in the Microsoft Copilot dashboard. This feature provides organizations with enhanced visibility into how users who are not licensed for Microsoft 365 Copilot are engaging with Copilot Chat. These insights include usage trends, retention and intensity metrics, app-level breakdowns, and filtering by organizational attributes-helping organizations better understand adoption patterns and tailor support strategies. This feature will be available to tenants with at least 50 assigned Viva Insights licenses or 50 assigned Microsoft 365 Copilot licenses (includes Viva Insights service plan). This message is associated with Microsoft 365 Roadmap ID 499899. When this will happen Public Preview: We will begin rolling out at the end of October 2025 and expect to complete by end of November 2025. General availability (Worldwide): We will announce a revised GA date after we have had an opportunity to collect feedback from the public preview. Thank you for your patience. |
Updated October 1, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing a new feature: M365 Copilot Chat adoption metrics in the Microsoft Copilot dashboard. This feature provides organizations with enhanced visibility into how users who are not licensed for Microsoft 365 Copilot are engaging with Copilot Chat. These insights include usage trends, retention and intensity metrics, app-level breakdowns, and filtering by organizational attributes-helping organizations better understand adoption patterns and tailor support strategies. This feature will be available to tenants with at least 50 assigned Viva Insights licenses or 50 assigned Microsoft 365 Copilot licenses (includes Viva Insights service plan). This message is associated with Microsoft 365 Roadmap ID 499899. When this will happen Public Preview: We will begin rolling out at the end of October 2025 and expect to complete by end of November 2025. General availability (Worldwide): We will begin rolling out at the end of November 2025 and expect to complete by end of December 2025. |
N/A |
| MC1146816 | (Updated) Microsoft Copilot dashboard (in Viva Insights): New benchmarks to compare Copilot usage across organizations | We're introducing Benchmarks in the Microsoft Copilot dashboard (in Viva Insights). This new feature enables organizations to compare Copilot usage internally across cohorts and externally against similar companies. These insights help identify adoption trends and opportunities to improve Copilot engagement. This message is associated with Microsoft 365 Roadmap ID: 495464. When this will happen Targeted Release (Worldwide): We will begin rolling out in late September 2025 and expect to complete by early October 2025. General Availability (Worldwide): We will begin rolling out in mid-October 2025 and expect to complete by late October 2025. |
Updated October 1, 2025: We have updated the timeline. Thank you for your patience. We're introducing Benchmarks in the Microsoft Copilot dashboard (in Viva Insights). This new feature enables organizations to compare Copilot usage internally across cohorts and externally against similar companies. These insights help identify adoption trends and opportunities to improve Copilot engagement. This message is associated with Microsoft 365 Roadmap ID: 495464. When this will happen Targeted Release (Worldwide): We will begin rolling out in mid-October 2025 (previously late September) and expect to complete by late October 2025 (previously early October). General Availability (Worldwide): We will begin rolling out in late October 2025 (previously mid-October) and expect to complete by late November 2025 (previously late October). |
N/A |
| MC1146822 | (Updated) Microsoft Viva: Copilot Analytics - Unified Exclusion list | Introduction We're introducing a Unified Exclusion list in Copilot Analytics (Microsoft Viva Insights), a new feature that provides a single, consistent way to exclude specific users from all Viva Insights. With this update, administrators will have one consolidated exclusion list that applies across the Microsoft Copilot Dashboard (in Viva Insights), Manager and Team insights, Advanced Insights, and the upcoming Microsoft 365 Copilot Chat analytics (available in Copilot Dashboard). Admins can manage exclusions easily through one list, simplifying configuration and safeguarding sensitive user data without impacting other organizational HR data. This ensures consistent privacy controls and data reporting for both licensed and "free" (unlicensed) Copilot users in your organization. Admins can use CSV upload and Azure Active Directory (Entra ID groups) to manage exclusions in the tenant. This message is associated with Microsoft 365 Roadmap ID 500161. When this will happen General Availability (Worldwide): We will begin rolling out this feature update globally, starting late-September 2025 and expect rollout to be completed by early-October 2025. |
Updated October 2, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing a Unified Exclusion list in Copilot Analytics (Microsoft Viva Insights), a new feature that provides a single, consistent way to exclude specific users from all Viva Insights. With this update, administrators will have one consolidated exclusion list that applies across the Microsoft Copilot Dashboard (in Viva Insights), Manager and Team insights, Advanced Insights, and the upcoming Microsoft 365 Copilot Chat analytics (available in Copilot Dashboard). Admins can manage exclusions easily through one list, simplifying configuration and safeguarding sensitive user data without impacting other organizational HR data. This ensures consistent privacy controls and data reporting for both licensed and "free" (unlicensed) Copilot users in your organization. Admins can use CSV upload and Azure Active Directory (Entra ID groups) to manage exclusions in the tenant. This message is associated with Microsoft 365 Roadmap ID 500161. When this will happen General Availability (Worldwide): We will begin rolling out this feature update globally, starting early October 2025 (previously late-September) and expect rollout to be completed by late October 2025 (previously early October). |
N/A |
| MC1148543 | (Updated) Microsoft Teams: Collaborative Notes in Chats | Introduction We're introducing Teams Collaborative Notes (powered by Loop) in group chats across desktop and web experiences. This feature enables users to co-create and edit notes, agendas, and action items directly within the Teams chat interface, enhancing real-time collaboration without switching contexts. This message is associated with Roadmap ID 498159. When this will happen Public Preview: Rollout begins late September 2025 and completes by early October 2025. General Availability: Rollout begins late September 2025 and completes by early October 2025. |
Updated September 30, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing Teams Collaborative Notes (powered by Loop) in group chats across desktop and web experiences. This feature enables users to co-create and edit notes, agendas, and action items directly within the Teams chat interface, enhancing real-time collaboration without switching contexts. This message is associated with Roadmap ID 498159. When this will happen Public Preview: Rollout begins late September 2025 and completes by early October 2025. General Availability: Rollout begins early October 2025 (previously late September) and completes by late October 2025 (previously early October). |
N/A |
| MC1148543 | (Updated) Microsoft Teams: Collaborative Notes in Chats | Updated September 30, 2025: We have updated the timeline. Thank you for your patience. Introduction We're introducing Teams Collaborative Notes (powered by Loop) in group chats across desktop and web experiences. This feature enables users to co-create and edit notes, agendas, and action items directly within the Teams chat interface, enhancing real-time collaboration without switching contexts. This message is associated with Roadmap ID 498159. When this will happen Public Preview: Rollout begins late September 2025 and completes by early October 2025. General Availability: Rollout begins early October 2025 (previously late September) and completes by late October 2025 (previously early October). |
Updated October 2, 2025: We have updated the content. Thank you for your patience. Introduction We're introducing Teams Collaborative Notes (powered by Loop) in group chats across desktop and web experiences. This feature enables users to co-create and edit notes, agendas, and action items directly within the Teams chat interface, enhancing real-time collaboration without switching contexts. This message is associated with Roadmap ID 498159. When this will happen Public Preview: Rollout begins late September 2025 and completes by early October 2025. General Availability: Rollout begins early October 2025 (previously late September) and completes by late October 2025 (previously early October). |
N/A |
| MC1150662 | Action Required – Configure Browser Policy to Preserve OneDrive and SharePoint Web Performance and Offline Capability | Updated September 15, 2025: We have updated the content. Thank you for your patience. [Introduction] Upcoming privacy-related changes in Chromium-based browsers (Google Chrome and Microsoft Edge) will increase restrictions on local network access. When enforcement begins, users accessing OneDrive for Web (and some integrated Microsoft 365 experiences such as Microsoft Lists and SharePoint Document Libraries) will encounter a browser permission prompt for local network access unless the required policy is in place. If the permission is not allowed, performance optimizations and offline capabilities powered by OneDrive and Share Point will not be available. This communication provides required administrator actions to prevent loss of functionality. [When this will happen:] Chrome and Edge will roll out this privacy related change as part of Chromium 141 at the end of September. |
Updated October 3, 2025: We have updated the timeline. Thank you for your patience. [Introduction] Upcoming privacy-related changes in Chromium-based browsers (Google Chrome and Microsoft Edge) will increase restrictions on local network access. When enforcement begins, users accessing OneDrive for Web (and some integrated Microsoft 365 experiences such as Microsoft Lists and SharePoint Document Libraries) will encounter a browser permission prompt for local network access unless the required policy is in place. If the permission is not allowed, performance optimizations and offline capabilities powered by OneDrive and Share Point will not be available. This communication provides required administrator actions to prevent loss of functionality. [When this will happen:] Chrome and Edge will roll out this privacy related change as part of Chromium 141 at the end of October 2025 (previously end of September). |
N/A |
| MC1156359 | (Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online | Introduction To streamline reporting experiences and focus development efforts on modern integration paths, we're retiring the legacy Power BI integration within SharePoint lists and libraries. This change supports improved performance and flexibility through supported alternatives like Export to Power BI and Power BI Desktop connections. When this will happen: Retirement begins mid-November and ends mid-December 2025. |
Updated September 30, 2025: We have updated the content. Thank you for your patience. Introduction To streamline reporting experiences and focus development efforts on modern integration paths, we're retiring the legacy Power BI integration within SharePoint lists and libraries. This change supports improved performance and flexibility through supported alternatives like Export to Power BI and Power BI Desktop connections. When this will happen: Retirement begins mid-November and ends mid-December 2025. There will be no extensions. |
N/A |
| MC1160180 | (Updated) NEW Microsoft 365 companion apps: a suite designed to enhance productivity | [Introduction] Starting in late October 2025, Microsoft will begin automatically installing the Microsoft 365 companion apps-People, Files, and Calendar-on Windows 11 devices that already have Microsoft 365 desktop client apps. These taskbar-integrated apps are designed to streamline everyday workflows, helping users stay focused, reduce context switching, and complete tasks faster. With Copilot integration, users can ground their prompts in the right context-whether it's a shared file, a meeting, or a collaborator. This integration allows users to catch up, summarize, and take action more efficiently. This message is associated with Microsoft 365 Roadmap ID 486856. [When this will happen:] General availability: Rollout begins late October 2025 and is expected to complete late December 2025. |
Updated September 30, 2025: We have updated the content. Thank you for your patience. [Introduction] Starting in late October 2025, Microsoft will begin automatically installing the Microsoft 365 companion apps-People, Files, and Calendar-on Windows 11 devices that already have Microsoft 365 desktop client apps. These taskbar-integrated apps are designed to streamline everyday workflows, helping users stay focused, reduce context switching, and complete tasks faster. With Copilot integration, users can ground their prompts in the right context-whether it's a shared file, a meeting, or a collaborator. This integration allows users to catch up, summarize, and take action more efficiently. This message is associated with Microsoft 365 Roadmap ID 486856. [When this will happen:] General availability: Rollout begins late October 2025 and is expected to complete late December 2025. |
N/A |
| MC1162276 | (Updated) Microsoft Teams: Trust Indicators – a new way of representing users outside your organization | [Introduction:] To help users quickly identify external participants in Microsoft Teams and reduce the risk of oversharing sensitive information, we're introducing Trust Indicators-visual labels (badges or icons) next to people's names. These indicators signal whether someone is external to your organization, a guest, or an anonymous meeting participant. [When this will happen:] Public Preview: Begins rolling out late September 2025; expected completion by late November 2025. General Availability (Worldwide, GCC, GCC High, DoD): Begins rolling out late November 2025; expected completion by early January 2050. |
Updated September 30, 2025: We have updated the title and timeline. Thank you for your patience. [Introduction:] To help users quickly identify external participants in Microsoft Teams and reduce the risk of oversharing sensitive information, we're introducing Trust Indicators-visual labels (badges or icons) next to people's names. These indicators signal whether someone is external to your organization, a guest, or an anonymous meeting participant. [When this will happen:] Public Preview: Begins rolling out late September 2025; expected completion by late November 2025. General Availability (Worldwide, GCC, GCC High, DoD): Begins rolling out late November 2025; expected completion by early January 2026. |
N/A |
| MC1162288 | (Updated) Microsoft Outlook: Declarative Agents in Copilot Chat coming to classic Outlook for Windows | [Introduction:] To enhance the extensibility of Microsoft 365 Copilot, we're introducing support for Declarative Agents in Biz Chat and Biz Chat Starter within classic Outlook for Windows. Declarative Agents allow users to customize their Copilot experience by integrating plugins, enterprise connectors, and orchestration logic. This update aligns classic Outlook with other Copilot Chat experiences, delivering consistent agent capabilities across platforms. This update is tracked under Microsoft 365 Roadmap ID 481559. [When this will happen:] General Availability (Worldwide): We will begin rolling out late October 2025 and expect to complete by mid-December 2025. |
Updated October 3, 2025: We have updated the timeline. Thank you for your patience. [Introduction:] To enhance the extensibility of Microsoft 365 Copilot, we're introducing support for Declarative Agents in Copilot Chat within classic Outlook for Windows. Declarative Agents will be available for Copilot Chat users (without a Microsoft 365 Copilot license) and Microsoft 365 Copilot users (with a Microsoft 365 Copilot license). Declarative Agents allow users to customize their Copilot experience by integrating plugins, enterprise connectors, and orchestration logic. This update aligns classic Outlook with other Copilot Chat experiences, delivering consistent agent capabilities across platforms. This update is tracked under Microsoft 365 Roadmap ID 481559. [When this will happen:] General Availability (Worldwide): We will begin rolling out late October 2025 and expect to complete by mid-December 2025. |
N/A |
| MC1162289 | (Updated) Microsoft Outlook: Summarize email with Copilot chat | [Introduction] We're introducing a new way to quickly summarize emails using Copilot chat in Outlook. With a single click, users can generate concise summaries of email content, helping them stay focused and save time. This feature supports both Classic and New Outlook for Windows and is available to users with a Microsoft 365 Copilot license and pinning enabled. This message is associated with Microsoft 365 Roadmap ID 503316. [When this will happen:] Targeted Release (Worldwide): Rollout underway by early October 2025; expected completion by early November 2025. General Availability (Worldwide): Begins mid-October 2025; expected completion by late November 2025. |
Updated October 2, 2025: We have updated the content. Thank you for your patience. [Introduction] We're introducing a new way to quickly summarize emails and attachments using Copilot chat in Outlook. With a single click, users can generate concise summaries of email content and attachments, helping them stay focused and save time. This feature supports both Classic and New Outlook for Windows and is available to users with a Microsoft 365 Copilot license and pinning enabled. This message is associated with Microsoft 365 Roadmap ID 503316. [When this will happen:] Targeted Release (Worldwide): Rollout underway by early October 2025; expected completion by early November 2025. General Availability (Worldwide): Begins mid-October 2025; expected completion by late November 2025. |
N/A |
| MC1163100 | Power Automate for desktop - Assign custom names to actions in desktop flows | We are announcing the ability to assign custom names to actions in desktop flows in Power Automate for desktop. This feature will reach general availability on October 31, 2025. | Update: Release of this feature has been postponed, we will announce a new date in the future.
We are announcing the ability to assign custom names to actions in desktop flows in Power Automate for desktop. |
N/A |
| MC542767 | (Updated) SharePoint 2013 workflow retirement | Updated June 2, 2025: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 10 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:] Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants. Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants. |
Updated October 3, 2025: This update serves as a reminder that SharePoint 2013 workflow will retire and stop working in 6 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:] Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants. Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants. |
N/A |
| MC693863 | (Updated) Azure ACS retirement in Microsoft 365 | Updated June 2, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 10 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:] Major: Retirement Timeline: Starting November 1st, 2024, new tenants will not be able use Azure ACS. Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants. Action: Review and assess impact |
Updated October 3, 2025: This update serves as a reminder that Azure ACS in Microsoft 365 will retire and stop working in 6 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:] Major: Retirement Timeline: Starting November 1st, 2024, new tenants will not be able use Azure ACS. Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants. Action: Review and assess impact |
N/A |
| MC693865 | (Updated) SharePoint Add-In retirement in Microsoft 365 | Updated June 2, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 10 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:] Major: Retirement Timeline: Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible. Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog). Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants. Action: Review and assess impact |
Updated October 3, 2025: This update serves as a reminder that SharePoint Add-Ins will retire and stop working in 6 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:] Major: Retirement Timeline: Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible. Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog). Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants. Action: Review and assess impact |
N/A |
| MC792601 | (Updated) SharePoint Framework domain isolated web parts retirement | Updated June 2, 2025: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 10 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:] Starting April 2, 2025, domain isolated web parts will be turned off for any newly created tenants. Starting April 2, 2026, Microsoft will remove the ability to use domain isolated web parts for existing tenants. |
Updated October 3, 2025: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 6 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:] Starting April 2, 2025, domain isolated web parts will be turned off for any newly created tenants. Starting April 2, 2026, Microsoft will remove the ability to use domain isolated web parts for existing tenants. |
N/A |
| MC796790 | Update: Microsoft 365 and Microsoft Teams: Unified management of Teams apps in Teams, Outlook, and the Microsoft 365 app | Updated September 12, 2025: We have updated the content. Thank you for your patience. What it is Microsoft is rolling out a new feature to streamline how app and agent availability is managed across Teams, Outlook, and Microsoft 365 Copilot. Until now, IT admins configured availability settings separately in both the Microsoft 365 Admin Center (MAC) and the Teams Admin Center (TAC), which led to mismatches. With this update, you'll be able to unify availability policies for apps and agents across both portals, making app management more consistent and efficient. This message is associated with Microsoft 365 Roadmap ID 393931 and 503105. When this will happen: We will begin rolling out this feature late September 2025 and expect to complete by mid-November 2025. 1. Phase 1 - Default Tenant Unification We will begin rolling out this feature at the end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and Microsoft 365 apps availability policies are in alignment for all future administrative changes. This message is associated with Microsoft 365 Roadmap ID 393931. 2. Phase 2 - Modified Tenants Unification We will begin rolling out this feature at the end of October 2025. This phase targets tenants that have previously modified their organization-wide defaults, app availability, or block/unblock settings in either admin center. These tenants will be transitioned to a unified management experience across both Microsoft 365 and Teams admin centers. For tenants with agent or app availability differences across both admin centers, a wizard in the Teams admin center will help identify affected agents and apps and guide through resolving discrepancies. For tenants with no agent or app availability differences across both admin centers, guidance will be provided to help maintain unified availability policy for all future changes. This message is associated with Microsoft 365 Roadmap ID 503105. 3. Phase 3 - Automatic Unification Tenants that haven't transitioned as part of Phase 1 & Phase 2, will be automatically moved to unified app agent management. We will update this post with a timeline and more details later. |
Updated October 1, 2025: We have updated the content documentation link. Thank you for your patience. What it is Microsoft is rolling out a new feature to streamline how app and agent availability is managed across Teams, Outlook, and Microsoft 365 Copilot. Until now, IT admins configured availability settings separately in both the Microsoft 365 Admin Center (MAC) and the Teams Admin Center (TAC), which led to mismatches. With this update, you'll be able to unify availability policies for apps and agents across both portals, making app management more consistent and efficient. This message is associated with Microsoft 365 Roadmap ID 393931 and 503105. When this will happen: We will begin rolling out this feature late September 2025 and expect to complete by mid-November 2025. 1. Phase 1 - Default Tenant Unification We will begin rolling out this feature at the end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and Microsoft 365 apps availability policies are in alignment for all future administrative changes. This message is associated with Microsoft 365 Roadmap ID 393931. 2. Phase 2 - Modified Tenants Unification We will begin rolling out this feature at the end of October 2025. This phase targets tenants that have previously modified their organization-wide defaults, app availability, or block/unblock settings in either admin center. These tenants will be transitioned to a unified management experience across both Microsoft 365 and Teams admin centers. For tenants with agent or app availability differences across both admin centers, a wizard in the Teams admin center will help identify affected agents and apps and guide through resolving discrepancies. For tenants with no agent or app availability differences across both admin centers, guidance will be provided to help maintain unified availability policy for all future changes. This message is associated with Microsoft 365 Roadmap ID 503105. 3. Phase 3 - Automatic Unification Tenants that haven't transitioned as part of Phase 1 & Phase 2, will be automatically moved to unified app agent management. We will update this post with a timeline and more details later. |
N/A |
| MC921752 | (Updated) Retirement of the SharePoint SendEmail API | Updated June 5, 2025: As a reminder from the post announced on October 31st, 2024, we will be retiring the Utility.SendEmail API on October 31st, 2025. In addition, you are now able to identify usage of the API via the Purview audit logs in the admin center As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center. Open Audit to search for activities. Select a date range to run the audit search for (recommend running it for at least 90 days) Put the following text, "SendEmailApiInvoked" into the "Activities - operation names" textbox and click search. The request will be queued, and results will be available once processed. Click on the results and review each of the items. Use the UserAgent and ApplicationDisplayName to help identify the caller. [NOTE:] If the ApplicationDisplayName = "Workflow" then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows. From custom code the API can be referenced via REST as ("/_api/SP.Utilities.Utility.SendEmail") while for CSOM, it would be "Utility.SendEmail" with more information on the original implementation at Utility.SendEmail method for CSOM. [When this will happen:] October 31, 2025 |
Updated September 30, 2025: As a reminder from the post announced on October 31st, 2024, we will be retiring the Utility.SendEmail API on October 31st, 2025. In addition, you are now able to identify usage of the API via the Purview audit logs in the admin center As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center. Open Audit to search for activities. Select a date range to run the audit search for (recommend running it for at least 90 days) Put the following text, "SendEmailApiInvoked" into the "Activities - operation names" textbox and click search. The request will be queued, and results will be available once processed. Click on the results and review each of the items. Use the UserAgent and ApplicationDisplayName to help identify the caller. [NOTE:] If the ApplicationDisplayName = "Workflow" then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows. From custom code the API can be referenced via REST as ("/_api/SP.Utilities.Utility.SendEmail") while for CSOM, it would be "Utility.SendEmail" with more information on the original implementation at Utility.SendEmail method for CSOM. [When this will happen:] October 31, 2025 |
N/A |
| MC921752 | (Updated) Retirement of the SharePoint SendEmail API | Updated September 30, 2025: As a reminder from the post announced on October 31st, 2024, we will be retiring the Utility.SendEmail API on October 31st, 2025. In addition, you are now able to identify usage of the API via the Purview audit logs in the admin center As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center. Open Audit to search for activities. Select a date range to run the audit search for (recommend running it for at least 90 days) Put the following text, "SendEmailApiInvoked" into the "Activities - operation names" textbox and click search. The request will be queued, and results will be available once processed. Click on the results and review each of the items. Use the UserAgent and ApplicationDisplayName to help identify the caller. [NOTE:] If the ApplicationDisplayName = "Workflow" then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows. From custom code the API can be referenced via REST as ("/_api/SP.Utilities.Utility.SendEmail") while for CSOM, it would be "Utility.SendEmail" with more information on the original implementation at Utility.SendEmail method for CSOM. [When this will happen:] October 31, 2025 |
Updated October 1, 2025: As previously announced in the October 31st, 2024, post, we will be retiring the Utility.SendEmail API on October 31st, 2025. As a reminder, you are able to identify usage of the API via the Purview audit logs in the admin center As a tenant admin, navigate to the Microsoft Purview Portal available within the Microsoft 365 Admin Center. Open Audit to search for activities. Select a date range to run the audit search for (recommend running it for at least 90 days) Put the following text, "SendEmailApiInvoked" into the "Activities - operation names" textbox and click search. The request will be queued, and results will be available once processed. Click on the results and review each of the items. Use the UserAgent and ApplicationDisplayName to help identify the caller. [NOTE:] If the ApplicationDisplayName = "Workflow" then the items will be unaffected by this API retirement but will follow the SharePoint 2013 Workflow retirement. We will be retiring the Utility.SendEmail API from SharePoint. The SP.Utilities.Utility.SendEmail could be used to send emails from custom applications or processes within SharePoint Online, including Power Automate, and custom workflows. From custom code the API can be referenced via REST as ("/_api/SP.Utilities.Utility.SendEmail") while for CSOM, it would be "Utility.SendEmail" with more information on the original implementation at Utility.SendEmail method for CSOM. [When this will happen:] October 31, 2025 |
N/A |
| MC981462 | (Updated) Multiple account access to Copilot in Microsoft 365 desktop and mobile apps | Updated July 2, 2025: We have updated the timeline below. Thank you for your patience. Multiple account access to Copilot in Microsoft 365 desktop and mobile apps will be available soon. [When will this happen] General availability (Worldwide): We will begin rolling out in early March 2025 and expect to complete by early July 2025 (previously mid-June). Cloud Policy to manage use will be available by late January 2025. |
Updated October 1, 2025: Today we announced multiple updates to our Microsoft 365 subscription lineup for individuals. Multiple account access allows individuals with these subscriptions to access Microsoft 365 Copilot value while at work through the Microsoft 365 apps. As mentioned previously, enterprise data protection continues to apply for files accessed with the user's organizational identity, regardless of which account grants Copilot access. Learn more about what this means for your organization. If you wish to restrict multiple account access to Copilot, you can use the "Multiple account access to Copilot for work documents" Cloud Policy. For more information, refer to documentation. Multiple account access to Copilot in Microsoft 365 desktop and mobile apps will be available soon. [When will this happen] General availability (Worldwide): We will begin rolling out in early March 2025 and expect to complete by early July 2025 (previously mid-June). Cloud Policy to manage use will be available by late January 2025. |
N/A |
MC MessageTagNames changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1130385 | (Updated) Retirement of inline SVG images in Microsoft Outlook | Retirement | Updated message, Retirement | N/A |
| MC1134174 | (Updated) Outlook Mobile for iOS and Android: Draft messages now minimize automatically when closed | Feature update | Updated message, Feature update | N/A |
| MC1146822 | (Updated) Microsoft Viva: Copilot Analytics - Unified Exclusion list | New feature, Admin impact | Updated message, New feature, Admin impact | N/A |
| MC1148543 | (Updated) Microsoft Teams: Collaborative Notes in Chats | New feature, User impact | Updated message, New feature, User impact | N/A |
| MC1156359 | (Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online | User impact, Retirement | Updated message, User impact, Retirement | N/A |
| MC1160180 | (Updated) NEW Microsoft 365 companion apps: a suite designed to enhance productivity | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | N/A |
| MC1162276 | (Updated) Microsoft Teams: Trust Indicators – a new way of representing users outside your organization | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | N/A |
| MC1162288 | (Updated) Microsoft Outlook: Declarative Agents in Copilot Chat coming to classic Outlook for Windows | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | N/A |
| MC1162289 | (Updated) Microsoft Outlook: Summarize email with Copilot chat | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | N/A |
MC prepare changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1048624 | (Updated) DNS Provisioning Change | 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 October 1st (previously August 1st) to use List serviceConfigurationRecords Graph API (List serviceConfigurationRecords). Use List serviceConfigurationRecords to retrieve the mailExchange value for your MX record. After October 1st (previously August 1st), 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 October 1st (previously August 1st. 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 October 1st (previously August 1st), 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. https://learn.microsoft.com/graph/api/domain-list-serviceconfigurationrecords?view=graph-rest-1.0&tabs=http |
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 February 1st, 2025 (previously October 1st) to use List serviceConfigurationRecords Graph API (List serviceConfigurationRecords). Use List serviceConfigurationRecords to retrieve the mailExchange value for your MX record. After February 1st, 2025 (previously October 1st), 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 February 1st, 2025 (previously October 1st). 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 February 1st, 2025 (previously October 1st), 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. https://learn.microsoft.com/graph/api/domain-list-serviceconfigurationrecords?view=graph-rest-1.0&tabs=http |
02/01/2026 |
| MC1148543 | (Updated) Microsoft Teams: Collaborative Notes in Chats | https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=498159 | https://learn.microsoft.com/powershell/module/microsoftteams/set-csteamsmessagingconfiguration?view=teams-ps#-messagingnotes https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=498159 |
N/A |
| MC1156359 | (Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online | https://aka.ms/IntegrationSPListPBI https://learn.microsoft.com/power-bi/connect-data/create-dataset-sharepoint-online-list https://learn.microsoft.com/power-bi/connect-data/desktop-sharepoint-online-list |
https://learn.microsoft.com/power-bi/connect-data/create-dataset-sharepoint-online-list https://learn.microsoft.com/power-bi/connect-data/desktop-sharepoint-online-list https://learn.microsoft.com/power-bi/create-reports/service-quick-create-sharepoint-list https://powerbi.microsoft.com/blog/deprecation-of-power-bi-integration-within-sharepoint-lists-and-libraries/ |
N/A |
| MC1160180 | (Updated) NEW Microsoft 365 companion apps: a suite designed to enhance productivity | Notify users about this change via an internal announcement to set expectations. Update any relevant internal documentation to reflect the availability of these apps. If you want to opt out of automatic installation: Uncheck Enable automatic installation of Microsoft 365 companion apps and Microsoft 365 Apps Choose Microsoft 365 companion apps Select Modern App settings Go to Device Configuration Learn more: Overview of Microsoft 365 companion apps - Microsoft 365 Apps | Microsoft Learn Check out the latest features here: Get Started with Microsoft 365 companion apps | Microsoft Support App highlights: People app features: Look up colleagues by name, skills, role, location and more. Find Microsoft 365 and locally downloaded files. Find events by organizer, attendees, or title.
[Compliance considerations:] |
Notify users about this change via an internal announcement to set expectations. Update any relevant internal documentation to reflect the availability of these apps. If you want to opt out of automatic installation: Go to Microsoft 365 App Admin Center. Navigate to Customization -> Device Configuration. Select Modern App settings Choose Microsoft 365 companion apps Uncheck Enable automatic installation of Microsoft 365 companion apps and Microsoft 365 Apps Learn more: Overview of Microsoft 365 companion apps - Microsoft 365 Apps | Microsoft Learn Check out the latest features here: Get Started with Microsoft 365 companion apps | Microsoft Support App highlights: People app features: Look up colleagues by name, skills, role, location and more. Find Microsoft 365 and locally downloaded files. Find events by organizer, attendees, or title.
[Compliance considerations:] |
N/A |
| MC796790 | Update: Microsoft 365 and Microsoft Teams: Unified management of Teams apps in Teams, Outlook, and the Microsoft 365 app | https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=393931 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=503105 |
https://learn.microsoft.com/microsoftteams/uam-tac-mac https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=393931 https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=503105 |
N/A |
| MC921752 | (Updated) Retirement of the SharePoint SendEmail API | Migrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the SP.Utilities.Utility.SendEmail API. The following are recommended or alternative approaches: Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload) Automate creating, sending, and processing messages Customizations through Power Automate may also utilize the Outlook connector and utilize "Send an email" within the Actions. Overview of using Outlook and Power Automate Learn more: Retirement of the SharePoint SendEmail API Automate creating, sending, and processing messages Overview of using Outlook and Power Automate Learn about the Microsoft Purview portal | Microsoft Learn https://go.microsoft.com/fwlink/?linkid=2289866 https://learn.microsoft.com/graph/outlook-create-send-messages https://learn.microsoft.com/power-automate/email-overview https://learn.microsoft.com/previous-versions/office/sharepoint-csom/jj167799(v=office.15) https://learn.microsoft.com/purview/purview-portal |
Migrate any custom code, power automate, processes or policies running within SharePoint Online that have been configured to send email using the SP.Utilities.Utility.SendEmail API. The following are recommended or alternative approaches: Use Microsoft Graph to send email using the user: SendMail API (Part of the Outlook mail workload) Automate creating, sending, and processing messages Customizations through Power Automate may also utilize the Outlook connector and utilize "Send an email" within the Actions. Overview of using Outlook and Power Automate
Learn more: |
N/A |
| MC981462 | (Updated) Multiple account access to Copilot in Microsoft 365 desktop and mobile apps | If you wish to restrict multiple account access to Copilot, you can use the "Multiple account access to Copilot for work documents" Cloud Policy. This policy setting is expected to be available in Cloud Policy by the end of January 2025 [Additional information] For more information, see Multiple account access to Copilot for work and school documents. https://go.microsoft.com/fwlink/p/?linkid=2300619 https://learn.microsoft.com/microsoft-365-apps/admin-center/overview-cloud-policy |
If you wish to restrict multiple account access to Copilot, you can use the "Multiple account access to Copilot for work documents" Cloud Policy. This policy setting is expected to be available in Cloud Policy by the end of January 2025 [Additional information] For more information, see Multiple account access to Copilot for work and school documents. https://go.microsoft.com/fwlink/p/?linkid=2300619 https://learn.microsoft.com/copilot/microsoft-365/multiple-account-access https://learn.microsoft.com/microsoft-365-apps/admin-center/overview-cloud-policy https://techcommunity.microsoft.com/blog/microsoft365copilotblog/employees-can-bring-copilot-from-their-personal-microsoft-365-plans-to-work---wh/4458212 https://www.microsoft.com/en-us/microsoft-365/blog/2025/10/01/meet-microsoft-365-premium-your-ai-and-productivity-powerhouse/ |
N/A |
MC Title changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1130385 | (Updated) Retirement of inline SVG images in Microsoft Outlook | Retirement of inline SVG images in Microsoft Outlook | (Updated) Retirement of inline SVG images in Microsoft Outlook | N/A |
| MC1146816 | (Updated) Microsoft Copilot dashboard (in Viva Insights): New benchmarks to compare Copilot usage across organizations | Microsoft Copilot dashboard (in Viva Insights): New benchmarks to compare Copilot usage across organizations | (Updated) Microsoft Copilot dashboard (in Viva Insights): New benchmarks to compare Copilot usage across organizations | N/A |
| MC1146822 | (Updated) Microsoft Viva: Copilot Analytics - Unified Exclusion list | Microsoft Viva: Copilot Analytics - Unified Exclusion list | (Updated) Microsoft Viva: Copilot Analytics - Unified Exclusion list | N/A |
| MC1148543 | (Updated) Microsoft Teams: Collaborative Notes in Chats | Microsoft Teams: Collaborative Notes in Chats | (Updated) Microsoft Teams: Collaborative Notes in Chats | N/A |
| MC1156359 | (Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online | Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online | (Updated) Retiring Power BI “Visualize the List” and “Visualize the Library” Features in SharePoint Online | N/A |
| MC1160180 | (Updated) NEW Microsoft 365 companion apps: a suite designed to enhance productivity | NEW Microsoft 365 companion apps: a suite designed to enhance productivity | (Updated) NEW Microsoft 365 companion apps: a suite designed to enhance productivity | N/A |
| MC1162276 | (Updated) Microsoft Teams: Trust Indicators – a new way of representing users outside your organization | Trust Indicators- A new way of representing users outside your organization | (Updated) Microsoft Teams: Trust Indicators – a new way of representing users outside your organization | N/A |
| MC1162288 | (Updated) Microsoft Outlook: Declarative Agents in Copilot Chat coming to classic Outlook for Windows | Microsoft Outlook: Declarative Agents in Copilot Chat coming to classic Outlook for Windows | (Updated) Microsoft Outlook: Declarative Agents in Copilot Chat coming to classic Outlook for Windows | N/A |
| MC1162289 | (Updated) Microsoft Outlook: Summarize email with Copilot chat | Microsoft Outlook: Summarize email with Copilot chat | (Updated) Microsoft Outlook: Summarize email with Copilot chat | N/A |
| MC792601 | (Updated) SharePoint Framework domain isolated web parts retirement | SharePoint Framework domain isolated web parts retirement | (Updated) SharePoint Framework domain isolated web parts retirement | N/A |
CW40 New Office 365 Message Center items
| MC ID | MC Title | MC Category | MC Workload | MC Major Change | MC Action required by |
|---|---|---|---|---|---|
| MC1162083 | Microsoft 365 Copilot: Agent Mode available in Excel Labs add-in (Frontier preview) | Plan For Change | Microsoft 365 for the web | False | N/A |
| MC1162297 | New support for historical data uploads in Organizational Data in Microsoft 365 | Plan For Change | Microsoft 365 suite | False | N/A |
| MC1162291 | Microsoft Copilot Studio: Agent ownership reassignment | Stay Informed | Microsoft 365 suite | False | N/A |
| MC1162289 | (Updated) Microsoft Outlook: Summarize email with Copilot chat | Stay Informed | Exchange Online | False | N/A |
| MC1162288 | (Updated) Microsoft Outlook: Declarative Agents in Copilot Chat coming to classic Outlook for Windows | Stay Informed | Exchange Online | False | N/A |
| MC1162285 | Microsoft Copilot Studio icon update | Stay Informed | Microsoft Copilot (Microsoft 365), Microsoft 365 Copilot Chat | False | N/A |
| MC1162276 | (Updated) Microsoft Teams: Trust Indicators – a new way of representing users outside your organization | Stay Informed | Microsoft Teams | False | N/A |
| MC1162275 | Product transitions to the cloud.microsoft domain – September 2025 | Plan For Change | Microsoft 365 apps | False | N/A |
| MC1162274 | New post-deployment configuration for unified sensors (preview) | Stay Informed | Microsoft Defender XDR | False | N/A |
| MC1162273 | Microsoft Purview | eDiscovery - Metadata field enhancements in process reporting | Stay Informed | Microsoft Purview | False | N/A |
| MC1163100 | Power Automate for desktop - Assign custom names to actions in desktop flows | Stay Informed | Microsoft Power Automate | False | N/A |
| MC1163091 | Power Automate – Enable version control for desktop flows | Stay Informed | Microsoft Power Automate | False | N/A |
| MC1162966 | Microsoft Purview | Information Protection: Updates to Microsoft built-in Sensitive Information Types (SITs) | Stay Informed | Microsoft Purview | False | N/A |
| MC1162965 | Microsoft 365 Copilot: Version history now available in Copilot Pages | Stay Informed | Microsoft Copilot (Microsoft 365), Microsoft 365 Copilot Chat | False | N/A |
| MC1162964 | New in Teams – open channels in dedicated windows | Stay Informed | Microsoft Teams | False | N/A |
| MC1162959 | Microsoft Teams admin center: Speed up app reviews with trust-based filters | Stay Informed | Microsoft Teams | False | N/A |
| MC1162958 | Viva Engage - Retirement of themes in user settings | Plan For Change | Microsoft Viva | True | N/A |
| MC1162957 | Public preview: New content explorer experience for cases in Insider Risk Management | Stay Informed | Microsoft Purview | False | N/A |
| MC1162951 | Microsoft Teams admin center: Expanded security and compliance info for more apps and agents | Plan For Change | Microsoft Teams | False | N/A |
| MC1162950 | Reminder: Update Email Configurations for Viva Engage Email Domain Migration | Plan For Change | Microsoft Viva | False | N/A |
| MC1162947 | Windows 11, version 25H2 is now available via feature updates | Stay Informed | Microsoft Intune | False | N/A |
| MC1162945 | Plan for Change: Removing Intune guided scenarios from the Intune admin center in January 2026 | Plan For Change | Microsoft Intune | False | N/A |
| MC1163640 | Updates available for Microsoft 365 Apps for Current Channel | Stay Informed | Microsoft 365 apps | False | N/A |
| MC1163922 | Upcoming Secure by Default Settings Changes for Exchange and Teams APIs | Plan For Change | Exchange Online, Microsoft Teams | True | N/A |
| MC1163778 | Microsoft 365: Visual refresh of app icons | Stay Informed | Microsoft 365 apps | False | N/A |
| MC1163766 | New policy setting to require explicit consent for recording and transcription in Teams 1:1 calls | Plan For Change | Microsoft Teams | False | N/A |
| MC1163763 | Microsoft Secure Score: New recommendations for Microsoft Defender for Endpoint | Stay Informed | Microsoft Defender XDR | False | N/A |
| MC1163761 | Improved device selection on Microsoft Teams meeting join screen | Stay Informed | Microsoft Teams | False | N/A |
| MC1163760 | New support for HR and employee profile data in Microsoft 365 Copilot connectors | Plan For Change | Microsoft 365 suite | True | N/A |
| MC1163757 | Microsoft Exchange Online: New limit for dynamic distribution groups (DDGs) for Microsoft 365 operated by 21Vianet | Plan For Change | Exchange Online | False | 11/01/2025 |
| MC1163756 | Outlook for Android will require Android 10.0 or higher starting January 2026 | Plan For Change | Microsoft 365 apps | False | 01/04/2026 |
| MC1163754 | Enhancements to the Deep Analysis tab of Email Entity page by Microsoft Defender for Office 365 | Stay Informed | Microsoft Defender XDR | False | N/A |
| MC1163753 | Outlook on the web activity-based timeout is retiring | Plan For Change | Exchange Online, Microsoft 365 for the web | True | N/A |
| MC1164381 | OneDrive: Simplified file transfer for departing employees | Stay Informed | Microsoft OneDrive | False | N/A |
| MC1164380 | Microsoft 365 Copilot: Information about billing plan setup for Microsoft 365 Copilot Chat | Plan For Change | Microsoft 365 Copilot Chat | False | 10/03/2025 |
| MC1164379 | Microsoft Teams admin center: Permission and privilege levels for apps and agents | Stay Informed | Microsoft Teams | False | N/A |
| MC1164375 | Retirement of "When Sending a Message" Group Policy in Classic Outlook for Windows | Prevent Or Fix Issue | Microsoft 365 apps | True | 01/12/2026 |
