from 06/09/2025 to 06/15/2025
31 Office 365 Message Center Items were changed and
20 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 End Time changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1013461 | (Updated) Microsoft Teams: Customize the location of notifications in Teams for the web | 07/07/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC1019312 | (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions | 09/08/2025 09:00:00 | 2025-10-06T09:00:00Z | N/A |
| MC1024395 | (Updated) Transitioning from user's OneDrive to SharePoint for Whiteboards created in Teams Channels | 07/07/2025 09:00:00 | 2025-09-01T09:00:00Z | N/A |
| MC1053652 | (Updated) Microsoft Viva Pulse: New Delegation feature | 12/29/2025 08:00:00 | 2025-08-25T09:00:00Z | N/A |
| MC1053653 | (Updated) Teams Meetings Copilot response can be shared to external apps (Word or Excel) | 06/09/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC1055557 | (Updated) SharePoint Online: Content Security Policy Control in Tenant Administration | 07/14/2025 09:00:00 | 2025-08-25T09:00:00Z | N/A |
| MC1084035 | (Updated) Microsoft Teams: Pop out your core apps into a new window. | 07/28/2025 09:00:00 | 2025-10-27T08:00:00Z | N/A |
| MC718553 | (Updated) Microsoft Teams: Change background while recording on phone | 07/07/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC795355 | (Updated) Microsoft Teams admin center: App centric management for app installation and changes to app setup policies | 07/07/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC803014 | (Updated) Microsoft 365 Word, Excel, and PowerPoint for web: Enhanced File menu and easier file renaming | 07/07/2025 09:00:00 | 2025-09-01T09:00:00Z | N/A |
| MC894581 | (Updated) Microsoft Teams: Performance improvements for meetings in Chrome web browser for guests | 07/07/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC898391 | (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests | 07/07/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC956699 | (Updated) Microsoft Teams: Forward messages with app cards | 06/16/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC966633 | (Updated) Microsoft Teams: Meeting recap can be shared as a link | 07/07/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC967240 | (Updated) Microsoft Teams: File open preferences will extend to more Microsoft 365 apps | 07/07/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC992216 | (Updated) Microsoft Teams: Third-party chat and meeting keyboard shortcut support | 07/14/2025 09:00:00 | 2025-08-11T09:00:00Z | N/A |
| MC993226 | (Updated) Microsoft Teams: New location sharing settings for emergency calls and other features | 07/07/2025 09:00:00 | 2025-09-08T09:00:00Z | N/A |
MC How Affect changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1041456 | (Updated) New Microsoft Outlook and Outlook for the web: New setting to enable two-click view for encrypted emails | With this two-click feature enabled, users will be required to select View message for every encrypted email, and then the email will render. This feature ensures that users deliberately access encrypted email content, reducing the risk of accidental exposure, especially in unsecured environments like public spaces or during screen sharing:
Admins can find the TwoClickMailPreviewEnabled setting in the Microsoft Azure directory. This setting is a Boolean type with default = 0, which means the experience is disabled by default. To enable the feature for all users in your tenant, set value = 1. |
With this two-click feature enabled, users will be required to select View message for every encrypted email, and then the email will render. This feature ensures that users deliberately access encrypted email content, reducing the risk of accidental exposure, especially in unsecured environments like public spaces or during screen sharing:
Admins can find the TwoClickMailPreviewEnabled setting in the Microsoft Azure directory. This setting is a Boolean type with default = 0, which means the experience is disabled by default. To enable the feature for all users in your tenant, set value = 1. |
N/A |
| MC1045211 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | Viva Engage will no longer support private content mode, present within the classic Yammer admin center. Verified admins will no longer be able to enable or disable this feature. If the feature was left on by a verified admin, then it will be disabled for them. There are alternative methods that can fulfill the needs previously met by private content mode: Viewing private community content without being a member: Users with the Global Administrator or Groups Administrator role can search for private communities within Engage and join these communities without requiring explicit approvals. Learn more about other Entra ID roles here. Viewing community admins and members for private communities without being a member: Since Engage Communities are backed by Microsoft 365 groups, the list of group owners and group members are visible within Entra ID for all users. Learn more about group management here. Handling legal/audit cases in Engage: Compliance administrators, eDiscovery managers, and eDiscovery administrators can access, search, and export private community and private message content on Viva Engage. Learn more about our eDiscovery standard solution here. Admins are also able to perform network data exports which can be manipulated to handle other advanced use cases. |
Viva Engage will no longer support private content mode, present within the classic Yammer admin center. Verified admins will no longer be able to enable or disable this feature. There are alternative methods that can fulfill the needs previously met by private content mode: Viewing private community content without being a member: Users with the Global Administrator or Groups Administrator role can search for private communities within Engage and join these communities without requiring explicit approvals. Learn more about other Entra ID roles here. Viewing community admins and members for private communities without being a member: Since Engage Communities are backed by Microsoft 365 groups, the list of group owners and group members are visible within Entra ID for all users. Learn more about group management here. Handling legal/audit cases in Engage: Compliance administrators, eDiscovery managers, and eDiscovery administrators can access, search, and export private community and private message content on Viva Engage. Learn more about our eDiscovery standard solution here. Enable Supervisor mode when calling Yammer REST APIs: If you rely on the Yammer REST APIs to programmatically fetch private community content, you may continue to do so by enabling supervisor mode, as documented here. Admins are also able to perform network data exports which can be manipulated to handle other advanced use cases. |
N/A |
| MC1053652 | (Updated) Microsoft Viva Pulse: New Delegation feature | Delegation will on by default. Delegates will be able to: Create pulses View past pulse reports Send pulses Resend pulses Schedule pulses Delegates cannot view or respond to 1:1 conversations. |
Delegation is turned on by default in tenants. Admins can manage delegation at the tenant level, group level using Microsoft Entra ID groups or Microsoft 365 groups, or at the user level for maximum flexibility through centralized feature access management. You can create and update policies in the Microsoft 365 admin center or in PowerShell. Use the FeatureID value PulseDelegation to configure delegation in the tenant. See Control access to features in Viva to learn more. Delegates will be able to: Create and send Pulses on behalf of the delegator. Survey recipients for Pulses sent by the delegate will see the email and Teams notifications indicate that the Pulse was sent on behalf of the delegator. View all Pulses sent or drafted. View all Pulse reports. Delegates cannot view or respond to confidential conversations and cannot share Pulse reports. |
N/A |
| MC1069555 | (Updated) Microsoft Teams: Send messages to attendees in the meeting lobby with Lobby chat | Admin controls: After this rollout, the policy for Lobby chat will be on by default in the TAC. Admins can enable or disable Lobby chat with a meeting policy in the TAC. Under Meeting policies > Global (Org-wide default) > Meeting engagement, admins will find a new toggle option for Organizers can chat with lobby participant. When the option is enabled, participants who can't bypass the lobby due to meeting policy will be able to view messages sent by the organizer in a Lobby chat. To enable this policy, Meeting chat in the TAC must be set to On for everyone or On for everyone but anonymous users.
Meeting organizer experience: When someone joins the lobby, the meeting organizer will see a new Lobby tab in their Chat experience (meeting chat, one-on-one chat, or group chats). The meeting organizer will be able to send one-way messages to attendees in the lobby in the Lobby tab: Lobby attendee experience: When the meeting organizer sends a message to the lobby, a new Lobby chat panel will open in the right panel of the pre-join screen and display the message. Lobby attendees cannot reply to these messages |
Admin controls: After this rollout, the policy for Lobby chat will be on by default in the TAC. Admins can enable or disable Lobby chat with a meeting policy in the TAC. Under Meeting policies > Global (Org-wide default) > Meeting engagement, admins will find a new toggle option for Organizers can chat with lobby participant. When the option is enabled, participants who can't bypass the lobby due to meeting policy will be able to view messages sent by the organizer in a Lobby chat. To enable this policy, Meeting chat in the TAC must be set to On for everyone or On for everyone but anonymous users.
Meeting organizer experience: When someone joins the lobby, the meeting organizer will see a new Lobby tab in their Chat experience. The meeting organizer will be able to send one-way messages to attendees in the lobby in the Lobby tab: Lobby attendee experience: When the meeting organizer sends a message to the lobby, a new Lobby chat panel will open in the right panel of the pre-join screen and display the message. Lobby attendees cannot reply to these messages |
N/A |
| MC1089315 | Resharing to external users required after enabling Microsoft SharePoint integration with Microsoft Entra B2B | This change only impacts organizations that have already enabled or plan to enable SharePoint and OneDrive integration with Microsoft Entra B2B. After integration, all new external sharing will use Microsoft Entra B2B Invitation Manager. Previously shared links that used the SharePoint One-Time Passcode (OTP) will no longer work. External users attempting to use these older links will encounter the error message "Sorry, something went wrong. This organization has updated its guest access settings. To access this item, please contact the person who shared it with you and ask them to reshare it with you." Impact to end users: |
All users in every tenant that has already enabled or in future, will enable SharePoint integration with Entra B2B are impacted. Your external users will lose access to all the files, folders and sites shared before enabling this integration. To give access again, resharing is required. After the integration is enabled, external sharing will use Microsoft Entra B2B Invitation Manager External users attempting to use older links will encounter an error message "Sorry, something went wrong. This organization has updated its guest access settings. To access this item, please contact the person who shared it with you and ask them to reshare it with you. Impact to end users: |
06/30/2025 |
| MC786329 | (Updated) Exchange Online to retire Basic Auth for Client Submission (SMTP AUTH) | In September 2024, we will update the SMTP AUTH Clients Submission Report in the Exchange admin center to show if Basic auth or OAuth is being used to submit email to Exchange Online. In January 2025, we will send a Message Center post to tenants who are using Basic auth with Client Submission (SMTP AUTH) to alert them to the upcoming change. In August 2025, about 30 days before we disable Basic auth we will send another Message Center post to tenants who are still using Basic auth with Client Submission (SMTP AUTH). During September 2025, we will remove support for Basic auth with the Client Submission (SMTP AUTH) endpoints: smtp.office365.com smtp-legacy.office365.com Once Basic auth is permanently disabled, any clients or apps connecting using Basic auth with Client Submission (SMTP AUTH) will receive this response: 550 5.7.30 Basic authentication is not supported for Client Submission. |
The SMTP AUTH Clients Submission Report in the Exchange admin center has been updated to show if Basic auth or OAuth is being used to submit email to Exchange Online. Starting in July 2025, we will send monthly Message Center posts to tenants who are using Basic auth with Client Submission (SMTP AUTH) to alert them to the upcoming change. Starting March 1st 2026 (previously September 2025) we will gradually start rejecting Basic Auth requests to the Client Submission (SMTP AUTH) endpoints, increasing to 100% rejection by the end of the April 2026. The Client Submission (SMTP AUTH) endpoints in scope for this change are: * smtp.office365.com * smtp-legacy.office365.com Once Basic auth is permanently disabled, any clients or apps connecting using Basic auth with Client Submission (SMTP AUTH) will receive this response: * 550 5.7.30 Basic authentication is not supported for Client Submission. |
N/A |
MC Messages changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1013461 | (Updated) Microsoft Teams: Customize the location of notifications in Teams for the web | Updated May 12, 2025: We have updated the timeline below. Thank you for your patience. Microsoft Teams will soon allow users to personalize the placement of notifications on their screens. Users will be able to choose from four options (bottom right, top right, bottom left, or top left) to make notifications more convenient and less disruptive, enhancing both focus and productivity. This message applies to Teams for the web. This message is associated with Microsoft 365 Roadmap ID 480720. [When this will happen:] Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 and expect to complete by late May 2025 (previously late April). |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Microsoft Teams will soon allow users to personalize the placement of notifications on their screens. Users will be able to choose from four options (bottom right, top right, bottom left, or top left) to make notifications more convenient and less disruptive, enhancing both focus and productivity. This message applies to Teams for the web. This message is associated with Microsoft 365 Roadmap ID 480720. [When this will happen:] Targeted Release: We will begin rolling out early April 2025 and expect to complete by mid-April 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out mid-April 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC1019312 | (Updated) Microsoft Teams: Meeting participants can request collaborative annotation sessions | Updated May 23, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen. This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.) This message is associated with Microsoft 365 Roadmap ID 89975. [When this will happen:] Targeted Release: We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-July 2025 and expect to complete by late July 2025. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Meeting participants will be able to request an annotation session while someone else is sharing their screen. This message applies to Teams for Windows desktop and Teams for Mac desktop. (Users can view and annotate in Teams on the web but cannot initiate annotations.) This message is associated with Microsoft 365 Roadmap ID 89975. [When this will happen:] Targeted Release: We will begin rolling out early August 2025 and expect to complete by mid-August 2025. General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-August2025 and expect to complete by late August 2025. |
N/A |
| MC1024395 | (Updated) Transitioning from user's OneDrive to SharePoint for Whiteboards created in Teams Channels | Updated April 18, 2025: We have updated the rollout timeline below. Thank you for your patience. We are updating the storage location for Whiteboards created from the Teams Channel Tab App. Previously, these whiteboards were saved on the initiator's OneDrive, which caused access issues due to sharing settings, information barriers, or conditional access policies. To resolve these issues and align with the behavior of other M365 apps, whiteboards initiated from the Teams Channel Tab App will now be stored in the corresponding SharePoint site of the Teams Channel (also known as the channel site). This change ensures seamless access for all channel members while adhering to set policies. [When this will happen:] We will begin rolling out in early May 2025 (previously early April) and expect to complete by late May 2025 (previously late April). |
Updated June 10, 2025: We have updated the timeline below. Thank you for your patience. We are updating the storage location for Whiteboards created from the Teams Channel Tab App. Previously, these whiteboards were saved on the initiator's OneDrive, which caused access issues due to sharing settings, information barriers, or conditional access policies. To resolve these issues and align with the behavior of other M365 apps, whiteboards initiated from the Teams Channel Tab App will now be stored in the corresponding SharePoint site of the Teams Channel (also known as the channel site). This change ensures seamless access for all channel members while adhering to set policies. [When this will happen:] We will begin rolling out in early May 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC1025217 | (Updated) Microsoft Teams: In channels, the "Shared" tab (formerly the "Files" tab) will have new capabilities | Updated May 14, 2025: We have updated the timeline below. 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 July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide): We will begin rolling out mid-July 2025 and expect to complete by mid-August 2025. |
Updated June 11, 2025: We have updated the timeline below. 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 August 2025 and expect to complete by mid-August 2025. General Availability (Worldwide): We will begin rolling out late August 2025 and expect to complete by mid-September 2025. |
N/A |
| MC1036575 | (Updated) Microsoft Viva Engage: External Networks are being modernized | Updated May 9, 2025: We have updated the timeline below. Thank you for your patience. The modern Viva Engage user experience is available now for External, and you are being asked to initiate migration. This message provides details on adopting the modern version of External Networks. In addition to the user experience changes, we are building modern External Networks on top of native Microsoft 365 services just like your Engage home network experience. This increases the level of compliance and enhances the admin experience by enabling Microsoft 365 admin features that are available on tenants. IMPORTANT: When requested in future communications, admins must choose to migrate External Networks to the modern platform. Failure to respond will result in the legacy External Networks being retired and deleted. [When this will happen:] This retirement will occur on June 15, 2025 (previously June 1). If you need additional time, we ask you to please contact your Microsoft Account representative and request them to submit a 60-day extension, which would then allow you to complete the move by August 15th 2025. If you have already reached out to Microsoft and your exception has been approved, you do not need to submit or apply for the 60-day extension. |
Updated June 10, 2025: We have updated the timeline below. Thank you for your patience. The modern Viva Engage user experience is available now for External, and you are being asked to initiate migration. This message provides details on adopting the modern version of External Networks. In addition to the user experience changes, we are building modern External Networks on top of native Microsoft 365 services just like your Engage home network experience. This increases the level of compliance and enhances the admin experience by enabling Microsoft 365 admin features that are available on tenants. IMPORTANT: When requested in future communications, admins must choose to migrate External Networks to the modern platform. Failure to respond will result in the legacy External Networks being retired and deleted. New in this update: The cutoff date for filing any extension request is by June 15th. Any external network that hasn't requested an extension by this date will no longer be accessible starting July 7th, 2025. [When this will happen:] This retirement will occur on June 15, 2025. The extra 15 days is being given to allow for any networks that have not requested for the extension to perform any data export. If you need additional time, we ask you to please contact your Microsoft Account representative and request them to submit a 60-day extension, which would then allow you to complete the move by August 15th 2025. If you have already reached out to Microsoft and your exception has been approved, you do not need to submit or apply for the 60-day extension. |
06/01/2025 |
| MC1041456 | (Updated) New Microsoft Outlook and Outlook for the web: New setting to enable two-click view for encrypted emails | Updated June 3, 2025: We have updated the timeline below. Thank you for your patience. New Outlook for Windows desktop and Outlook for the web will soon support a two-click view for encrypted emails, which requires user confirmation before allowing access to encrypted emails. As an admin, you can enable the two-click feature for your users. This message is associated with Microsoft 365 Roadmap ID 483883. [When this will happen:] General Availability (Worldwide): We will begin rolling out early April 2025 and expect to complete by late April 2025. General Availability (GCC): We will begin rolling out early May 2025 and expect to complete by late May 2025. General Availability (Worldwide, GCC): For Android and iOS, we will begin rolling out mid-June 2025 and expect to complete by late June 2025. |
Updated June 11, 2025: We have updated the content. Thank you for your patience. New Outlook for Windows desktop, Outlook for the web, Outlook iOS and Outlook Android will soon support a two-click view for encrypted emails, which requires user confirmation before allowing access to encrypted emails. As an admin, you can enable the two-click feature for your users. This message is associated with Microsoft 365 Roadmap ID 483883. [When this will happen:] General Availability (Worldwide): We will begin rolling out early April 2025 and expect to complete by late April 2025. General Availability (GCC): We will begin rolling out early May 2025 and expect to complete by late May 2025. General Availability (Worldwide, GCC): For Android and iOS, we will begin rolling out mid-June 2025 and expect to complete by late June 2025. |
N/A |
| MC1045211 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | In alignment with Microsoft 365 core workload administration best practices private content mode will be retired as of June 30th, 2025. This feature has been utilized for specific use cases related to Viva Engage administration and management, and we have outlined alternative solutions for these scenarios in the communication below. This applies to Engage on web, Engage on Teams and Engage on outlook. [When this will happen:] (Worldwide) The feature will be completely retired by June 30th, 2025 |
Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. In alignment with Microsoft 365 core workload administration best practices, the private content mode user experience on the classic Yammer admin center will be retired as of June 30th, 2025. This feature has been utilized for specific use cases related to Viva Engage administration and management, and we have outlined alternative solutions for these scenarios in the communication below. This applies to Engage on web, Engage on Teams and Engage on outlook. [When this will happen:] General availability (Worldwide): The feature will be retired by June 30th, 2025. |
N/A |
| MC1045211 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. In alignment with Microsoft 365 core workload administration best practices, the private content mode user experience on the classic Yammer admin center will be retired as of June 30th, 2025. This feature has been utilized for specific use cases related to Viva Engage administration and management, and we have outlined alternative solutions for these scenarios in the communication below. This applies to Engage on web, Engage on Teams and Engage on outlook. [When this will happen:] General availability (Worldwide): The feature will be retired by June 30th, 2025. |
Updated June 12, 2025: We have updated the timeline below. Thank you for your patience. In alignment with Microsoft 365 core workload administration best practices, the private content mode user experience on the classic Yammer admin center will be retired as of June 30th, 2025. This feature has been utilized for specific use cases related to Viva Engage administration and management, and we have outlined alternative solutions for these scenarios in the communication below. This applies to Engage on web, Engage on Teams and Engage on outlook. [When this will happen:] General availability (Worldwide): The feature will be retired by June 30th, 2025. |
N/A |
| MC1045222 | (Updated) Ability to Stop Copilot while it is generating a response | Updated May 16, 2025: We have updated the timeline below. Thank you for your patience. Users will have the ability to 'Stop generating' a Copilot response. This message is associated with Microsoft 365 Roadmap ID 325948 [When this will happen:] Targeted Release: We will begin rolling out late May 2025 (previously early May) and expect to complete by late May 2025 (previously mid-May). General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. |
Updated June 12, 2025: We have updated the timeline below. Thank you for your patience. Users will have the ability to 'Stop generating' a Copilot response. This message is associated with Microsoft 365 Roadmap ID 325948 [When this will happen:] Targeted Release: We will begin rolling out late May 2025 (previously early May) and expect to complete by late May 2025 (previously mid-May). General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC1047929 | (Updated) Microsoft Viva Engage app for iOS/Android will have a shorter name in app stores | Updated May 15, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for the Microsoft Viva Engage app for iOS and Android: We will shorten the name for this app from "Viva Engage" to "Engage." The change will display in the Apple App Store and Google Play Store and in the installed app. [When this will happen:] General Availability (Worldwide): We will begin rolling out late May 2025 (previously early May) and expect to complete by late June 2025 (previously mid-May). |
Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for the Microsoft Viva Engage app for iOS and Android: We will shorten the name for this app from "Viva Engage" to "Engage." The change will display in the Apple App Store and Google Play Store and in the installed app. [When this will happen:] General Availability (Worldwide): We will begin rolling out mid-June 2025 (previously late May) and expect to complete by late June 2025 (previously mid-May). |
N/A |
| MC1053645 | (Updated) Microsoft Teams: Create new channels faster from the "New items" menu at top of the list of chats and channels | Updated May 13, 2025: We have updated the title and description below. Thank you for your patience. Coming soon in Microsoft Teams: When creating a new channel, creators can select any team to host the channel -- including teams with no shown channels -- provided they have the necessary permissions to create channels in that team. Previously, only teams with shown channels were included in the list of host teams. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. This message is associated with Microsoft 365 Roadmap ID 479744. [When this will happen:] Targeted Release: We will begin rolling out early May 2025 and expect to complete by early May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Coming soon in Microsoft Teams: When creating a new channel, creators can select any team to host the channel -- including teams with no shown channels -- provided they have the necessary permissions to create channels in that team. Previously, only teams with shown channels were included in the list of host teams. This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web. This message is associated with Microsoft 365 Roadmap ID 479744. [When this will happen:] Targeted Release: We will begin rolling out early May 2025 and expect to complete by early May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC1053652 | (Updated) Microsoft Viva Pulse: New Delegation feature | Updated April 24, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. Coming soon to Microsoft Viva Pulse: A new Delegation feature. Users in your tenant will be able to assign other users as delegates to create and send pulses on their behalf. A delegator can have a maximum of 5 delegates. A user can only be a delegate of one individual. This message applies to Viva Pulse in Windows desktop and Viva Pulse in Mac desktop. To use this feature, users must have a license for Viva or Microsoft 365 Copilot. This message is associated with Microsoft 365 Roadmap ID 479753. [When this will happen:] General Availability (Worldwide): We will communicate via Message center when we are ready to proceed. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Major update: Microsoft Viva Pulse is rolling out a new delegation feature in July 2025 that enables users in your tenant to assign other users as delegates to take actions on their behalf. This feature is designed to support executive assistants, chiefs of staff, and other designated roles who act on behalf of organizational leaders in collecting and analyzing feedback. Delegation in Viva Pulse allows a user (the delegator) to authorize another user (the delegate) to manage the Pulse survey lifecycle on their behalf. Delegates can create, send, and manage Pulses, while the delegator retains ownership and visibility into all activity. To use this feature, users must have a license for Viva Pulse via Microsoft Viva Suite, Microsoft Viva Workplace Analytics and Employee Feedback, or Microsoft 365 Copilot. This message is associated with Microsoft 365 Roadmap ID 479753. [When this will happen:] General Availability (Worldwide): We will roll out the delegation feature in mid-July 2025. |
N/A |
| MC1053653 | (Updated) Teams Meetings Copilot response can be shared to external apps (Word or Excel) | Microsoft 365 Copilot responses in Microsoft Teams meetings can be shared to external apps (Word or Excel). Responses generated by Copilot in Meetings will come with a button to Open in another app. Although this will start with Word and Excel, more apps will be added in the future. The Open in button will show up when: A response has more than the set number of characters (1,300), which will make it long enough to warrant editing in a document. Shorter responses can always be copied/pasted anywhere outside of Teams, as long as the meeting policy allows. A response has a table, which will allow it to be exported to Excel if the meeting policy allows. Responses will only be able to be exported if the meeting policy allows copying or exporting of Copilot responses and will respect the sensitivity label of the meeting (sensitivity labels are available to Teams Premium customers). This message is associated with Microsoft 365 Roadmap ID 481352. [When this will happen:] Targeted release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Microsoft 365 Copilot responses in Microsoft Teams meetings can be shared to external apps (Word or Excel). Responses generated by Copilot in Meetings will come with a button to Open in another app. Although this will start with Word and Excel, more apps will be added in the future. The Open in button will show up when: A response has more than the set number of characters (1,300), which will make it long enough to warrant editing in a document. Shorter responses can always be copied/pasted anywhere outside of Teams, as long as the meeting policy allows. A response has a table, which will allow it to be exported to Excel if the meeting policy allows. Responses will only be able to be exported if the meeting policy allows copying or exporting of Copilot responses and will respect the sensitivity label of the meeting (sensitivity labels are available to Teams Premium customers). This message is associated with Microsoft 365 Roadmap ID 481352. [When this will happen:] Targeted release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC1055557 | (Updated) SharePoint Online: Content Security Policy Control in Tenant Administration | Updated May 21, 2025: We have updated the content Thank you for your patience. SharePoint Online Tenant Administrators can now allow script sources for modern pages in SharePoint sites. This feature is particularly useful in scenarios where modern pages have custom code that loads scripts (e.g., TypeScript code) from external sources like a content delivery network (CDN). SharePoint will now report to administrators where sources that have not been allowed are loaded from, providing a way for administrators to identify those sources and take action. Tenant Administrators can also enforce browsers to only load scripts from allowed sources. This behavior can be enabled using SharePoint Online Management Shell. [When this will happen:] Targeted Release: We will begin rolling out on late March 2025 and expect to complete by early April 2025. General Availability (Worldwide): We will begin rolling out on late April 2025 and expect to complete by late April 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out on late April 2025 and expect to complete by early June 2025 (previously mid-May). |
Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. SharePoint Online Tenant Administrators can now allow script sources for modern pages in SharePoint sites. This feature is particularly useful in scenarios where modern pages have custom code that loads scripts (e.g., TypeScript code) from external sources like a content delivery network (CDN). SharePoint will now report to administrators where sources that have not been allowed are loaded from, providing a way for administrators to identify those sources and take action. Tenant Administrators can also enforce browsers to only load scripts from allowed sources. This behavior can be enabled using SharePoint Online Management Shell. [When this will happen:] Targeted Release: We will begin rolling out on late March 2025 and expect to complete by early April 2025. General Availability (Worldwide): We will begin rolling out on late April 2025 and expect to complete by late April 2025. General Availability (GCC, GCC High, DoD): We will begin rolling out on late April 2025 and expect to complete by late June 2025 (previously early June). |
N/A |
| MC1059668 | (Update) Microsoft Teams: Meeting option suggestions in classic Microsoft Outlook for Windows | Updated June 6, 2025: Due to significant delays in the release train and the need to ensure adequate stabilization time, we are postponing the release of this feature to maintain quality and reliability. Thank you for your patience. Coming soon: The Microsoft Teams Meeting add-in in classic Microsoft Outlook for Windows desktop will suggest meeting options to meeting organizers based on meeting details, helping organizers easily schedule meetings with optimized settings from the scheduling form. This message is associated with Microsoft 365 Roadmap ID 487858. [When this will happen:] General Availability (Worldwide): We will begin rolling out mid-July 2025 (previously early June) and expect to complete by late July 2025 (previously mid-June). |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Coming soon: The Microsoft Teams Meeting add-in in classic Microsoft Outlook for Windows desktop will suggest meeting options to meeting organizers based on meeting details, helping organizers easily schedule meetings with optimized settings from the scheduling form. This message is associated with Microsoft 365 Roadmap ID 487858. [When this will happen:] Targeted Release: We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability: We will begin rolling out mid-July 2025 and expect to complete by late July 2025. |
N/A |
| MC1069555 | (Updated) Microsoft Teams: Send messages to attendees in the meeting lobby with Lobby chat | Updated May 30, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Meeting organizers will be able to send one-way messages to attendees in the meeting lobby using the Lobby chat. The Lobby chat is intended to optimize the lobby experience for all participants, ensuring that organizers are better equipped to run external meetings and external attendees are well informed about the meeting when it begins. This feature is on by default and admins can choose to disable it in the Teams admin center (TAC). This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams for iOS/Android. This message is associated with Microsoft 365 Roadmap ID 480716. [When this will happen:] Targeted Release: We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. |
Updated June 12, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: Meeting organizers will be able to send one-way messages to attendees in the meeting lobby using the Lobby chat. The Lobby chat is intended to optimize the lobby experience for all participants, ensuring that organizers are better equipped to run external meetings and external attendees are well informed about the meeting when it begins. This feature is on by default and admins can choose to disable it in the Teams admin center (TAC). This message applies to Teams on Desktop, Mac, Web iOS and Android will be released shortly This message is associated with Microsoft 365 Roadmap ID 480716. [When this will happen:] Targeted Release: We will begin rolling out mid-June 2025 and expect to complete by late June 2025. General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by mid-July 2025. |
N/A |
| MC1070846 | Microsoft PowerPoint for Windows: Create a presentation with Microsoft Copilot from the PowerPoint Backstage view | Updated May 29, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft PowerPoint for Windows desktop: Users will be able to create a PowerPoint presentation with Copilot straight from the PowerPoint Backstage view, accessible when you start PowerPoint or when you select the File tab. This feature requires a Microsoft 365 license or a Microsoft Copilot 365 license. This message is associated with Microsoft 365 Roadmap ID 491469. [When this will happen:] Targeted Release: We will begin rolling out early June 2025 (previously mid-May) and expect to complete by mid-July 2025 (previously late May). General Availability (Worldwide): We will begin rolling out mid-June 2025 (previously late May) and expect to complete by late June 2025. |
Updated June 10, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft PowerPoint for Windows desktop: Users will be able to create a PowerPoint presentation with Copilot straight from the PowerPoint Backstage view, accessible when you start PowerPoint or when you select the File tab. This feature requires a Microsoft 365 license and a Microsoft Copilot 365 license. This message is associated with Microsoft 365 Roadmap ID 491469. [When this will happen:] Targeted Release: We will begin rolling out early June 2025 (previously mid-May) and expect to complete by mid-July 2025 (previously late May). General Availability (Worldwide): We will begin rolling out mid-June 2025 (previously late May) and expect to complete by late June 2025. |
N/A |
| MC1070846 | Microsoft PowerPoint for Windows: Create a presentation with Microsoft Copilot from the PowerPoint Backstage view | Updated June 10, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft PowerPoint for Windows desktop: Users will be able to create a PowerPoint presentation with Copilot straight from the PowerPoint Backstage view, accessible when you start PowerPoint or when you select the File tab. This feature requires a Microsoft 365 license and a Microsoft Copilot 365 license. This message is associated with Microsoft 365 Roadmap ID 491469. [When this will happen:] Targeted Release: We will begin rolling out early June 2025 (previously mid-May) and expect to complete by mid-July 2025 (previously late May). General Availability (Worldwide): We will begin rolling out mid-June 2025 (previously late May) and expect to complete by late June 2025. |
Updated June 11, 2025: We have updated the content. Thank you for your patience. Coming soon for Microsoft PowerPoint for Windows desktop: Users will be able to create a PowerPoint presentation with Copilot straight from the PowerPoint Backstage view, accessible when you start PowerPoint or when you select the File tab. This feature requires a Microsoft 365 license and a Microsoft Copilot 365 license. This message is associated with Microsoft 365 Roadmap ID 491469. [When this will happen:] Targeted Release: We will begin rolling out early June 2025 (previously mid-May) and expect to complete by mid-July 2025 (previously late May). General Availability (Worldwide): We will begin rolling out mid-July 2025 (previously late May) and expect to complete by late July 2025. |
N/A |
| MC1077865 | Updated: Microsoft Teams: Introducing the Network Strength Indicator | To improve meeting clarity and reduce confusion caused by connectivity issues, we're adding a new Network Strength Indicator. This message is associated with Microsoft 365 Roadmap ID 414513 [When this will happen:] Targeted Release: We will begin rolling out early July 2025 and expect to complete by late July 2025. General Availability (Worldwide, GCC): We will begin rolling out early August 2025 and expect to complete by early September 2025. |
Updated June 10, 2025: We have updated the timeline below. Thank you for your patience. To improve meeting clarity and reduce confusion caused by connectivity issues, we're adding a new Network Strength Indicator. This message is associated with Microsoft 365 Roadmap ID 414513 [When this will happen:] Targeted Release: We will begin rolling out late August 2025 and expect to complete by early September 2025. General Availability (Worldwide, GCC): We will begin rolling out early September 2025 and expect to complete by mid-September 2025. |
N/A |
| MC1084035 | (Updated) Microsoft Teams: Pop out your core apps into a new window. | Updated May 29, 2025: We have updated the content. Thank you for your patience. Users will have the capability to open their core applications, such as Chat, Teams, and other essential apps, in separate windows by selecting Open in new window from the app's context menu. This latest update facilitates enhanced productivity and provides greater customization of the user's workflow. This improvement enables users to manage their core collaboration applications more efficiently, ultimately leading to a more streamlined and effective work environment. This message is associated with Microsoft 365 Roadmap ID 495003. [When this will happen:] Targeted Release: We will begin rolling out early July 2025 and expect to complete by mid-July 2025. General Availability (Worldwide): We will begin rolling out mid-July 2025 and expect to complete by early August 2025. |
Updated June 10, 2025: We have updated the timeline below. Thank you for your patience. Users will have the capability to open their core applications, such as Chat, Teams, and other essential apps, in separate windows by selecting Open in new window from the app's context menu. This latest update facilitates enhanced productivity and provides greater customization of the user's workflow. This improvement enables users to manage their core collaboration applications more efficiently, ultimately leading to a more streamlined and effective work environment. This message is associated with Microsoft 365 Roadmap ID 495003. [When this will happen:] Targeted Release: We will begin rolling out early September 2025 and expect to complete by mid-September 2025. General Availability (Worldwide): We will begin rolling out mid-September 2025 and expect to complete by early October 2025. |
N/A |
| MC1084635 | (Updated) Event Updates visible in email | Updated June 5, 2025: We have updated the content. Thank you for your patience. If an organizer updates an event that you have been invited to, you will now see Event Updated in the email and the updated location if applicable. This message is associated with Microsoft 365 Roadmap ID 491018 [When this will happen:] General Availability (Worldwide): We will begin rolling out on early June 2025 and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out on early June 2025 and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out on early June 2025 and expect to complete by late July 2025. General Availability (DoD): We will begin rolling out on early June 2025 and expect to complete by late July 2025. |
Updated June 11, 2025: We have updated the timeline below. Thank you for your patience. If an organizer updates an event that you have been invited to, you will now see Event Updated in the email and the updated location if applicable. This message is associated with Microsoft 365 Roadmap ID 491018 [When this will happen:] General Availability (Worldwide): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. General Availability (GCC): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. General Availability (GCC High): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. General Availability (DoD): We will begin rolling out on late June 2025 (previously early June) and expect to complete by late July 2025. |
N/A |
| MC1089315 | Resharing to external users required after enabling Microsoft SharePoint integration with Microsoft Entra B2B | As part of our ongoing efforts to enhance security, we are making a critical change to how Microsoft SharePoint and Microsoft OneDrive integrate with Microsoft Entra B2B. This change affects how external users access previously shared content. [When this will happen:] Effective July 1, 2025, external users will no longer be able to access files, folders, or sites via links that were shared before your organization enabled SharePoint and OneDrive integration with Microsoft Entra B2B. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. As part of our ongoing efforts to enhance security, we are making a critical change to how Microsoft SharePoint and Microsoft OneDrive integrate with Microsoft Entra B2B. This change affects how external users access previously shared content. [When this will happen:] Effective July 1, 2025, external users will no longer be able to access files, folders, or sites via links that were shared before your organization enabled Microsoft SharePoint and OneDrive integration with Microsoft Entra B2B. |
06/30/2025 |
| MC718553 | (Updated) Microsoft Teams: Change background while recording on phone | Updated May 9, 2025: We have updated the rollout timeline below. Thank you for your patience. Users can now record themselves anywhere and share it with coworkers in the Microsoft Teams chat or channel without worrying about the background. Users can now change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on iOS devices. This message is associated with Microsoft 365 Roadmap ID 380852 [When this will happen:] General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early May 2024 (previously late March) and expect to complete by late May 2025 (previously late April). |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Users can now record themselves anywhere and share it with coworkers in the Microsoft Teams chat or channel without worrying about the background. Users can now change their background to any image they want or make the background blurry while recording using their Microsoft Teams camera on iOS devices. This message is associated with Microsoft 365 Roadmap ID 380852 [When this will happen:] General Availability (Worldwide, GCC, GCC High and DoD): We will begin rolling out early May 2024 (previously late March) and expect to complete by late June 2025 (previously late May. |
N/A |
| MC786329 | (Updated) Exchange Online to retire Basic Auth for Client Submission (SMTP AUTH) | Updated October 18, 2024: We have updated the SMTP AUTH Clients Submission Report in the Exchange admin center, adding the Authentication Protocol column to show if Basic auth or OAuth is being used to submit email to Exchange Online. The data will build up over the next 90 days. Thank you for your patience. Today, we are announcing that Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) in September 2025. After this time, applications and devices will no longer be able to use Basic auth as an authentication method and must use OAuth when using SMTP AUTH to send email. Basic auth is a legacy authentication method that sends usernames and passwords in plain text over the network. This makes it vulnerable to credential theft, phishing, and brute force attacks. To improve the protection of our customers and their data, we are retiring Basic auth from Client Submission (SMTP AUTH) and encouraging customers to use modern authentication methods that are more secure. [When this will happen:] We will be making this change in September 2025. |
Updated June 12, 2025: We have delayed the Basic Auth removal from SMTP AUTH Client Submission to begin March 1st 2026 and complete by April 30th 2026 in order to give customers more time to adopt alternatives. Expect no further delays beyond this date. Please review the information below for more details. Updated October 18, 2024: We have updated the SMTP AUTH Clients Submission Report in the Exchange admin center, adding the Authentication Protocol column to show if Basic auth or OAuth is being used to submit email to Exchange Online. The data will build up over the next 90 days. Thank you for your patience. Today, we are announcing that Exchange Online will permanently remove support for Basic authentication with Client Submission (SMTP AUTH) gradually beginning with a small percentage of submission rejections for all tenants on March 1st 2026 and reaching 100% rejections on April 30th 2026, (previously September 2025). After this time, applications and devices will no longer be able to use Basic auth as an authentication method and must use OAuth when using SMTP AUTH to send email. Basic auth is a legacy authentication method that sends usernames and passwords in plain text over the network. This makes it vulnerable to credential theft, phishing, and brute force attacks. To improve the protection of our customers and their data, we are retiring Basic auth from Client Submission (SMTP AUTH) and encouraging customers to use modern authentication methods that are more secure. [When this will happen:] We will be making this change beginning March 1st, 2026, and completing April 30th, 2026 (previously September 2025). |
N/A |
| MC795355 | (Updated) Microsoft Teams admin center: App centric management for app installation and changes to app setup policies | Updated April 2, 2025: We have updated the rollout timeline and phasing below. Thank you for your patience. Coming soon for Microsoft Teams: App centric management for admin app installation introduces new admin settings to control who in the tenant has specific Teams apps preinstalled. Similar to app centric management for app availability, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023), admins will be able to install apps for users, groups, or everyone in the organization. After rollout, app centric management will replace Installed apps in the Teams admin center and give admins the ability to install apps individually. The Installed apps in your app setup policies will be migrated to app centric management based on your current user and group assignments for each policy. The rest of your settings in app setup policies will remain unchanged and will continue to work based on app setup policies, including Pinned apps. After this rollout, you can install Teams apps for selected sets of users, groups, or all users in the organization, and Installed apps in app setup policies will no longer be available. This message is associated with Microsoft 365 Roadmap ID 394274. [When this will happen:] App centric management will roll out in four General Availability phases. Phase 1 | General Availability (Worldwide): We will begin rolling out late July 2024 (previously mid-July) and expect to complete late May 2025 (previously late March) phase applies to tenants who meet both conditions: 1) tenants with no Installed apps in the Global app setup policy and 2) tenants with no custom app setup policies created in the Teams admin center. After rollout, these tenants will have app centric management enabled for their app installs. Admins may see the Manage apps page in read-only mode for a short time. Phase 2 | More details coming soon as a follow up MC post. This phase applies to all remaining tenants. This phase will migrate apps installed for users and groups through Installed apps in app setup policies to app centric management. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Teams: App centric management for admin app installation introduces new admin settings to control who in the tenant has specific Teams apps preinstalled. Similar to app centric management for app availability, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023), admins will be able to install apps for users, groups, or everyone in the organization. After rollout, app centric management will replace Installed apps in the Teams admin center and give admins the ability to install apps individually. The Installed apps in your app setup policies will be migrated to app centric management based on your current user and group assignments for each policy. The rest of your settings in app setup policies will remain unchanged and will continue to work based on app setup policies, including Pinned apps. After this rollout, you can install Teams apps for selected sets of users, groups, or all users in the organization, and Installed apps in app setup policies will no longer be available. This message is associated with Microsoft 365 Roadmap ID 394274. [When this will happen:] App centric management will roll out in four General Availability phases. Phase 1 | General Availability (Worldwide): We will begin rolling out late July 2024 (previously mid-July) and expect to complete late June 2025 (previously late May) phase applies to tenants who meet both conditions: 1) tenants with no Installed apps in the Global app setup policy and 2) tenants with no custom app setup policies created in the Teams admin center. After rollout, these tenants will have app centric management enabled for their app installs. Admins may see the Manage apps page in read-only mode for a short time. Phase 2 | More details coming soon as a follow up MC post. This phase applies to all remaining tenants. This phase will migrate apps installed for users and groups through Installed apps in app setup policies to app centric management. |
N/A |
| MC803014 | (Updated) Microsoft 365 Word, Excel, and PowerPoint for web: Enhanced File menu and easier file renaming | Updated April 22, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Word for the web, Microsoft Excel for the web, and Microsoft PowerPoint for the web: An enhanced File menu, so users can more easily create, open, share, export, and manage files. We have also updated the autosave experience and made file renaming more efficient. [When this will happen:] Targeted Release: We began rolling out mid-May 2024 and expect to complete by late July 2024. General Availability (Worldwide): We will begin rolling out early August 2024 and expect to complete by late May 2025 (previously mid-April). |
Updated June 10, 2025: We have updated the timeline below. Thank you for your patience. Coming soon for Microsoft Word for the web, Microsoft Excel for the web, and Microsoft PowerPoint for the web: An enhanced File menu, so users can more easily create, open, share, export, and manage files. We have also updated the autosave experience and made file renaming more efficient. [When this will happen:] Targeted Release: We began rolling out mid-May 2024 and expect to complete by late July 2024. General Availability (Worldwide): We will begin rolling out early August 2024 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC894581 | (Updated) Microsoft Teams: Performance improvements for meetings in Chrome web browser for guests | Updated May 9, 2025: We have updated the timeline below. Thank you for your patience. Anonymous users (guests) who join Microsoft Teams meetings in the Chrome web browser will soon experience performance improvements. This message is associated with Microsoft 365 Roadmap ID 401116. [When this will happen:] Targeted Release: We will begin rolling out early November and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024. General Availability (GCC, GCC High and DoD): We will begin rolling out early January 2025 and expect to complete by late May 2025 (previously late April). |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Anonymous users (guests) who join Microsoft Teams meetings in the Chrome web browser will soon experience performance improvements. This message is associated with Microsoft 365 Roadmap ID 401116. [When this will happen:] Targeted Release: We will begin rolling out early November and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024. General Availability (GCC, GCC High and DoD): We will begin rolling out early January 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC898391 | (Updated) Microsoft Teams: Performance improvements for meetings in Edge web browser for guests | Updated May 9, 2025: We have updated the timeline below. Thank you for your patience. Anonymous users (guests) who join Microsoft Teams meetings in the Microsoft Edge for Business web browser will soon experience performance improvements. They will be able to join meetings faster. This message is associated with Microsoft 365 Roadmap ID 401117. [When this will happen:] Targeted Release: We will begin rolling out early November 2024 and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024. General Availability (GCC, GCC High, and DoD): We will begin rolling out early January 2025 and expect to complete by late May 2025 (previously late April). |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Anonymous users (guests) who join Microsoft Teams meetings in the Microsoft Edge for Business web browser will soon experience performance improvements. They will be able to join meetings faster. This message is associated with Microsoft 365 Roadmap ID 401117. [When this will happen:] Targeted Release: We will begin rolling out early November 2024 and expect to complete by mid-November 2024. General Availability (Worldwide): We will begin rolling out mid-November 2024 and expect to complete by late-November 2024. General Availability (GCC, GCC High, and DoD): We will begin rolling out early January 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC956699 | (Updated) Microsoft Teams: Forward messages with app cards | Updated May 8, 2025: We have updated the rollout timeline below. Thank you for your patience. We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card. Please note: Forwarding of bot cards is excluded from this release. This message is associated with Microsoft 365 Roadmap ID 469506. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. We are introducing the ability to forward app cards. With the addition of app card forwarding, users now have a new way to share app cards across chats. To forward a message containing an app card, simply navigate to the More Actions menu of any message containing an app card and select forward. From here, the forward message dialog will populate, which provides users with a preview of the message being forwarded, including the app card. Please note: Forwarding of bot cards is excluded from this release. This message is associated with Microsoft 365 Roadmap ID 469506. |
N/A |
| MC966633 | (Updated) Microsoft Teams: Meeting recap can be shared as a link | Updated May 9, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Meeting participants will be able to share a link to the Meeting recap from the meeting thumbnail in chat and the Recap tab, making it easier to reference and share Meeting recap insights with others. Meeting participants can share the meeting recap link with anyone in their organization. Users who don't have access to the recording or transcript must request access before they can access the Meeting recap. This message is associated with Microsoft 365 Roadmap ID 471430. This message applies to Teams for Windows desktop and Teams for Mac desktop. [When this will happen:] Targeted Release: We will begin rolling out early February 2025 and expect to complete by early February 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (GCC High): We will begin rolling out late March 2025 and expect to complete late May 2025 (previously late April). Sharing a Meeting recap link from the meeting thumbnail: Sharing a Meeting recap link from the Recap tab: Shared Meeting recap link in chat: |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Meeting participants will be able to share a link to the Meeting recap from the meeting thumbnail in chat and the Recap tab, making it easier to reference and share Meeting recap insights with others. Meeting participants can share the meeting recap link with anyone in their organization. Users who don't have access to the recording or transcript must request access before they can access the Meeting recap. This message is associated with Microsoft 365 Roadmap ID 471430. This message applies to Teams for Windows desktop and Teams for Mac desktop. [When this will happen:] Targeted Release: We will begin rolling out early February 2025 and expect to complete by early February 2025. General Availability (Worldwide, GCC): We will begin rolling out mid-February 2025 and expect to complete by late February 2025. General Availability (GCC High): We will begin rolling out late March 2025 and expect to complete late June 2025 (previously late May). Sharing a Meeting recap link from the meeting thumbnail: Sharing a Meeting recap link from the Recap tab: Shared Meeting recap link in chat: |
N/A |
| MC967240 | (Updated) Microsoft Teams: File open preferences will extend to more Microsoft 365 apps | Updated March 12, 2025: We have updated the rollout timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Users will be able to set their preference for how their cloud-hosted Microsoft Word, Microsoft Excel and Microsoft PowerPoint files should open when they select links for these files from Teams. The new setting (open in a browser, desktop app, or directly in Teams) will extend to links selected in other Microsoft365 apps, starting with classic Microsoft Outlook, Word, Excel, and PowerPoint, for greater consistency across apps. This message applies to Teams for Windows desktop. This message is associated with Microsoft 365 Roadmap ID 471000. [When this will happen:] Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Coming soon to Microsoft Teams: Users will be able to set their preference for how their cloud-hosted Microsoft Word, Microsoft Excel and Microsoft PowerPoint files should open when they select links for these files from Teams. The new setting (open in a browser, desktop app, or directly in Teams) will extend to links selected in other Microsoft365 apps, starting with classic Microsoft Outlook, Word, Excel, and PowerPoint, for greater consistency across apps. This message applies to Teams for Windows desktop. This message is associated with Microsoft 365 Roadmap ID 471000. [When this will happen:] Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late June 2025 (previously late May). |
N/A |
| MC992216 | (Updated) Microsoft Teams: Third-party chat and meeting keyboard shortcut support | Updated March 28, 2025: We have updated the rollout timeline below. Thank you for your patience. Users familiar with keyboard shortcuts from third-party chat and meeting applications can use those same shortcuts in Microsoft Teams. To enable this, go to the Settings and more button in the upper right, access the keyboard shortcuts dialog, and select a communication or meeting layout. This allows users to apply the shortcuts they are used to from other applications. This message is associated with Microsoft 365 Roadmap ID 472913. [When this will happen:] Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-May 2025 and expect to complete by late May 2025. |
Updated June 13, 2025: We have updated the timeline below. Thank you for your patience. Users familiar with keyboard shortcuts from third-party chat and meeting applications can use those same shortcuts in Microsoft Teams. To enable this, go to the Settings and more button in the upper right, access the keyboard shortcuts dialog, and select a communication or meeting layout. This allows users to apply the shortcuts they are used to from other applications. This message is associated with Microsoft 365 Roadmap ID 472913. [When this will happen:] Targeted Release: We will begin rolling out early May 2025 and expect to complete by mid-May 2025. General Availability (Worldwide): We will begin rolling out mid-June 2025 (previously mid-May) and expect to complete by late June 2025 (previously late May). |
N/A |
| MC993226 | (Updated) Microsoft Teams: New location sharing settings for emergency calls and other features | Updated April 16, 2025: We have updated the rollout timeline below. Thank you for your patience. Microsoft is updating its policies regarding the sharing of user location data to enhance privacy, improve data security, and ensure compliance with evolving regulatory standards. To enhance transparency and user control, Teams is introducing a new location consent experience that gives users the choice of when and how Teams can use their location data (specifically SSID & BSSID). Please refer to the public documentation that will be published shortly. This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time. [When this will happen:] Targeted Release: We will begin rolling out mid-April 2025 (previously late March) and expect to complete by mid-April 2025 (previously late March). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late April 2025 (previously mid-April) and expect to complete by late May 2025 (previously early May). |
Updated June 12, 2025: We have updated the timeline below. Thank you for your patience. Microsoft is updating its policies regarding the sharing of user location data to enhance privacy, improve data security, and ensure compliance with evolving regulatory standards. To enhance transparency and user control, Teams is introducing a new location consent experience that gives users the choice of when and how Teams can use their location data (specifically SSID & BSSID). Please refer to the public documentation that will be published shortly. This message applies to Teams for Windows desktop (version 24H2 or greater) and Teams for Mac desktop. VDI clients will not be supported at this time. [When this will happen:] Targeted Release: We will begin rolling out mid-April 2025 (previously late March) and expect to complete by mid-April 2025 (previously late March). General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late April 2025 (previously mid-April) and expect to complete by late July 2025 (previously late May). |
N/A |
MC MessageTagNames changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1045211 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | User impact, Admin impact, Retirement | Updated message, User impact, Admin impact, Retirement | N/A |
| MC1053645 | (Updated) Microsoft Teams: Create new channels faster from the "New items" menu at top of the list of chats and channels | Feature update, User impact | Updated message, Feature update, User impact | N/A |
| MC1053653 | (Updated) Teams Meetings Copilot response can be shared to external apps (Word or Excel) | New feature, User impact, Admin impact | Updated message, New feature, User impact, Admin impact | N/A |
| MC1077865 | Updated: Microsoft Teams: Introducing the Network Strength Indicator | New feature, User impact | Updated message, New feature, User impact | N/A |
| MC1089315 | Resharing to external users required after enabling Microsoft SharePoint integration with Microsoft Entra B2B | Feature update, User impact, Admin impact | Updated message, Feature update, User impact, Admin impact | 06/30/2025 |
MC prepare changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1036575 | (Updated) Microsoft Viva Engage: External Networks are being modernized | Actions you need to take if you want to migrate from the current implementation to the modern one: 1. Identify all your External Network usage. As an Engage administrator, you may not currently be the administrator for older External Networks associated with your tenant. 2. Use the network data export to download a backup of each of your External Networks. 3. Inform users who are using the External Networks that the experience will shift from the current to the new one once the migration is complete. 4. Check the Message center for further updates. IMPORTANT: If you do not take action by June 15th or have not already requested an extension (and it has been granted), your External Network will be deleted. Documentation to configure modern External Networks is now live at: Set up modern external Viva Engage networks | Microsoft Learn Learn more: Export and manage Viva Engage data. https://learn.microsoft.com/viva/engage/configure-your-viva-engage-network/modern-external-networks https://learn.microsoft.com/viva/engage/eac-as-manage-data |
Actions you need to take if you want to migrate from the current implementation to the modern one: 1. Identify all your External Network usage. As an Engage administrator, you may not currently be the administrator for older External Networks associated with your tenant. 2. Use the network data export to download a backup of each of your External Networks. 3. Inform users who are using the External Networks that the experience will shift from the current to the new one once the migration is complete. 4. Check the Message center for further updates. IMPORTANT: If you do not take action by June 15th or have not already requested an extension (and it has been granted), access to your External Network will be removed effective July 7th, 2025. Documentation to configure modern External Networks is now live at: Set up modern external Viva Engage networks | Microsoft Learn Learn more: Export and manage Viva Engage data. https://learn.microsoft.com/viva/engage/configure-your-viva-engage-network/modern-external-networks https://learn.microsoft.com/viva/engage/eac-as-manage-data |
06/01/2025 |
| MC1045211 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | There will be no exceptions to the retirement which will be done on June 30th, 2025. We recommend you communicate clearly and early to admins of this impending change and coordinate an effort to understand the alternative solutions proposed above. https://learn%20about%20groups,%20group%20membership,%20and%20access%20-%20microsoft%20entra%20%7c%20microsoft%20learn/ https://learn.microsoft.com/en-us/purview/edisc https://learn.microsoft.com/en-us/viva/engage/eac-as-manage-data https://microsoft%20entra%20built-in%20roles%20-%20microsoft%20entra%20id%20%7c%20microsoft%20learn/ |
There will be no exceptions to the retirement which will be done on June 30th, 2025. We recommend you communicate clearly and early to admins of this impending change and coordinate an effort to understand the alternative solutions proposed above. https://learn%20about%20groups,%20group%20membership,%20and%20access%20-%20microsoft%20entra%20%7c%20microsoft%20learn/ https://learn.microsoft.com/en-us/purview/edisc https://learn.microsoft.com/en-us/viva/engage/eac-as-manage-data https://learn.microsoft.com/rest/api/yammer/api-requests https://microsoft%20entra%20built-in%20roles%20-%20microsoft%20entra%20id%20%7c%20microsoft%20learn/ |
N/A |
| MC1045211 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | There will be no exceptions to the retirement which will be done on June 30th, 2025. We recommend you communicate clearly and early to admins of this impending change and coordinate an effort to understand the alternative solutions proposed above. https://learn%20about%20groups,%20group%20membership,%20and%20access%20-%20microsoft%20entra%20%7c%20microsoft%20learn/ https://learn.microsoft.com/en-us/purview/edisc https://learn.microsoft.com/en-us/viva/engage/eac-as-manage-data https://learn.microsoft.com/rest/api/yammer/api-requests https://microsoft%20entra%20built-in%20roles%20-%20microsoft%20entra%20id%20%7c%20microsoft%20learn/ |
After June 30th, private content mode will automatically be disabled for all tenants, and if needed you would have the ability to enable it by calling the REST API as highlighted above. There will be no exceptions to the retirement which will be done on June 30th, 2025. We recommend you communicate clearly and early to admins of this impending change and coordinate an effort to understand the alternative solutions proposed above. https://learn%20about%20groups,%20group%20membership,%20and%20access%20-%20microsoft%20entra%20%7c%20microsoft%20learn/ https://learn.microsoft.com/en-us/purview/edisc https://learn.microsoft.com/en-us/viva/engage/eac-as-manage-data https://learn.microsoft.com/rest/api/yammer/api-requests https://microsoft%20entra%20built-in%20roles%20-%20microsoft%20entra%20id%20%7c%20microsoft%20learn/ |
N/A |
| MC1053652 | (Updated) Microsoft Viva Pulse: New Delegation feature | This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Pulse admins can toggle the delegation feature on or from Feature Access Management in Viva. Learn more View usage metrics with the tenant admin dashboard | Microsoft Learn Microsoft Viva - Feature access management | Microsoft Learn Before rollout, we will update this post with new documentation. https://learn.microsoft.com//viva/feature-access-management https://learn.microsoft.com/viva/feature-access-management https://learn.microsoft.com/viva/pulse/setup-admin-access/tenant-admin-dashboard https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=479753 |
This rollout will happen automatically in mid-July 2025 with no admin action required before the rollout. Review your current configuration to assess the impact on your organization. You may want to notify your users about this change and update any relevant documentation. Learn more View usage metrics with the tenant admin dashboard | Microsoft Learn Microsoft Viva - Feature access management | Microsoft Learn Before we complete rolling out the delegation feature, we will update this post with new documentation that explains how to set up delegation in Viva Pulse. https://learn.microsoft.com/Viva/control-access-admin-center https://learn.microsoft.com/viva/feature-access-management https://learn.microsoft.com/viva/pulse/setup-admin-access/tenant-admin-dashboard https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=479753 |
N/A |
| MC1089315 | Resharing to external users required after enabling Microsoft SharePoint integration with Microsoft Entra B2B | Notify your users: Inform users who collaborate externally that previously shared links will no longer work after Entra B2B integration. Update internal documentation: Adjust training materials and helpdesk scripts to reflect this change. Plan for MFA: External users will be required to complete multi-factor authentication (MFA) registration as part of the Entra B2B onboarding process. Learn more: Microsoft Entra B2B integration for SharePoint & OneDrive - SharePoint in Microsoft 365 | Microsoft Learn |
Notify your users: Inform your users who collaborate externally that previously shared links will no longer work. Update internal documentation: Adjust training materials and helpdesk scripts to reflect this change. Learn more: Microsoft Entra B2B integration for SharePoint & OneDrive - SharePoint in Microsoft 365 | Microsoft Learn https://learn.microsoft.com/sharepoint/sharepoint-azureb2b-integration |
06/30/2025 |
| MC786329 | (Updated) Exchange Online to retire Basic Auth for Client Submission (SMTP AUTH) | If your client supports OAuth, follow these steps: Authenticate an IMAP, POP or SMTP connection using OAuth If your client doesn't support OAuth and you must use Basic Auth with Client Submission (SMTP AUTH), you will need to switch to one of the following alternatives before September 2025: If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal to your tenant, you can use Microsoft 365 High Volume Email. Please visit this site to learn more: Manage high volume emails for Microsoft 365 Public preview If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal and external to your tenant, you can use Azure Communication Services Email. Please visit this site to learn more: Overview of Azure Communication Services email If you have an Exchange Server on-premises in a hybrid configuration, you can use Basic auth to authenticate with the Exchange Server on-premises or configure the Exchange Server on-premises with a Receive connector that allows anonymous relay on Exchange servers. Please visit this site to learn more: Allow anonymous relay on Exchange servers Regardless of the volume of email, if you must use Basic auth to send email with Exchange Online, then you must use one of the alternatives. We understand that this change requires some adjustments, but we believe that this is a necessary step to enhance the security and reliability of our email service and your data. https://learn.microsoft.com/azure/communication-services/concepts/email/email-overview https://learn.microsoft.com/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth https://learn.microsoft.com/exchange/mail-flow/connectors/allow-anonymous-relay?view=exchserver-2019 https://learn.microsoft.com/Exchange/mail-flow-best-practices/high-volume-mails-m365 |
If your client supports OAuth, follow these steps: Authenticate an IMAP, POP or SMTP connection using OAuth If your client doesn't support OAuth and you must use Basic Auth with Client Submission (SMTP AUTH), you will need to switch to one of the following alternatives before April 2026, previously September 2025: * If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal to your tenant, you can use Microsoft 365 High Volume Email. Please visit this site to learn more: Manage high volume emails for Microsoft 365 Public preview * If you are using basic authentication with Client Submission (SMTP AUTH) to send emails to recipients internal and external to your tenant, you can use Azure Communication Services Email. Please visit this site to learn more: Overview of Azure Communication Services email * If you have an Exchange Server on-premises in a hybrid configuration, you can use Basic auth to authenticate with the Exchange Server on-premises or configure the Exchange Server on-premises with a Receive connector that allows anonymous relay on Exchange servers. Please visit this site to learn more: Allow anonymous relay on Exchange servers Regardless of the volume of email, if you must use Basic auth to send email with Exchange Online, then you must use one of the alternatives or a 3P solution. We understand that this change requires some adjustments, but we believe that this is a necessary step to enhance the security and reliability of our email service and your data. https://learn.microsoft.com/azure/communication-services/concepts/email/email-overview https://learn.microsoft.com/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth https://learn.microsoft.com/exchange/mail-flow/connectors/allow-anonymous-relay?view=exchserver-2019 https://learn.microsoft.com/Exchange/mail-flow-best-practices/high-volume-mails-m365 |
N/A |
MC Title changes
| MC ID | MC Title | Old Value | New Value | MC Action required by |
|---|---|---|---|---|
| MC1045211 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | (Updated) Microsoft Viva Engage: Private content mode will retire as of June 30th, 2025 | N/A |
| MC1053653 | (Updated) Teams Meetings Copilot response can be shared to external apps (Word or Excel) | Teams Meetings Copilot response can be shared to external apps (Word or Excel) | (Updated) Teams Meetings Copilot response can be shared to external apps (Word or Excel) | N/A |
| MC1077865 | Updated: Microsoft Teams: Introducing the Network Strength Indicator | Microsoft Teams: Introducing the Network Strength Indicator | Updated: Microsoft Teams: Introducing the Network Strength Indicator | N/A |
CW24 New Office 365 Message Center items
| MC ID | MC Title | MC Category | MC Workload | MC Major Change | MC Action required by |
|---|---|---|---|---|---|
| MC1090702 | Update to Default blocked file types in Outlook web and new Outlook for Windows | Plan For Change | Microsoft 365 for the web, Microsoft 365 apps | True | N/A |
| MC1090698 | Microsoft Teams: New audit logs for Give control, Take control, and Screensharing | Stay Informed | Microsoft Teams | False | N/A |
| MC1090697 | Microsoft Viva Engage: Copilot adoption community now available to all tenants | Stay Informed | Microsoft Viva | False | N/A |
| MC1090695 | Microsoft Purview: Upcoming Update to Audit Records for Microsoft Purview Role Group Changes | Plan For Change | Microsoft Purview | True | N/A |
| MC1090694 | Admin Toggle to enable/disable "Mark Complete" feature in Viva Learning | Stay Informed | Microsoft Viva | False | N/A |
| MC1090689 | Microsoft Teams: Enhanced peripheral data in Pro Management portal reports for BYOD spaces | Plan For Change | Microsoft Teams | False | N/A |
| MC1090688 | Teams Town hall screen management privileges in Teams Rooms on Windows | Plan For Change | Microsoft Teams | False | N/A |
| MC1091448 | Microsoft 365 admin center: Email notifications for service health issues available in multiple languages | Stay Informed | Microsoft 365 apps | False | N/A |
| MC1091443 | Microsoft Defender XDR: Scoped access for Defender for Identity (preview) | Stay Informed | Microsoft Defender XDR | False | N/A |
| MC1092459 | Microsoft Viva Insights: New prompt categories in the Microsoft Copilot Dashboard | Stay Informed | Microsoft Viva, Microsoft Copilot (Microsoft 365) | False | N/A |
| MC1092458 | Microsoft Exchange Online: New Message Trace will be GA; legacy Message Trace will retire | Plan For Change | Exchange Online | False | 08/31/2025 |
| MC1092456 | Microsoft Viva Engage: Manage GDPR requests through the Engage admin center | Stay Informed | Microsoft Viva | False | N/A |
| MC1092430 | Microsoft Viva Goals: New Data export feature | Stay Informed | Microsoft Viva | False | N/A |
| MC1092207 | Updates available for Microsoft 365 Apps for Semi-Annual Enterprise Channel | Stay Informed | Microsoft 365 apps | False | N/A |
| MC1093237 | Microsoft Exchange Online: New Reject Direct Send parameter (preview) | Stay Informed | Exchange Online | False | N/A |
| MC1093236 | Microsoft Teams: An enhanced agent experience in Chats and Channels | Plan For Change | Microsoft Teams | False | N/A |
| MC1093235 | Text Prediction turned off by default in Outlook | Stay Informed | Microsoft 365 for the web, Microsoft 365 apps | False | N/A |
| MC1093233 | Important Update: Token Protection Policy for Power Query in Excel | Stay Informed | Microsoft 365 apps | False | N/A |
| MC1094051 | Support Update for SharePoint Framework Field Customizers in Lists and Document Libraries | Plan For Change | SharePoint Online | True | 06/30/2026 |
| MC1093912 | Microsoft Outlook for iOS/Android: Improved Contacts with profile enrichment and duplicate management | Stay Informed | Exchange Online, Microsoft 365 apps | False | N/A |
