Microsoft Roadmap, messagecenter and blogs updates from 05-09-2025

Updated August 25, 2025: We have updated the content to show as intended. Thank you for your patience.

Introduction

We’re enhancing Microsoft Secure Score by introducing new improvement actions based on Microsoft Defender for Identity posture recommendations. These updates provide a more accurate reflection of your organization’s identity security posture and help strengthen your overall security configuration.

When this will happen

• Public Preview: Rollout begins mid-August 2025 and completes by mid-September 2025.
• General Availability: Rollout begins mid-September 2025 and completes by late October 2025. Applies to Worldwide, GCC, GCC High, and DoD environments.

How this affects your organization

New posture recommendations will appear in Microsoft Secure Score as improvement actions. These include:

• Remove stale service accounts
• Remove discovered passwords in Active Directory account attributes

These recommendations will be visible only if your tenant has a Defender for Identity sensor deployed in your identity infrastructure. The update is enabled by default and requires no configuration changes.

What you can do to prepare

• No admin action is required before or after rollout.
• Review your current identity configuration to assess potential impact.
• Notify relevant administrators and update internal documentation as needed.
• Regularly review Microsoft Secure Score to monitor and act on new improvement suggestions.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

• APJ: September 19, 2025
• EUR: September 26, 2025
• NAM: October 3, 2025

• Assign a Windows Autopilot Enrollment Status Page (ESP) profile to devices. 
• Confirm or edit new settings in Intune to ensure updates can be installed during provisioning. 
• Assign Windows Update rings profile to ensure the OOBE respects pause and deferral settings. 

• Review the step-by-step instructions to Get ready for Windows quality updates out of the box. 
• Learn more about the Windows Autopilot Enrollment Status Page (ESP). 
• Read the preannouncement. 

1. Navigate to the Power Platform admin center
2. Go to Manage > Environments
3. Select an environment
4. Go to Settings > Product > Features > Preview and experimental AI models

Updated August 26, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing a new way to search in Microsoft Teams using structured, SQL-like query commands in the search bar. This enhancement allows users to filter messages, files, and conversations more precisely using keywords such as from:username, with:username, in:channel, or is:type (message, file, group chat, channel). This feature is especially useful for developers and power users who prefer to express specific search intent to narrow down search results and easily find what they are looking for.

This message is associated with Microsoft 365 Roadmap ID 496590.

When this will happen

Targeted Release: We began rolling out in early August 2025 and expect to complete by early August 2025 – Completed

General Availability (Worldwide): We began rolling out mid-August 2025 and expect to complete by mid-August 2025 – Completed

General Availability (GCC, GCCH, and DoD): We began rolling out late August 2025 and expect to complete by late September 2025.

How this affects your organization

This feature enhances the search experience in Microsoft Teams by enabling structured, SQL-like queries. It will be available on the following platforms at launch:

• Teams Web
• Teams Desktop
• Teams Mac

Users will be able to filter messages, files, and conversations using commands such as is:, in:, from:, and with:. This applies to all Teams content that is accessible to the user, including private chats, shared channels, and files.

Once available, the feature will be on demand—users can begin typing one of the supported commands in the search bar to activate it.

If a user enters an unsupported or malformed query, the system will default to standard search results. Users can also leverage query suggestions to help formulate correct queries.

This update provides a faster, more accurate way to locate content, especially in large or complex Teams environments.

What you can do to prepare

No admin action is required. You may wish to:

• Inform users about this new capability.
• Encourage users to try structured search queries.
• Share training materials or internal documentation to support adoption.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated August 26, 2025: After further review, this item is a duplicate of MC1136042. For the most accurate and up-to-date information, please refer to MC1136042.

Introduction

We’re streamlining the Microsoft 365 Copilot mobile app on iPhone and iPad to help users interact with their content more naturally and efficiently. This update will introduce file previews of Word, Excel, PowerPoint files in the mobile app. In these file previews, users can easily view file contents and comments, as well as use Copilot Chat to command and ask questions about the file. As part of this change, users will be prompted to open the standalone Word, Excel, and PowerPoint apps to edit their files. This change is rolling out in September for iPhone devices and coming later for iPad devices.

When this will happen

This update will be generally available for iPhone devices on September 15, and iPad devices soon after.

How this affects your organization

August 22, 2025: 

When users edit or try to create a Word, Excel, or PowerPoint file in the Microsoft 365 Copilot app on an iOS (iPhone or iPad) device, they will begin seeing a popup banner encouraging installation of standalone Word, Excel, or PowerPoint app. Users can choose to ignore the banner and continue in the Microsoft 365 Copilot app, with no change to functionality.

September 15, 2025: 

• The Microsoft 365 Copilot app for iPhone will transition to a file preview experience for Word, Excel, and PowerPoint files where they can view file contents and comments and use Copilot Chat to command and ask questions about the files. Users will not be able to edit files in the Microsoft 365 Copilot iPhone app. Instead, they will be prompted to open or install the standalone apps (ie. Microsoft Word iPhone app) to edit files.
• Teams, OneDrive, and Outlook apps will stop opening these files in the Microsoft 365 Copilot iPhone app for editing and instead prompt users to install or open the respective standalone apps.
• When opening a Word, Excel, or PowerPoint file in the Microsoft 365 Copilot iPhone app via Search result, Copilot Chat response, or share to Microsoft 365 Copilot action from a third-party app, users will get a streamlined experience where they can preview the file contents and get Copilot Chat assistance on the file directly in the preview.
• In the Create experience in the Microsoft 365 Copilot iPhone app, users will get a chat-centered experience when creating a document rather than the template options in Word, Excel, or PowerPoint experience. With this, they will directly see a Copilot Chat conversation experience when selecting the Word, Excel or PowerPoint option from the Create Screen. There, they can create a file via a chat prompt. They may open the file in the standalone Word, Excel, or PowerPoint apps once created for further editing.

After September 15, 2025:

We will roll out a similar set of updates to the Microsoft 365 Copilot app for iPad.

What you can do to prepare

No admin action is required. However, we recommend:

• Informing iOS users about updates to file experiences in the Microsoft 365 Copilot app and encouraging installation of Microsoft Word, Excel, and PowerPoint apps from the iOS App Store.
• Updating internal documentation and training materials to reflect the new file handling behavior for the Microsoft 365 Copilot iOS app.
• For organizations using mobile device management (MDM), consider pushing the standalone Word, Excel, PowerPoint and OneDrive apps to managed iOS devices. 

Updated August 26, 2025: We have updated the content. Thank you for your patience.

We are introducing improvements to how the Windows Autopatch Client Broker is managed and installed. The broker performs device readiness checks to identify whether a device is fully prepared to be managed by Windows Autopatch. Further, when a support request is created, it enables automated log collection to help diagnose and resolve issues more quickly. For information on data storage, see Privacy.

You will soon have the flexibility to deploy the client broker on-demand, either to all Autopatch devices or scoped to specific Entra ID groups. As part of this update, Win32 app deployment will become the default installation method, replacing the previous PowerShell-based approach. This change helps overcome limitations associated with PowerShell scripts and ensures a more reliable installation experience. Admins who prefer to use PowerShell can still manually install the broker using scripts if needed.

[When will this happen:]

The changes will be gradually rolled out starting September 22, 2025.

[How will this affect your organization:]

There will be no changes to your current set of devices with the client broker installed—they will remain assigned to the PowerShell script. However, with the upcoming launch, you’ll have the option to migrate to a Win32 app-based installation for improved reliability. Additionally, you’ll be able to use portal controls to selectively install the client broker on devices based on Entra ID groups.

[What you need to do to prepare:]

You should prepare for these changes in the Microsoft Intune admin center and inform your team. If you have any questions or concerns, or need assistance, file a service request by visiting the Microsoft Intune admin center. Additional Information and details will also be included on any docs.microsoft.com post feature release. 

Updated August 26, 2025: We have updated the content. Thank you for your patience.

Introduction

Coming soon to Microsoft Teams: a new control for users to turn off Microsoft Copilot when it is active in a meeting. This control will also turn off recording, transcript, and Facilitator if they are active. Copilot will not have access to what was said or shown in the meeting while it was turned off. After the meeting ends, Copilot will have access to all chat content and any recordings or transcripts created while it was active.

• Targeted Release: Rollout will begin mid-September 2025 and is expected to complete by late September 2025.
• General Availability: Rollout will begin late September 2025 and is expected to complete by early October 2025.

This feature will be available to users by default.

After rollout, users can turn off Copilot during a meeting using the following methods:

• Teams for desktop and web: Select the Copilot icon at the top of the screen to open Copilot, then select Turn off for everyone from the More options (three-dot) menu in the top-right corner of the Copilot panel.
• Teams for iOS/Android: Tap the meeting screen, tap the Copilot icon at the top, then tap the gear icon on the Copilot sheet.

• No admin action is required.
• We recommend reviewing your current meeting configurations and notifying users about this change.
• Update any relevant training materials or documentation to reflect the new Copilot controls.

Compliance considerations

To better reflect the identity and functionality of the Microsoft 365 Copilot app, we are updating the executable name on Windows devices. This change improves clarity for IT admins, developers, and users managing diagnostics or process monitoring.

When this will happen:

This update will roll out to affected users with the next app update after September 20, 2025.

How this affects your organization:

With the change, the executable name for the Microsoft 365 Copilot Windows app will change from Webviewhost.exe to M365Copilot.exe. For users who installed the app via the Microsoft Store, the update will happen automatically on September 20 if their device settings allow for automatic updates. For users who installed the app through other platforms or have settings that do not allow automatic updates, the change will happen once users update their app.

This update does not affect app functionality or user experience.

What you can do to prepare:

No action is required unless your organization has dependencies on Webviewhost.exe. If so, update those references to M365Copilot.exe to ensure continued functionality.

Compliance considerations:

No compliance considerations identified, review as appropriate for your organization.

Introduction

We’re expanding AI capabilities to SharePoint document libraries in Microsoft 365 on the web. AI file actions—already available in OneDrive—will now be accessible in SharePoint, enabling users to summarize content, compare files, generate FAQs, ask questions, and create audio overviews directly from document libraries.

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout began mid-May 2025 and is expected to complete by mid-September 2025.
• Targeted Release (Worldwide): Rollout began mid-May 2025 and is expected to complete by early September 2025.

Figure i. You can access AI actions from the “AI Actions” button in the toolbar in document libraries in SharePoint

Figure ii. You can also find these actions when you select or hover over an item in a document library

AI file actions will be available to all users with a Copilot license in SharePoint document libraries on the web. These actions mirror those currently available in OneDrive and offer enhanced productivity by enabling users to interact with files using natural language prompts.

This feature is on by default and does not require admin configuration.

• No action is required to enable this feature.
• We recommend informing your users about the new capabilities and reviewing Copilot licensing to ensure appropriate access.

Compliance considerations

Introduction:

We’re introducing a new Posts tab in the Microsoft Viva Communications dashboard. This enhancement provides corporate communicators and network administrators with a centralized location to manage communications across their lifecycle. The tab allows users to view drafts, scheduled posts, and published history, filter by ownership, and initiate new communications—all without leaving the dashboard.

We will begin rolling out in mid-September 2025 and expect to complete by the end of October 2025.

The new Posts tab will be available to all Microsoft 365 tenants using Viva Engage. Published posts will be retroactively visible from May 2025 onward.

Users can:

• View drafts, scheduled posts, and published history.
• Filter posts by ownership using the “Owned by” filter to view content created by themselves or others.
• Initiate new communications directly from the dashboard.

This feature is on by default and does not require admin configuration.

New Posts tab – Manage drafts, scheduled posts, and published history in one place:

• No action is required to enable the feature.
• Admins may wish to inform communications teams about the new functionality and encourage adoption.

No compliance considerations identified, review as appropriate for your organization.

Introduction

We’re introducing a refreshed user experience (UX) for Microsoft Entra credential enrollment and management. This update improves usability and accessibility across credential enrollment and management screens, with no changes to existing functionality.

When this will happen

General Availability (Worldwide, GCC, and GCCHigh): We will begin rolling out in early November 2025 and expect to complete by early November 2025.

How this affects your organization

Users and administrators will see an updated visual experience for credential management workflows. There are no changes to underlying functionality or user flows.

Screenshots 1-4. Refreshed credential enrollment and management UX with modern design element:

What you can do to prepare

No action is required. We recommend informing help desk teams of the visual refresh to reduce potential confusion.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Due to low usage, we’re retiring the sub-domains feature in Microsoft Defender for Cloud Apps – Cloud Discovery. This change simplifies the Cloud Discovery experience and aligns with broader improvements in app discovery and reporting.

• Start of retirement: September 22, 2025
• Full deprecation: December 31, 2025

This change will be applied automatically. No admin action is required.

If your organization currently uses sub-domain discovery insights in Cloud Discovery, these insights will no longer be available after the deprecation date. This may impact how administrators view and analyze discovered apps at the sub-domain level.

The feature is currently on by default for organizations using Cloud Discovery.

We recommend reviewing your current Cloud Discovery configurations and adjusting any workflows or reports that rely on sub-domain insights. For more information on discovered apps and alternative insights, visit:

• Learn more about discovered apps

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

As a follow up to MC804771, based on Admin feedback, we are updating the behavior for automated hiding of inactive channels to be opt-in (suggestions) only. With this update, Teams will offer users suggestions on channels that are inactive, and the user is prompted to review their inactive channels and hide them only if they choose. The user will also be able to view when they last visited the channel to help them decide if they would like to hide the channel. The settings support this opt-in workflow and there are no changes to the on demand hiding process.

This message is associated with Microsoft 365 Roadmap ID: 325780

[When this will happen:]

Targeted Release: Available now.

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late August 2025.

[How this will affect your organization:]

Before this rollout:

Users had to manually manage their relevant channels list by hiding inactive and irrelevant channels.

After this rollout:

Manage preferences for automated suggestions via Teams Settings

If users prefer to manage channels manually, they can opt out of the auto-suggestions process. Simply go to Teams settings, select General, and toggle off “Suggestions for hiding inactive channels.”

Hide inactive channels on demand when needed

Users can manually view which channels are inactive and choose to hide some or all of them whenever you need. This can be done from Settings, under General, by clicking the “Get Suggestions” button. Note that this action can be performed once every 24 hours.

Automated suggestions of inactive channels

With this, Teams will suggest channels that have been inactive for the user. Once the inactive channels are identified, the user is notified with the coach mark message, “Looks like you haven’t visited some channels lately. Hide them to help you focus.”

The user can select Review and Hide to see the details and decide which channels they would like to hide. The user can choose not hide any channels by selecting Not Now.

If a user has less than or equal to 25 shown channels, no channels will be suggested for that user. This feature is on by default and all Teams users on the affected platforms will have access to it.

[What you need to do to prepare:]

Admins need to be aware of this feature, but no additional action is needed.

• Windows Backup for Organizations is now generally available! Experience seamless device transitions with enterprise-grade backup and restore.
• This update improves the Copilot key’s reliability and resolves an issue that prevented users from restarting Copilot after using the key.
• This update addresses an issue where Wi-Fi might not reconnect automatically after a Group Policy update.
• This update addresses an issue where cameras didn’t appear during remote sessions after being added or removed. Newly connected cameras were not recognized in Remote Desktop Services (RDS) environments.

• Windows 11, version 23H2: KB5064080
• Windows 10, version 22H2: KB5063842

• Devices are Microsoft Entra or Microsoft Entra hybrid joined.  
• Devices are running a supported version of Windows 10, version 22H2 or Windows 11, version 22H2 or later. 
• Devices have the August 2025 or newer Windows security update. 
• The backup policy is enabled via mobile device management (MDM) or Group Policy.  

• Devices are Microsoft Entra joined. 
• Devices are running Windows 11, version 22H2 or later. 
• Devices are preprovisioned with at least the August 2025 Windows security update prior to users going through out-of-box experience (OOBE). 

• Get started with step-by-step instructions at Windows Backup for Organizations is now available. 
• Read the official documentation for Windows Backup for Organizations. 
• Learn more about quality updates with OOBE at Get ready for Windows quality updates out of the box. 
• Enable backup policies via mobile device management (MDM) or Group Policy.  

The In development for Microsoft Intune page in our documentation has been updated.

[How this will affect your organization:]

The In development page provides a list of features in upcoming releases of Microsoft Intune to assist in your readiness and planning. The list has now been updated. You will start seeing these changes in the next month or in a subsequent release.

[What you need to do to prepare:]

You can inform your IT staff and helpdesk of the upcoming changes listed on this page. Plan to update your user guidance, if you feel any of these features would be important to your users.

Updated August 27, 2025: We have updated the timeline. 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 October 2025 and expect to complete by mid-October 2025.

General Availability (WW, GCC, GCC High, and DoD): We will begin rolling out mid-October 2025 and expect to complete by late October 2025

[How this will affect your organization:]

After the rollout, meeting participants who are not sharing their screens will have the ability to request an annotation session. This request will be sent to the presenter sharing their screen who can choose to accept or deny it:

If the request is accepted, the annotation session will start for everyone in the meeting:

Anonymous users in the meeting will not be able to send a request.

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation as appropriate.

Learn more: Use annotation while sharing your screen in Microsoft Teams – Microsoft Support (we will update this before rollout)

Watch: How to use Collaborative Annotations in a Microsoft Teams meeting (2022)

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

Coming soon: Users can share Microsoft Teams apps or agents from the app or agent profile and from the app side panel in Teams.

This message applies to Teams for Windows desktop, Teams for Mac desktop and Teams on the web.

A Microsoft 365 Copilot license is not required to share agents as described in this message. If a user has access to the agents, the users will be able to share them.

This message is associated with Microsoft 365 Roadmap ID 483355.

[When this will happen:]

Targeted Release: We will begin rolling out mid-October 2025 and expect to complete by late October 2025.

General Availability (Worldwide): We will begin rolling out early November 2025 and expect to complete by late November 2025

[How this will affect your organization:]

After this rollout:

• Users can select the Share option when hovering on the app or agent icon in 1:1 chat mode with the app or agent.
• After a user selects the +Apps icon from the three-dot menu in the top right of any chat, the user can right-click to share the app or agent.

Share option from hovering on app/agent icon:

Sharing from right panel:

This change will be on by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

With this rollout, if no room is booked for the meeting, an AI-generated room suggestion will be sent in the meeting chat an hour before the meeting start time when two or more attendees are co-located in the same building, making in-person collaboration easier. The room suggestion will consider location of participants, room availability, and capacity to find the best space. You can reserve the suggested room with just one click and update the invite for everyone. The organizer must have a Teams premium license for this experience to occur, which is on Teams mobile on iOS.  #MicrosoftPlaces

This message is associated with Microsoft 365 Roadmap ID 482191

[When this will happen:]

General Availability (Worldwide): We will begin rolling out mid-October 2025 and expect to complete by late October 2025.

[How this will affect your organization:]

This will be a default on feature.

For a room suggestion to be generated, a meeting must have:

• Between two to seven attendees with at least two attendees that are co-located
• Teams meeting link
• Organizer has Teams premium
• No room is already booked for the meeting
• No external attendees
• Not an all-day event 

Room suggestions will be generated in buildings where at least two attendees, who haven’t declined the meeting, share the same work location. For instance, if a meeting has four attendees, with two in Building X and two in Building Y, suggestions for both buildings will be sent. Distribution lists are not considered.

If a meeting is moved, canceled, or the suggested room becomes unavailable, the card will update dynamically upon clicking ‘Reserve’.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may also want to notify your team about this change and update any relevant documentation. We recommend making sure that your rooms are properly added to Places directory with a building associated.  

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

We are adding more functionality to offline mode in the new Outlook for Windows. You will now be able to open and save attachments from your emails without an internet connection.   

Please note that this is only scoped to classic file attachments. OneDrive and SharePoint links in the body of the emails will still need a connection to be opened.   

For this functionality to work you need to make sure Offline is enabled and offline attachments are enabled.   

At the user level you can verify this by checking two settings in new Outlook Settings – General – Offline:   

1. Enable offline email, calendar and people  
2. Include file attachments  

This functionality will also be enabled or disabled based on the True/False behavior of the already existing Mailbox Policy: OWAMailboxPolicy- OfflineEnabledWin. 

Attachments from emails within the timeframe and folder scope selected in the “Settings – General – Offline” will be synced and available locally for users to open without an internet connection.  

This message is associated with Microsoft 365 Roadmap ID 472026

[When this will happen:]

Targeted Release (Worldwide): We will begin rolling out on mid-May 2025 and expect to complete by late May 2025.

General Availability (Worldwide): We will begin rolling out on late June 2025 and expect to complete by mid-August 2025.

General Availability (GCC): We will begin rolling out on late August 2025 and expect to complete by mid-September 2025.

[How this will affect your organization:]

Classic attachments from emails within the timeframe and folder scope selected in the “Settings – General – Offline” will be synced and available locally for users to open without an internet connection:

[What you need to do to prepare:]

The default on or off of this feature will depend on your existing Offline configuration in the new Outlook via the following policy: OWAMailboxPolicy- OfflineEnabledWin.  This feature will not change the default of this Policy. You can find more information about this Policy here: Set-OwaMailboxPolicy  

If you have not made any changes to this Policy, then the default of this feature will be on. 

Updated August 27, 2025: We have updated the content. Thank you for your patience. 

 Coming soon: Microsoft Purview | Data Loss Prevention (DLP) policy support for Microsoft Fabric allows admins to scope DLP policies to lakehouses, in addition to Microsoft Power BI (also supported today). In other words, in Fabric lakehouses, DLP policies can help audit and notify users through policy tips based on sensitive content. We will also extend DLP policy support Fabric KQL databases and mirrored databases.

This message is associated with Microsoft 365 Roadmap ID 420332.

[When this will happen:]

Public Preview:

• DLP policy support for Fabric lakehouses is available in Public Preview as of October 2024.
• For KQL databases and mirrored databases, we will begin rolling out mid-April 2025 and expect to complete by late April 2025 

General Availability (Worldwide): We will begin rolling out mid-September 2025 (previously mid-August) and expect to complete by early October 2025 (previously early September).

[How this will affect your organization:]

After this rollout, when admins configure DLP policies on Fabric workspaces, DLP policies will scan and identify sensitive information (as well as semantic models) in lakehouses, KQL databases, and mirrored databases. Mirrored databases include Mirrored Azure Cosmos databases, Mirrored Azure databases for PostgreSQL, Mirrored Azure SQL databases, Mirrored Azure SQL Managed Instance, Mirrored databases, Mirrored Snowflake, and Mirrored SQL Server databases.

If you already have a Fabric or Power BI location selected in your DLP policy today, the policy will automatically start applying to these assets as well (as long as the lakehouse, KQL, and mirror database is in the scope of the DLP policy).

You can configure a policy to apply to Fabric in Purview at Data Loss Prevention > Create policy > Locations:

[What you need to do to prepare:]

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.

No action is required from admins. Both existing and new DLP policies will be on by default and will automatically start evaluating Fabric lakehouses, KQL, and mirrored databases.

If you do not want to include Fabric lakehouses, KQL, and mirrored databases in your DLP policies, please review your policies and update the location scopes appropriately.

DLP policy support for Fabric is subject to the new Microsoft Purview pay-as-you-go billing model (will be updated before rollout).

Learn more: Get started with DLP for Fabric and Power BI | Microsoft Learn

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

Microsoft Teams: Your Office 365 subscription is being updated with a new service plan: Queues app for Microsoft Teams. Powered by Teams Phone, the Queues app enables team members to make and receive customer calls without having to leave Teams, with tailored experiences for users and leads that are designed for efficiency in call handling and resolution.

This message is associated with Microsoft 365 Roadmap ID 490056

[How this will affect your organization]

Queues app will be listed as a service plan under the Teams Premium license. This is to prepare for the GCCH and DOD release of the New Voice Applications Settings for Authorized Users for Microsoft Teams (early September 2025). The rollout plan outlining the availability of the New Voice Applications Settings for Authorized Users will be communicated via the Message Center and the roadmap.

[What you need to do to prepare]

You may consider updating your training and documentation as appropriate.

Admins: Manage voice applications policies in Microsoft Teams – Microsoft Teams | Microsoft Learn

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

Users will soon be able to access agents in Microsoft 365 Copilot from the Edge sidebar (on the right side of the screen) while using Copilot.

This message applies to Web chat and Work chat for users with a Microsoft 365 Copilot license and to Copilot Chat for users with a Microsoft 365 license.

This message is associated with Microsoft 365 Roadmap ID 482410.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in late September 2025 (previously late August) and expect to complete by early October 2025 (previously early September).

[How this will affect your organization:]

Users must first add agents to Microsoft 365 Copilot for them to be available in the Edge sidebar when using Copilot. (Learn more about adding agents: Introducing agents – Microsoft Support). Users will not be able to create, search for, or add new agents when using Copilot from the Edge sidebar at this time.

Users will be able to access their previously added agents in Microsoft 365 Copilot from the Edge sidebar while using Copilot. This rollout will help users focus on their main browser activities and access agents without switching to another screen.

This feature will be available by default.

Select Agents from the three-dot menu (…) in the top right of the Edge sidebar:

View and select an available agent:

Engage with agents on the Edge sidebar, such as the Prompt Coach:

[What you need to do to prepare:]

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.

Learn more

• How to manage Copilot in the Edge sidebar: Microsoft 365 Copilot Chat in Edge | Microsoft Learn
• Manage agents for Microsoft 365 Copilot in Integrated Apps – Microsoft 365 admin | Microsoft Learn
• Introducing agents – Microsoft Support

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

Copilot users in a business-to-business multi-tenant organization set up can now view the intelligent meeting recap after the meeting from the resource tenant where the meeting was hosted.

This message is associated with Microsoft 365 Roadmap ID 488298

[When this will happen:]

Targeted release: We will begin rolling out early October 2025 and expect to complete by mid- October 2025.

General Availability: We will begin rolling out mid- October 2025 and expect to complete by late October 2025.

[How this will affect your organization:]

The new capability empowers users in multi-tenant setup to access meeting recap post meeting.

[What you need to do to prepare:]

No action required for either admin or users. Any Copilot users configured as a business-to-business user in a multi-tenant organization will have the capability after the launch.

For additional information on B2B muti-tenant: Overview: B2B collaboration with external guests for your workforce

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing voice chats in Microsoft 365 Copilot. 

This update enables users to interact with Copilot using voice, offering a more natural, hands-free experience. Voice chat in M365 Copilot allows users to brainstorm ideas, explore topics, and quickly search—while being able to interrupt or redirect the conversation at any time. This feature will support productivity and accessibility across platforms.

[When this will happen:]

General Availability (Worldwide): Rollout will start early September 2025 (Previously iOS-only in mid-August). 

[How this will affect your organization:]

Users will see a voice chat icon in the bottom-right corner of the input box when using M365 Copilot. Selecting this icon will start voice conversation with Copilot, enabling a more natural and flexible way to interact with AI. This feature is on by default and does not require admin configuration. 

iOS/Android: 

Web/Windows/Mac: 

[What you can do to prepare:]

This feature will be on by default. No action is required by an admin. It is recommended that you notify your users about this new capability and update internal documentation.  

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

We’re adding new peripheral health reporting capabilities to the Pro Management portal, enabling admins to proactively monitor device issues in bring your own device (BYOD) rooms and desks.

These reports help identify when peripherals are faulty, missing, moved, or undetectable by a PC—allowing admins to take action before users report problems. Reports for rooms require a Teams Shared Devices license. Desk reporting is currently in public preview.

This change is associated with Microsoft 365 Roadmap ID: 493319

[When this will happen:]

General Availability (Worldwide and GCC): Rollout will begin in early October 2025 and is expected to complete by late October 2025.

[How this affects your organization:]

Admins can now use peripheral status data to detect hardware issues in BYOD rooms and desks before they impact users. This proactive monitoring can reduce support tickets and improve meeting space reliability.

• Reports for rooms require a Teams Shared Devices license.
• Reports for desks are available in public preview and do not yet require a license.

[What you can do to prepare:]

To ensure accurate peripheral status reporting:

• Use multiple peripherals in each room or desk setup. The system compares expected device pairings (e.g., if Peripheral A and B are usually connected together, but A is missing, it will be flagged).
• Simplify connectivity for users by using a single cable solution to connect all peripherals.
• Ensure rooms and desks are bookable and have associated peripherals—this enables the Teams desktop client to send the necessary telemetry. Peripheral association can be done manually or automatically.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Maybe (device telemetry is used for reporting)

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing a new sign-in experience that enhances flexibility and accessibility for a limited number of users on Microsoft Teams for the web. This change introduces new sign-in options—Continue with Apple and Continue with Google—on the sign-in page (teams.microsoft.com or teams.com) for users routed through login.microsoftonline.com/common.

NOTE: These options are intended for consumer Microsoft accounts and may be visible to both consumer and enterprise users, depending on your authentication configuration.

[When this will happen:]

We will begin rolling out this private preview (Worldwide) in mid-September 2025 (previously late August) to a small number of Teams for the web users and expect to complete by mid-October 2025. We expect to expand this feature to other Microsoft apps later in 2025.

[How this will affect your organization:]

After this rollout:

• Users can sign in or sign up for a Microsoft account using Apple or Google credentials.
• Some users will be prompted to confirm whether they are using a personal or work/school account.
• Existing sign-in methods remain unchanged, including entering an email/username or using Sign-in options to access organizational accounts.
• Organizations using custom URLs (such as login.microsoftonline.com/contoso.com) will not be affected.
• In the case of Teams on the web, the custom URLs will be https://teams.microsoft.com?tenantId=<YOUR_DOMAIN_NAME> or https://teams.microsoft.com?tenantId=<YOUR_TENANT_ID>

Screenshots of the new experience:

1. Users can select Continue with Apple or Continue with Google to sign in or sign up for a consumer Microsoft account using an Apple or Google credential. This image shows the Google option:

2. A subset of users who click these options will see a screen that confirms whether they are using a personal or work/school account. In this image, the user has selected the work/school option:

3. Users can still enter their email/username at the top of the sign-in screen, and sign into a specific organization with Sign-in options:

[What you need to do to prepare:]

No action is required. This feature is only being added to login.microsoftonline.com/common. Users accessing login.microsoftonline.com with a custom URL will not see this feature.

You can show a custom URL for your organization by passing a domain hint to apply company branding at the initial sign-in screen. Custom URLs for Teams on the web will be https://teams.microsoft.com?tenantId=<YOUR_DOMAIN_NAME> or https://teams.microsoft.com?tenantId=<YOUR_TENANT_ID>.

Learn more

• Add company branding to your organization’s sign-in page – Microsoft Entra | Microsoft Learn
• Adding branded URLs to authentication with Microsoft Entra External ID Custom URL Domains | Microsoft Entra Identity Platform

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing a new personalization feature in Microsoft Teams that allows users to select from a set of accent colors. This update enhances the user experience by enabling visual customization of the Teams interface and will be available on Desktop, Mac, and Web platforms. 

This message is associated with Microsoft 365 Roadmap ID 497139.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out in early November 2025 and expect to complete by late November 2025.

[How this will affect your organization:]

Users will be able to personalize their Teams experience by choosing an accent color for the Teams shell. This change is purely cosmetic and does not impact functionality or performance. The feature will be on by default and available to all users once the rollout is complete.

Image 1. Change accent colors in Settings > Appearance:

Image 2: User selected accent color applied in Teams:

[What you need to do to prepare:]

No admin action is required. However, you may wish to inform your users about this new personalization option.

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

You can now save a meeting as a draft on your calendar when you’re not ready to send invites. This update gives users more flexibility when planning events, especially when details are still being finalized.

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in July 2025 and is expected to complete by early September 2025 (previously late August).

Users will be able to save events as drafts when creating a meeting with at least one attendee. To do this, select the Discard button while composing the event, then choose Save as a draft. Draft events will appear on the calendar with a “[Draft]” prefix in the title.
This feature is available on mobile and will be on by default.

What you can do to prepare

• No admin action is required. You may want to:
• Inform your users about this new capability.
• Update internal training materials or documentation as needed.

No compliance considerations identified, review as appropriate for your organization.

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re enhancing offline functionality in the new Microsoft Outlook for Windows. This update (Microsoft 365 Roadmap ID 496371) enables users to add file attachments while composing emails offline, improving productivity for those working without an internet connection.

When this will happen

• Targeted Release (Worldwide): Rollout begins in mid-September 2025 and is expected to complete by mid-October 2025.
• General Availability (Worldwide): Rollout begins in mid-November 2025 and is expected to complete by late November 2025.
• General Availability (GCC): Rollout begins in early December 2025 and is expected to complete by mid-December 2025.

How this affects your organization

Users with offline mode enabled in the new Outlook for Windows will be able to attach files to draft emails while offline. These emails, including attachments, will be sent automatically once the device reconnects to the internet.

This feature will be on or off by default based on your current configuration of the OWAMailboxPolicy-OfflineEnabledWin policy. No changes will be made to existing configurations.

What you can do to prepare

To enable this functionality, ensure the following settings are configured in the new Outlook under Settings > General > Offline:

• Enable offline email, calendar, and people
• Include file attachments

Admins can manage this feature using the OWAMailboxPolicy-OfflineEnabledWin mailbox policy. Learn more at Set-OwaMailboxPolicy.

Caption i. Offline editing can be enabled or disabled in Settings > General > Offline

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

Introduction

You can now deploy, manage, and measure a frontline worker (FLW) pilot directly from Teams Admin Center. This new capability enables Teams administrators to define pilot users and owners, configure workloads, and monitor adoption—all in one place. It’s designed to help IT admins and business leaders streamline the rollout of Teams features tailored for frontline teams.

This message is associated with Microsoft 365 Roadmap ID 498226

When this will happen

Public Preview: Rolling out early October 2025; expected completion by mid-October 2025.

General Availability: Rolling out mid-October 2025; expected completion by late October 2025.

How this affects your organization

This feature provides a simplified experience for piloting Teams capabilities for frontline workers. Admins can:

• Select and configure workloads such as Chat, Channels, Shifts, Walkie Talkie, Viva Engage, and Tasks.
• Assign pilot users and owners.
• Share access to the Teams mobile app via QR code.
• Monitor adoption and usage insights directly in Teams Admin Center.

What you can do to prepare

To prepare for this rollout:

• Identify frontline worker pilot participants and the workloads you want to enable.
• Review your Teams Admin Center settings to ensure you have the necessary permissions.
• Plan communications with pilot users to support adoption.
• Learn more: [Link to be provided]

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated August 27, 2025: We have updated the content. Thank you for your patience.

Introduction

We’re introducing a new SharePoint Web Part: Agent Link Web Part. This feature allows site owners to embed a clickable link to an agent on a SharePoint page that launches the configured agent in the sidecar experience. It’s a lightweight, flexible way to surface contextual help using AI agents directly from within your site—improving discoverability and access to AI agents where users need it most.

Where to Find It: The Agent Link Web Part will appear under a new category called AI in the web part toolbox. Search for the name Agent Link WebPart.

This message is associated with Microsoft 365 Roadmap ID 481512.

When this will happen

General Availability (Worldwide): We will begin rolling out mid-August 2025 and expect to complete by late August 2025 – Completed

How this affects your organization

• Flexible Placement: Add a link to any custom SharePoint agent directly on your page.
• Contextual Assistance: Clicking the link opens the agent in the sidecar, enabling users to get help without leaving the page.
• Enhanced Discoverability: Promotes in-context discovery of AI-powered agents, helping users engage with intelligent assistance where and when they need it.
• License Handling: Users without access see a message indicating they don’t have access within the sidecar. As a reminder, links to agents only work for users with a Microsoft 365 Copilot license, or for users in organizations that have set up the Microsoft 365 PAYG meter.

Here’s how an editor adds the web part to the page:

Find the webparts in the toolbox. Under the category AI, find a web part called Agent Link and Add it to your page.

Next, configure and link it to an agent – either search for an agent or pick one from the recently used agents. Customize the size of the link from small, medium, or large, and choose to show a title or not.

Then, publish your page. That’s it – your web part is ready to go! Now, as a site visitor, sees the webpart on the page. When a user selects the webpart, the agent link opens in the sidecar.

 What you can do to prepare

Site admins and content authors may want to:

• Identify pages where contextual agent support can improve user experience.
• Plan to add the Agent Link Web Part to relevant pages post-GA.
• Ensure referenced agents are published and accessible to your users.
• Agents published to SharePoint are also configurable using this web part.

Note: This web part is currently not supported in mobile or email scenarios.

Additional resources:

Using web parts on SharePoint pages – Microsoft Support

Use the Agent link web part – Microsoft Support

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

Introduction

To simplify management and reduce configuration friction for voice and face recognition in Microsoft Teams Rooms (MTR), we’re introducing new admin-facing settings in the Teams Pro Management Portal and directly on Teams Rooms devices (Windows and Android). These settings replace PowerShell-based configuration with a more intuitive UI, offering clearer visibility into recognition status across rooms.

This message is associated with Microsoft 365 Roadmap ID 499615.

When this will happen

General Availability (Worldwide, GCC): Rollout will begin in mid-October 2025 and is expected to complete by late October 2025.

How this will affect your organization

This update enhances the experience for tenant admins who manage Intelligent Rooms by:

• Introducing a simplified UI in the Teams Pro Management Portal and on-device settings for managing voice and face recognition.
• Setting voice recognition to Off by default, allowing admins to enable it as needed.
• Eliminating the need for PowerShell scripts to configure recognition settings, though PowerShell will remain a supported method.

New UI for managing voice and face recognition settings in Teams Rooms devices:

This feature applies to Microsoft Teams Rooms on:

• Windows (version 4.19 or higher)
• Android (version 3.6 or higher)

Note: This feature is not supported on Surface Hub or Teams displays.

Access to the Teams Pro Management Portal requires at least one Teams Rooms Pro or Teams Shared Device license.

Users must enroll on-device and provide consent to participate in voice and face recognition. Recognition data is stored locally on the device and is not uploaded to the cloud.

What you can do to prepare

No action is required until rollout begins. Once available:

• Review and configure the new settings in the Teams Pro Management Portal or directly on Teams Rooms devices.
• If your organization uses voice and face recognition in Intelligent Rooms, you can now manage these settings via the new UI instead of PowerShell.
• PowerShell remains available for organizations that prefer or require script-based configuration.
• Enrollment is completed on-device and requires user consent.

Learn more: Overview of voice and face enrollment | Microsoft Teams | Microsoft Learn

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated August 27, 2025: We have updated the content. Thank you for your patience.

When this will happen: Updated Rollout Schedule for iPhone and iPad

The first phase of this change is in-product notifications in the M365 Copilot app to encourage users who are editing documents to install the Word, PowerPoint, Excel and OneDrive apps. This in-app notification will roll out to TestFlight users only the week of August 25, 2025 and become generally available on September 15, 2025 (09/15). This is a modification from the initial post to allow our enterprise customers more time to prepare.

The second phase of this change updates the Word, PowerPoint and Excel functionality in the Microsoft 365 Copilot app with previewers that will be made available to TestFlight users only in September and GA on October 13, 2025. All changes described below will be implemented across iPhone and iPad.

To get early builds and test out features before GA dates – you will need to join the iOS TestFlight program for the Microsoft 365 Copilot app. There are a limited number of seats available in the iOS TestFlight program. We periodically remove inactive users (those who have not updated their build) to make space for others. If you are unable to join because the program is full, please check back later, or contact your Microsoft Support representative. Learn More: Microsoft 365 Insider program on iOS, Become a Microsoft 365 Insider on iOS.

How this affects your organization: Transition to Previewers in the M365 Copilot App for WXP file viewing & File Access & Management

As part of this update, the Microsoft 365 Copilot app for iPhone and iPad will transition to a Copilot powered preview experience for Word, Excel, and PowerPoint. Users will continue to be able to view files and use Copilot Chat to get deeper analysis and insights on their content. If a user needs to edit, the M365 Copilot app will transition to the standalone Word, Excel, or PowerPoint apps. Users of the M365 Copilot app will continue to be able to browse and search recent files in the app, but users seeking comprehensive file management features will be encouraged to utilize the OneDrive app. When users land in the M365 Copilot app Search experience and navigate to the My files, Libraries, or My device entry points a notification will appear promoting the use of the OneDrive app for these actions.

Detailed Change Log: Word, Excel, PowerPoint, M365 Copilot App

• Word, Excel, PowerPoint: The Microsoft 365 Copilot app for iPhone and iPad will a provide a Copilot powered preview experience for documents. Users can view content and use Copilot Chat for file queries. Users who wish to edit the file will be prompted to open or install the standalone apps.
• M365 Copilot App: The M365 Copilot app has evolved to an AI-first productivity assistant that brings together productivity activity across Word, Excel, PowerPoint, Outlook and other Microsoft 365 apps. It gives your users the power of file previews and M365 Copilot chat in an experience that inherits all the security, identity and privacy policies you’ve set up in Microsoft 365.
• iPad Inclusion: All changes described will now be rolled out simultaneously for iPad and iPhone.
• Teams, OneDrive, Outlook iOS app integration: These apps on iPhone and iPad will continue to show users a preview of their Word, Excel and PowerPoint files. If users want to open and edit a Word, Excel, or PowerPoint file, they will now be directed to the respective standalone Word, Excel or PowerPoint app. The M365 Copilot app will no longer handle file open and edit operations from Teams, OneDrive or Outlook.
• File Management: Searching for files within the M365 Copilot app will remain available. For advanced file management, users will be directed to the standalone OneDrive app.
• Create Experience: Document creation in the M365 Copilot app will be available from chat. After file creation, users can view the file within M365 Copilot. Editing the document will transition to the standalone WXP apps.
• Offline File Experience: For users who wish to make files available offline, please use the Word, Excel, PowerPoint, and OneDrive apps. “Make Available Offline” is being removed from the M365 Copilot app in favor of Copilot powered previewer experiences.
• PDF Workflows: No changes. PDF handling continues as before in the M365 Copilot app.

What you can do to prepare: Updated Recommendations

• Inform iOS and iPadOS users about the updated file experiences in the M365 Copilot app, and for users who have the need to edit WXP files on their mobile devices, encourage installation of the standalone Word, Excel, and PowerPoint apps.

• The M365 Copilot app should continue to be available to end users as an AI-first productivity assistant. It brings together productivity apps and content with Copilot, Word, Excel, PowerPoint, and more.

• Update all internal documentation and training materials to reflect the revised file handling behavior for the M365 Copilot app across iPhone and iPad.

• For organizations using mobile device management (MDM), push the standalone Word, Excel, PowerPoint, and OneDrive apps to manage iOS/iPadOS devices.

• Join the iOS TestFlight program for the M365 Copilot app to get early access to changes

Learn more: Deployment guide: Manage iOS/iPadOS devices in Microsoft Intune

Compliance considerations: Impact on Workflows, Admin Controls, and Metrics

The M365 Copilot app remains a necessary and supported solution for enterprise environments, providing preview and AI-powered chat experiences for Word, Excel, and PowerPoint files. Organizations should continue to manage and deploy the Copilot app to maintain access to Enterprise AI workflows.

Introduction

We’re introducing the Microsoft Defender Core service for Windows Server 2012 R2 and Windows Server 2016. This new service enhances the stability and performance of Microsoft Defender Antivirus, helping organizations strengthen endpoint protection on legacy server platforms.

• Public Preview: Begins August 28, 2025, via the Beta channel (Prerelease).
• General Availability: Rollout begins in mid-September 2025 across all rings and completes by early October 2025.

The Microsoft Defender Core service will be installed alongside Microsoft Defender Antivirus on supported Windows Server 2012 R2 and Windows Server 2016 running the unified Microsoft Defender for Endpoint client. This service improves performance and reliability but does not change existing antivirus functionality or configurations.

This feature will be enabled by default once the platform is updated to the required version.

• Update the Microsoft Defender platform to version 4.18.25060.7-0 or newer.
• Allow the following URLs:
• Commercial: *.events.data.microsoft.com, *.endpoint.security.microsoft.com, *.ecs.office.com
• For US Gov, the ECS URLs are:
• GCC Mod: *.gccmod.ecs.office.com
• GCC High: *.config.ecs.gov.teams.microsoft.us
• DOD: *.config.ecs.dod.teams.microsoft.us
• If using an Application Control application or running a third-party AV and/or EDR, add the following process to the allowed list:
• MdCoreSvc – MpDefenderCoreService.exe

Learn about the prerequisites.

No compliance considerations identified, review as appropriate for your organization.

To help you manage Copilot Search adoption within the Microsoft 365 Copilot app, we’re introducing a new usage report in the Microsoft 365 admin center. This report provides insights into how users in your organization are engaging with Copilot Search, enabling better visibility and informed decision-making.

This message is associated with Microsoft 365 Roadmap ID: 497545    

When this will happen

General Availability (Worldwide): Rollout will begin late August 2025 and is expected to complete by early September 2025.

How this affects your organization

A new “Copilot Search” report will appear under Reporting > Usage > Microsoft 365 Copilot > Copilot Search in the Microsoft 365 admin center. This report includes:

• Active users and average daily active users
• Total searches and average searches per user
• Daily trend view of active usage and total searches
• Copilot Search usage breakdown per user

This feature is on by default and requires no configuration.

What you can do to prepare

No administrative action is required prior to rollout. We recommend informing relevant administrators so they can begin using the report once available.

Learn more: https://go.microsoft.com/fwlink/p/?linkid=2330630 

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Introduction

We’re retiring the Team Guidance feature in Microsoft Places. This feature allowed managers to set in-office team days and priorities. Its retirement supports Microsoft’s strategy to streamline collaboration tools and promote the use of Microsoft 365 Groups for team coordination and scheduling.

When this will happen

• August 27, 2025: Announcement phase begins
• September 29, 2025: Read-only phase begins
• November 3, 2025: Retirement phase begins; feature fully removed

How this affects your organization

During the phased retirement:

• Starting August 27, 2025:
  • Users will see a banner in the Team Guidance UI notifying them of the upcoming retirement.
• After September 29, 2025:
  • Users will no longer be able to create or edit Team Guidance entries.
  • Viewing and deleting existing entries will still be possible.
• Starting November 3, 2025:
  • Team Guidance and Workgroups will be removed from Microsoft Places.
  • Users will no longer have access to Team Guidance.
  • We recommend transitioning to Microsoft 365 Groups, which offer shared calendars, mailboxes, and collaboration tools for team coordination.

This feature is on by default and will be removed automatically.

What you can do to prepare

• Inform users of the upcoming change
• Begin transitioning to Microsoft 365 Groups for team scheduling
• Update internal training and documentation
• Visit Retirement of Places Team Guidance for migration guidance and best practices

This update complies with Microsoft’s Modern Lifecycle Policy. Over 90 days’ notice is provided to support a smooth transition.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

We've released updates to the following update channel for Microsoft 365 Apps:

• Current Channel

[When this will happen:]

We'll be gradually rolling out this update of Microsoft 365 Apps to users on that update channel starting August 26th, 2025 (PST).

[How this will affect your organization:]

If your Microsoft 365 Apps clients are configured to automatically update from the Office Content Delivery Network (CDN), then no action is required.

If you manage updates directly you can now download this latest update and begin deployment.

[What you need to do to prepare:]

To get more details about this update view the following release notes:

• Current Channel

Introduction

We hear your feedback about ways we can improve the notifications experience in Viva Engage. It’s always a fine balance between ensuring your users are notified of relevant content without notifications feeling too overwhelming or noisy. In response to your feedback, we’re rolling out an intelligent notifications experience. Specifically, this change will improve how Community Announcement notifications are delivered. This smarter delivery approach optimizes notifications delivery based on a user’s engagement behavior, helping to reduce notifications fatigue while ensuring timely visibility of announcements. 

When this will happen

General Availability (Worldwide): We will begin rolling out this change in early September 2025 and expect to complete the rollout by the end of September 2025.

How this affects your organization

Previously, when an admin created a new Community Announcement, this would send a notification in Teams and Mobile Push immediately, followed by an email notification two hours later if the announcement was not opened already in Teams and/or Mobile Push.  With this new update:

• Users will now receive the notification in one channel only—either Teams, Mobile Push, or Email. This notification channel may differ by user and is selected based on where a user has opened Engage notifications most frequently in the past 30 days. 
• If the announcement is not opened within two hours in the first notification channel, a secondary notification channel will be sent, also determined by where a user opens Engage notifications most frequently. 

We will continue to respect all user notification preferences and settings where applicable. If a notification channel is disabled or the app is not installed, it will not be selected as a potential notification channel for the Community Announcement delivery.

Note that this change applies only to regular Community Announcements in Viva Engage and does not affect the “essential” Community Announcement feature (where admins can still select the checkbox to send emails immediately —this functionality remains unchanged). 

What you can do to prepare

No admin action is required. However, we recommend:

• Informing your users about the new notifications change to reduce confusion
• Monitoring user feedback and engagement with Community Announcements’ notifications delivery
• Reviewing internal communication strategies to align with the new notification’s behavior

Introduction

We’re introducing new output control features in the Researcher Agent within Microsoft 365 Copilot. These enhancements allow users to customize the length of generated reports and select preferred output formats, improving flexibility and usability.

When this will happen: General Availability (Worldwide):

Rollout will begin in early September 2025 and is expected to complete by mid-September 2025.

How this affects your organization

This update gives users greater control over how research reports are generated and exported.

• Before generating a report, users can now select a desired length (short, comprehensive):

   

• After generation, users can choose from multiple output formats, including exporting to Word:

   

What you can do to prepare

• No action is required at this time.
• Admins may wish to inform users of the new customization options available in the Researcher Agent.

Compliance considerations

Introduction

We’re expanding access to the Data Access Governance report in SharePoint. Previously available only via SharePoint Online PowerShell, the Site permissions for your organization report is now accessible directly from the SharePoint Admin Center portal under Reports > Data Access Governance. This enhancement simplifies visibility into site-level permissions across your tenant and supports broader adoption of Microsoft Copilot.

When this will happen

General Availability: We began rolling out in mid-August 2025 and expect to complete by late August 2025.

How this affects your organization

You can now generate the Site permissions report directly from the SharePoint Admin Center portal, without needing PowerShell. This report provides insights into the exposure levels of SharePoint and OneDrive sites across your organization, helping you identify potential risks and take remedial actions. These insights are especially valuable for organizations adopting Microsoft Copilot, as they help ensure data is appropriately governed and accessible.

This feature is on by default and available to SharePoint administrators.

What you can do to prepare

• Review your current site permissions configuration to understand potential exposure.
• Notify your SharePoint administrators about the new portal-based access.
• Update internal documentation and workflows to reflect this change.

No compliance considerations have been identified, review as appropriate for your organization.

Introduction

We’re introducing a new feature: M365 Copilot Chat adoption metrics in the Microsoft Copilot dashboard. This feature provides organizations with enhanced visibility into how users who are not licensed for Microsoft 365 Copilot are engaging with Copilot Chat. These insights include usage trends, retention and intensity metrics, app-level breakdowns, and filtering by organizational attributes—helping organizations better understand adoption patterns and tailor support strategies.

This feature will be available to tenants with at least 50 assigned Viva Insights licenses or 50 assigned Microsoft 365 Copilot licenses (includes Viva Insights service plan).

This message is associated with Microsoft 365 Roadmap ID 499899.

When this will happen

General availability (Worldwide): We will begin rolling out at the end of September 2025 and expect to complete by mid-October 2025.

How this affects your organization

Users with access to the Microsoft Copilot dashboard will see new analytics cards and visualizations focused on Microsoft 365 Copilot Chat adoption for unlicensed users. These insights will appear in the dashboard’s adoption tab and include:

• Usage trends over time: Track active users and adoption growth.
• Adoption by group: Compare usage across departments or roles.
• Usage intensity and retention: Understand recurring usage and engagement levels.
• App-level breakdowns: Identify which apps and entry points drive adoption.
• Filtering and drilldown: Segment data by organizational attributes to tailor change management strategies.

This feature will be on by default for existing dashboard users. No additional administrator action is required to enable it.

What you can do to prepare

Review the impact of this feature on your organization’s reporting and privacy practices. You may also want to update internal training and documentation to reflect the new insights available.

Starting in September 2025:

• A new administrator control will be available for Global administrators, Viva Insights administrators, and AI administrators to turn off this feature at the tenant level. To disable this feature, use Viva Feature Access Management (VFAM) in Microsoft admin center or PowerShell.
• These same roles will also be able to exclude specific users or groups from being included in aggregated insights using the updated exclusion list feature.

Administrators should read the communication regarding the detailed scope and availability of this exclusion feature here (Roadmap ID: 500161).

Administrators should review any existing exclusions, assess their impact, and take appropriate action to exclude or include additional users or groups as needed.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Viva Insights | Microsoft Viva | Microsoft Learn
• Control access to features in Microsoft 365 | Microsoft Viva | Microsoft Learn
• Copilot for all: Introducing Microsoft 365 Copilot Chat | Microsoft Blog
• Manage settings for the Microsoft Copilot Dashboard and Viva Insights web app | Viva Insights | Microsoft Viva | Microsoft Learn
• Microsoft 365 Copilot overview | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

Compliance considerations

Introduction

We’re introducing smart tagging for electronically signed documents in SharePoint Online. When a document is uploaded and identified as electronically signed, it will automatically be tagged as “Signed.” This enhancement also applies retroactively— existing e-signed files will be updated with the appropriate tags.

To improve visibility and control, two optional metadata columns will be available in document libraries:

• Electronically Signed – Indicates whether a document has been e-signed.
• Signature Provider – Displays the service used for the e-signature.

This feature is available exclusively to tenants with eSignature enabled, helping streamline compliance tracking and document management.

This message is associated with Microsoft 365 Roadmap ID 500873.

When this will happen

General Availability (Worldwide): Rollout will begin in late September 2025 and is expected to complete by late November 2025.

How this affects your organization

Once eSignature is enabled, SharePoint will automatically tag e-signed documents across all sites. This improves visibility and simplifies compliance workflows. The feature is on by default for tenants with eSignature enabled.

Users will see new metadata columns in document libraries, which can be optionally added to views. No manual tagging is required.

What you can do to prepare

1. Enable eSignature in the Microsoft 365 admin center.
2. Configure your preferred eSignature provider.
3. Specify the SharePoint location for usage.

Regardless of the sites specified in item #3 above, tagging will be automatically applied to all SharePoint sites once eSignature is enabled.

Compliance considerations

Introduction

We’re expanding access to Microsoft Purview Diagnostics beyond Global Administrator to include Compliance Administrator, Security Administrator, and Organization Management roles. This enhancement enables more administrators to run diagnostics, improving visibility and troubleshooting capabilities across your compliance and security operations.

This update is associated with Microsoft 365 Roadmap ID 500894.

When this will happen

Public Preview: We will begin rolling out in late September 2025 and expect to complete by early November 2025.

General Availability (Worldwide): We will begin rolling out in mid-December 2025 and expect to complete by early January 2026.

How this affects your organization

Administrators assigned the Compliance Administrator, Security Administrator, or Organization Management roles will now be able to execute Microsoft Purview Diagnostics. This change enhances operational flexibility and reduces reliance on Global Admins for diagnostic tasks.

This feature is on by default and does not require manual enablement.

What you can do to prepare

No action is required to prepare for this update. However, we recommend reviewing role assignments to ensure appropriate access is granted.

Introduction

We’re introducing a new AI-powered report for SharePoint admins that enables comparison of site content and policies across your organization. You can select a site and compare its contents and settings with all other sites. The report provides a similarity percentage based on file content and highlights differences in site configurations and policies. This helps streamline governance by identifying opportunities to align settings across similar sites.

When this will happen

• Public Preview (Worldwide): Rollout begins early April 2025 and is expected to complete by late August 2025.
• General Availability (Worldwide): Rollout begins late August 2025 and is expected to complete by late December 2025.

How this affects your organization

This feature is optional and does not impact existing site configurations or user experiences. It provides admins with insights to support governance and policy alignment across similar sites. The report is accessible via the SharePoint admin center under Reports. It does not alter any site settings automatically.

Figure i. This feature can be found in SharePoint admin center > Reports > Site Policy configuration. 

Figure ii. Sample report

What you can do to prepare

• No preparation is required.
• You can begin using the report once it becomes available.
• A SharePoint Advanced Management (SAM) or Microsoft Copilot license is required to access this report. 

Learn more: Site policy comparison 

Compliance considerations

Updated August 27, 2025: We have updated the content. Thank you for your patience. 

 In 2023, we introduced Microsoft Teams apps that are compatible with Microsoft Outlook and the Microsoft 365 App (manifest version v1.13 or higher). Before this rollout, admin changes made in the Integrated apps section of the Microsoft 365 admin center would only affect these Teams apps in Outlook and the Microsoft 365 app. Similarly, changes made in the Teams admin center would exclusively affect Teams. Starting in June 2024, we will roll out Unified App Management to streamline the management of these apps across Teams, Outlook and the Microsoft 365 App, so they are consistently available across all supported clients.

This message is associated with Microsoft 365 Roadmap ID 393931.

[When this will happen:]

This rollout will happen in two major phases. Unified App Management can apply only to tenants that have migrated to app centric management in Teams admin center, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023).

• Phase 1 | General Availability (Worldwide): We will begin rolling out this feature end of September 2025. This initial phase targets tenants that have never modified their organization-wide defaults, app availability, or block/unblock in either the Microsoft 365 admin center or the Teams admin center. At the end of this phase, agent and app manageability will be unified across both Microsoft 365 admin center and Teams admin center ensuring agent and M365 apps availability configuration policies are in alignment for all future administrative changes.
• Phase 2: We will update this post with a timeline and more details in August 2025 (previously May 2025).  

[How this will affect your organization:]

Before this rollout, managing Teams apps that work in Outlook and the Microsoft 365 app was fragmented between the Integrated apps page in the Microsoft 365 admin center for Outlook and the Microsoft 365 app, and the Teams admin center for Teams. This sometimes resulted in different settings for the same app in the two admin centers. With Unified App Management, we will be consolidating app catalog management into a single platform. You will be able to manage apps on the Integrated apps page in the Microsoft 365 admin center or in the Teams admin center, and any changes made in either admin center will synchronize.

What you can expect

1. App catalog enhancements: Apps will start showing hosts where they are available: Teams, Outlook, or the Microsoft 365 app.
2. Organization-wide settings: App availability default settings will now apply to apps used in Teams, Outlook, and Microsoft 365 app.
3. App installs: Apps deployed from the Integrated apps page in Microsoft 365 admin center will be preinstalled in all applicable hosts for the app. Unlike app preinstallation in the Teams App setup policy, new app installs will provide access to the preinstalled apps, similar to deploying the app for Outlook and the Microsoft 365 App.. For more details on app deployment, refer to MC795355 Microsoft Teams admin center: App centric management for app installation and changes to app setup policies (May 2024)].
4. App availability: Managing app availability will apply to all applicable app hosts.
5. App block/unblock: Blocking or unblocking apps will apply to all applicable app hosts.
6. Consolidation of existing app settings: All existing app settings will be unified between Integrated apps (MAC) and Manage apps (TAC) pages. Merge rules can be found in Manage apps that work across Teams, Outlook, and Microsoft 365 | Microsoft Learn. These changes cannot be rolled back.
7. Consolidation report: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.

[What you need to do to prepare:]

We recommend that you review app and tenant settings in the Microsoft 365 admin center and the Teams admin center. If these are managed by different departments in your organization, we recommend conducting these reviews collaboratively.

We also recommend that you review the merge rules and consider their potential impact on apps in your organization. Make any necessary adjustments to unify them in advance, if the merge rules in this message do not align with your expectations.

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to update any relevant documentation as appropriate.

Updated August 27, 2025: We have updated the timeline. Thank you for your patience.

We are providing this update because your tenant is utilizing sensitivity labels and Microsoft SharePoint Online.

Coming soon: A new capability that ties together SharePoint Online library permissions and Purview sensitivity labeling and protection. We are happy to bring this capability to Public Preview. This is an opt-in feature in Microsoft PowerShell.

This message is associated with Microsoft 365 Roadmap ID 467254.

[When this will happen:]

Public Preview: We will begin rolling out mid-November 2024 and expect to complete by mid-January 2025.

General Availability (Worldwide, GCC): We will begin rolling out late mid-September 2025 and expect to complete by mid-October 2025.

General Availability (GCCHigh, DoD): We will begin rolling out mid-September 2025 and expect to complete by mid-October 2025.

[How this will affect your organization:]

After this rollout, SharePoint Online document library owners will be able to apply a sensitivity label at the library level, automatically applying that label to all unprotected and unlabeled files (Microsoft Word, Microsoft Excel, Microsoft PowerPoint, and PDFs) in the target library. This simplifies labeling in bulk across document libraries in an organization. This capability also helps protect files as they egress from the original document library, such as for collaboration purposes or attempted exfiltration. Files downloaded from these libraries are protected at download. Users accessing these files outside of SharePoint Online have their rights evaluated in real time against the document library. Changes to user permissions on the document library are reflected on downloaded files, including full revocation for users removed from the document library. This provides a more streamlined way to revoke access to documents for individual users (instead of revoking access to each document).

Learn more about how to use this feature and its capabilities, limitations, and licensing: Configure SharePoint with a sensitivity label to extend permissions to downloaded documents | Microsoft Learn

[What you need to do to prepare:]

After this feature is available, we recommend you test this feature first on sites with non-production data to understand its capabilities.

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review the referenced documentation links to learn more about enabling this feature.

Updated August 28, 2025: We have updated the timeline below. Thank you for your patience.

Within Microsoft Purview Data Security Posture Management for AI, OneDrive will be added to data risk assessments as a supported location.

This message is associated with Microsoft 365 Roadmap ID 488808.

[When this will happen:]

Public Preview: We will begin rolling out in mid-May 2025 and expect to complete by late May 2025.

General Availability (Worldwide): We will begin rolling out mid-October 2025 and expect to complete by mid-November 2025

[How this will affect your organization:]

[What you need to do to prepare:]

Updated August 28, 2025: We have updated the timeline. Thank you for your patience.

Coming soon to Microsoft Teams: When users connect to their organization’s Wi-Fi, Teams can automatically set their work location to reflect the building they are working in. This feature is opt-in and requires you to take action to configure it.

This message applies to Teams for Windows desktop and Teams for Mac desktop.

This message is associated with Microsoft 365 Roadmap ID 488800.

[When this will happen:]

General Availability (Worldwide): We will begin rolling early October 2025 and expect to complete by mid-October 2025.

[How this will affect your organization:]

This feature allows you to map Wi-Fi networks and devices to buildings, which allows your users to have their work location automatically configured when they connect. This is a major improvement over the current experience which relies on end-users to manually set their work location. When this feature is configured and enabled, Teams can automatically update the work location of users who connect their laptop to your organization’s Wi-Fi network or peripherals. The feature can leverage the mapping between your building names and your Wi-Fi networks to set the work location of your users to the right building. It can also leverage mappings to specific peripherals, such as monitors. Teams uses the same policy to enable or disable automatic updates of work location for Wi-Fi and peripherals. Learn more: New-CsTeamsWorkLocationDetectionPolicy (MicrosoftTeamsPowerShell) | Microsoft Learn

Teams will not update the location of your users if they connect after their working hours (that they can configure in the Microsoft Outlook Calendar). Also, their work location will be cleared at the end of their working hours.

[What you need to do to prepare:]

Automatic update of work location is off by default, but it can greatly improve the experience of your users. We recommend turning it on and configuring it in your tenant.

Before rollout, we will update this post with new documentation.

Updated June 27, 2025: We have updated the timeline below. Thank you for your patience.

Copilot Dashboard users can now view metrics that reflect both summarized and recapped meeting activity, offering a more complete view of Copilot’s impact in Teams. These updates replace previous Copilot Assisted Hour calculations and meeting metrics with unified “summarized or recapped” metrics, helping leaders better understand usage across their organization. The updated metrics are available in both the Copilot Dashboard and the M365 Copilot Impact report in Advanced Insights, with additional query support for Intelligent Recap meeting metrics.

This change is associated with Microsoft 365 Roadmap ID: 494687 

[When this will happen:]

Public Preview: We will begin rolling out this change late September 2025 (previously late July) and expect to complete by late October 2025 (previously late September).

General Availability (Worldwide): We will begin rolling out this change late October 2025 (previously late September) and expect to complete by late November 2025 (previously late October).

[How this will affect your organization:]

• Copilot Assisted Hours and Value calculations: values displayed under these metrics will increase, including for prior months, since these numbers will now include meetings where users accessed Intelligent Recap feature on Microsoft Teams.

  

• Meetings card: meeting hours and meetings summarized metrics will be updated to include meetings where Intelligent Recap was accessed.

  

Users who have access to Advanced Insights will see similar updates in the M365 Copilot Impact report. They will also be able to include “Meetings recapped” and “Meeting hours recapped” metrics in their flexible queries.

[What you need to do to prepare:]

The changes mentioned do not impact eligibility criteria to access the M365 Copilot Dashboard or the Microsoft 365 Copilot Impact report on Advanced Insights.

To view the updated metrics in Advanced Insights, you can access the pre-computed Microsoft 365 Copilot Impact report. You can also set-up your own query to customize metrics and additional organizational attributes.

To learn more, please see the following:

1. How to access the Copilot Dashboard and understand Copilot Assisted Hours metrics: Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn
2. To access the Microsoft 365 Copilot Impact report and understand Copilot Assisted Hours metrics: Microsoft 365 Copilot impact report | Microsoft Learn 
3. How we define Copilot meeting metrics: Advanced insights metric descriptions | Microsoft Learn 
4. How to access Advanced Insights: Introduction to advanced insights | Microsoft Learn

Updated August 28, 2025: Due to the customer feedback we’ve received, we will be delaying the legacy Message Trace support on Reporting Webservice until February 28th, 2026. Additionally, we will be onboarding the new Message Trace onto Graph API. The tentative timeline for Public Preview of the new Message Trace support on Graph API is November. Further details will be announced closer to the Public Preview release date.

This does not impact the deprecation timeline for the legacy Message Trace cmdlets. The legacy Message Trace cmdlets (Get-MessageTrace, Get-MessageTraceDetail) are still set to retire on September 1st, 2025.

We are excited to announce the General Availability of the new Message Trace in the Microsoft Exchange admin center (EAC) in Microsoft Exchange Online. This new experience, previously in Public Preview, offers improved performance, modern design, and enhanced feature parity. Admins can access it via Exchange admin center > Mail flow > Message Trace.

The GA release is associated with Microsoft 365 Roadmap ID 495489.

[When this will happen:]

• Retirement of legacy Message Trace begins September 1, 2025.
• General Availability (Worldwide): We will begin rolling out mid-June and expect to complete by late July.

[How this will affect your organization:]

• Like in Public Preview, the new Message Trace UX in EAC will be available by default and Microsoft PowerShell cmdlets (Get-MessageTraceV2, Get-MessageTraceDetailV2) will be available.
• The legacy Message Trace experience and cmdlets (Get-MessageTrace, Get-MessageTraceDetail) will remain available in parallel for several months to support the transition.
• Starting September 1, 2025, the following will begin deprecating:
  • Legacy Message Trace UI in EAC.
  • Legacy cmdlets (Get-MessageTrace, Get-MessageTraceDetail).
• Starting February 28th, 2026, Reporting Web Service support for Message Trace data will begin deprecating. 

[What you need to do to prepare:]

This GA rollout and retirement 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 admins and/or users about this change and update internal documentation.

• Begin using the new Message Trace experience in the Exchange admin center.
• Update any automation or scripts using legacy cmdlets to use the new versions by August 31, 2025.
• If you rely on the Reporting Web Service for Message Trace data, migrate to the new PowerShell cmdlets by February 28, 2026.
• To provide feedback on the new Message Trace, use Exchange admin center > Give Feedback.

Learn more about the GA rollout: Announcing General Availability (GA) of the New Message Trace in Exchange Online | Microsoft Community Hub (documentation will be linked to this blog before rollout)

Updated August 28, 2025: We have updated the timeline. Thank you for your patience.

We’re updating the Microsoft SharePoint site header and footer to deliver a more modern, customizable, and brand-aligned experience. This visual enhancement introduces new options for customizing the header, footer, and navigation links—empowering site owners to better reflect their organization’s identity and create more engaging, connected SharePoint sites.

This message is associated with Microsoft 365 Roadmap ID 489225.

[When this will happen:]

Targeted Release: We will begin rolling out late August 2025 (previously mid-August) and expect to complete by early September 2025 (previously late August).

General Availability (Worldwide, GCC): We will begin rolling out early September 2025 (previously late August) and expect to complete by mid-September 2025 (previously early September).

General Availability (GCC High, DoD): We will start rolling out mid-September 2025 (previously early September) and expect to complete by late September 2025.

[How this will affect your organization:]

These updates will enhance the visual consistency and usability of SharePoint sites, making it easier to deliver visually compelling, on-brand experiences across your organization.

For site viewers:

• The command bar will be hidden in View mode for a cleaner, more immersive experience.
• Teaching tips will help users locate previously available command bar buttons in the header.

For site owners:

New design flexibility will include:

• Set an image as the header or footer background and customize the overlay color.
• Change fonts for the site title, navigation links, footer name, and footer links using a set of predefined font families.
• Adjust footer alignment, including support for left alignment.

This change will be on by default.

After this rollout, site admins can customize the header background under the new Design tab in the Header configuration panel:

Site viewers will have a cleaner, more immersive experience with the command bar hidden in View mode.

[What you need to do to prepare:]

This rollout will happen automatically with no admin action required. You may want to notify your users about this change and update any relevant documentation as appropriate.

Before rollout, we will update this post with new documentation.

Updated August 28, 2025: We have updated the content. Thank you for your patience.

We’re updating the product licensing experience in the Microsoft Admin Center to make it easier for admins to distinguish between direct and group-based license assignments. This update improves clarity and performance on the product licensing pages (Billing > Licenses), helping you quickly understand how licenses are assigned and to whom.

[When this will happen:]

Rollout will begin in late June 2025 and is expected to complete by late September 2025 (previously late July). 

[How this will affect your organization:]

Admins will see a new layout on the product licensing pages:

• Users with directly assigned licenses will appear in the User tab.
• Users assigned via Group-Based Licensing (GBL) will appear in the Groups tab.
• Product names have been updated and now offer improved multilingual support.

To view users assigned via GBL, select the group name from the list of group assignments for that product, then navigate to the Successfully assigned tab.

This change is designed to improve page load performance and make license assignment paths more intuitive.

[What you can do to prepare:]

Review and update any internal documentation, training materials, or processes that assume all license assignments appear in the User tab. After this update, license assignments will be split between the User and Groups tabs based on how the license was assigned.

Updated August 28, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing a new capability in Microsoft Purview Information Protection: On-demand classification of files on Windows devices. This feature will enable you to discover and classify sensitive content stored on devices, helping to strengthen your data security posture and meet compliance requirements.

This capability is especially useful for:

• Investigating potential incidents or exposure risks
• Surfacing older files that weren’t captured in Data Loss Prevention (DLP) activity logs
• Identifying sensitive content in place for audit or compliance use

This message is associated with Microsoft 365 Roadmap ID 496593.

[When this will happen:]

Public Preview: We will begin rolling out mid-September 2025 and expect to complete by late September 2025.

General Availability (Worldwide): We will begin rolling out mid-November 2025 and expect to complete by late November 2025.

[How this will affect your organization:]

After this rollout, admins can access this feature in Purview Information Protection at Data Loss Protection > Classifiers > On-demand classification: 

There will be no impact to existing Purview configuration or user experience by default. You can choose to use this capability to discover existing content and apply applicable policies.

[What you need to do to prepare:]

No immediate action is required. Once available, you can initiate scans on Windows devices to classify existing data based on your organization’s compliance or security needs. Before rollout, we will update the following post: On-demand classification (preview) – Microsoft Purview | Microsoft Learn.

[Compliance considerations:]

• Does the change modify, interrupt, or disable any audit logging capabilities (Purview): Yes. – New audit event introduced.

Updated August 28, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Microsoft 365 Copilot in PowerPoint will soon support the use of your organization’s branded images when creating slides. By integrating enterprise assets stored in SharePoint Organization Asset Libraries (OAL) or Templafy (third-party solution), users can generate slides that use your brand images.

This message is associated with Microsoft 365 Roadmap IDs 496365, 496366, and 496367.

When this will happen

General Availability (Worldwide): We will begin rolling out in early September 2025 (previously late August) and expect to complete by late October 2025 (previously late September).

How this will affect your organization

After this rollout, brand managers and admins can connect enterprise image libraries from either SharePoint Organization Asset Libraries (OAL) or Templafy to Microsoft 365 Copilot in PowerPoint. Once connected, users will be able to generate slides using branded images from your organization’s asset library, helping ensure brand consistency.

This feature will be available by default for admins to configure. If no enterprise image library is connected, the option to use branded images will be disabled in the image source menu, and only Microsoft 365 images will be available.

Sharepoint OAL setup

To enable this feature with SharePoint OAL, admins must:

• Create an organization asset library in SharePoint for your company’s brand images.
• Run a Microsoft PowerShell command to connect the image library to Microsoft 365 Copilot.
• Ensure that images include robust metadata (keywords, titles, and alt-text) to support searchability.

Templafy setup

To enable this feature with Templafy, admins must:

• Have an active Templafy account configured with your company’s brand assets.
• Enable the Microsoft Graph Connector in your Templafy account settings to establish the Copilot connection.
• Ensure that images include robust metadata (keywords, titles, and alt-text) to support searchability.

Once setup is complete, users can select the New Slide Copilot icon in the PowerPoint ribbon, enter a prompt, and choose their preferred image source—either Microsoft 365 images or their organization’s branded image library—via the Image Source menu.

Admins can email [email protected] to request connection of their enterprise assets to Copilot in PowerPoint.

Note: We recommend enabling this feature only if your image library contains more than 1,000 images with robust metadata.

After setup, the option to select branded images from your organization’s library will be enabled when generating slides with Copilot in PowerPoint: 

Copilot in PowerPoint allows users to enter a prompt and choose image sources, including your organization’s branded image library, if connected.: 

What you can do to prepare:

Admins should:

• Notify brand managers of this new capability.
• Decide if you’d like to connect SharePoint OAL or Templafy to Copilot. Email [email protected] to connect enterprise assets.
• If enabled, inform employees that Copilot in PowerPoint can now use organizational images when generating slides.

Learn more: Keep your presentation on-brand with Copilot | Copilot in PowerPoint

Compliance considerations:

Does the change alter how existing customer data is processed, stored, or accessed? – Maybe. If the image libraries contain sensitive or regulated content, enabling Copilot to access and use them could change how that data is accessed and surfaced.

Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? – Yes. This feature expands Copilot’s generative AI capabilities by integrating branded image libraries into slide generation.

Does the change provide users any new way of interacting with generative AI? – Yes. Users will be able to generate slides with Copilot that automatically incorporate organizational images, which is a new interaction model.

Updated August 28, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing the ability to reference a PDF file when creating a slide using Copilot in PowerPoint. This enhancement enables users to extract and reuse content from cloud-stored PDFs, streamlining slide creation and improving productivity.

This feature is associated with Microsoft 365 Roadmap IDs 497536, 497540, and 497541. 

When this will happen

General Availability (Worldwide): We will begin rolling out in mid-October late (previously August 2025) and expect to complete by late November 2025 (previously late September).

How this will affect your organization

With this update, users can reference PDF files stored in OneDrive or SharePoint when using the “New Slide with Copilot” button in PowerPoint or the “Add a slide” option from the Copilot pane. Copilot will access the entire PDF file (text-based only) to generate slide content.

Key details:

• Supported files: Text-based PDFs stored in OneDrive or SharePoint. Password-protected or scanned/image-based PDFs are not supported.
• File size: Recommended maximum size is 24MB for optimal performance.
• Platform support: Available across PowerPoint for Windows, Mac, and Web.
• Prompting guidance: Users can click the paperclip icon or use the backslash (\) to reference a file. For large files, including the topic of interest in the prompt improves results.
• Licensing: Requires the Microsoft 365 Copilot add-on ($30/user/month). Not available with Copilot included in Microsoft 365 SKUs alone.
• Availability: This feature is available to tenants with Copilot enabled. There are no admin controls to enable or disable it.
• User control: Users can choose to keep or delete Copilot-generated slides.
• Telemetry: Usage of this feature is tracked.

This feature does not remove or alter any existing functionality. It is being added to the existing “New Slide with Copilot” experience.

What you need to do to prepare

• Inform your users about this new capability.
• Encourage them to explore how referencing PDFs can help them create slides more efficiently.
• No admin action is required for this update.

Learn more: Add a slide from a file with Copilot in PowerPoint

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated August 28, 2025: This request flow applies exclusively to agents built by Microsoft and does not extend to other agents available in the store.

Introduction

We’re introducing a new request and approval experience in the Microsoft 365 admin center for Microsoft agents. This update enables users to request access to agents—even those currently unavailable due to your organization’s configuration—directly from the Agent Store.

You can manage these requests centrally from the Copilot > Agents & connectors page in the Microsoft 365 admin center, streamlining access control and improving visibility into user interest.

This message is associated with Microsoft 365 Roadmap ID 494809.

When this will happen

Rollout will begin late September2025 (previously mid-August) and complete in mid-October 2025 (previously early September).

How this affects your organization

This update enhances flexibility and transparency in agent access management:

• Admins retain full control over access decisions and benefit from:
  • Centralized management of agent access requests.
  • Granular control to approve or reject requests at the individual user level.

This feature is on by default and requires no configuration to enable.

What you can do to prepare

No setup is required—this feature will roll out automatically.

To prepare:

• Visit the Copilot > Agents & connectors page in the Microsoft 365 admin center to view and manage agent access requests.
• Approve or reject requests based on your organization’s policies.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Updated August 28, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Microsoft Teams is introducing noise suppression for PSTN dial-in participants in Audio Conferences. This feature automatically reduces background noise—such as traffic or keyboard sounds—enhancing audio clarity for users joining meetings via phone.

• Targeted Release (Worldwide): Rollout begins in October 2025 and is expected to complete by late October 2025.
• General Availability (Worldwide, GCC, GCC High, and DoD): Rollout begins late October 2025 and is expected to complete by late November 2025

How this will affect your organization

Introduction

We’re introducing a new Open in Word action button in Microsoft 365 Copilot Chat. This feature allows users to seamlessly transfer Copilot-generated responses into Microsoft Word for further editing, formatting, or collaboration. It enhances productivity by bridging AI-generated content with familiar document workflows.

When this will happen

General Availability (Worldwide): Rollout begins in mid-September 2025 and is expected to complete by late September 2025.

How this affects your organization

Users with a Copilot license will see a new Open in Word button within Microsoft 365 Copilot Chat. This feature is on by default and requires no configuration. It enables users to move Copilot responses directly into Word, streamlining content creation and editing workflows.

There is no impact to existing workflows or user permissions. The feature is designed to enhance usability without requiring training or support.

What you can do to prepare

• No admin action is required. The feature will be available automatically to all users with a Copilot license.
• You may wish to inform users about this new capability to encourage adoption and improve productivity.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Introduction

Scoped knowledge is now supported in declarative agents (DA) for VIP connectors such as Azure DevOps (ADO) Work Items, Jira, and Confluence. This enhancement enables organizations to define precise boundaries for agent-accessible information, improving relevance, reducing noise, and aligning with organizational policies and user permissions.

This feature is available to tenants with a Microsoft 365 E5 license.

General Availability (Worldwide): We will begin rolling out in late August 2025 and expect to complete by early September 2025.

Once configured, scoped knowledge allows users to prompt Copilot with more personalized queries. This is especially useful for creating targeted agents tied to specific repositories or locations, helping reduce irrelevant results and improving agent performance. This helps you create agents that are scoped to your team’s knowledge, enabling more personalized responses to queries.

Tenants without Microsoft 365 E5 will not have access to this feature unless they upgrade.

What you can do to prepare

To configure scoped knowledge in declarative agents:

1. Under Choose other data sources, select the connector tile (such as Jira, Confluence).
2. Add relevant connections.
3. Return to the Knowledge main menu.
4. Select a scoping attribute (such as Project, Space, Folder).
5. Search or type the attribute name and add the desired scope.

Screenshot – Scoped knowledge configuration options in declarative agents for VIP connectors:

Learn more: Add knowledge sources to your declarative agent by using agent builder | Extensibility | Microsoft 365 Copilot | Microsoft Learn

No compliance considerations identified, review as appropriate for your organization.

Introduction

We’re pleased to announce the availability of SharePoint agents in the Microsoft Teams app store. These agents enable users to interact with SharePoint content directly within Teams, offering intelligent assistance for document discovery, content summarization, and collaboration.

By discovering and utilizing the most recently used agents personalized to each user, users can quickly access the most relevant SharePoint agents to use them in their flow of work. Up to 25 agents will appear towards the end of the agents section on the store. Users can find the agent details by selecting a listing, and choose to add them to chats or channels to streamline their workflows.

This message is associated with Microsoft 365 Roadmap ID 481824.

When this will happen

General Availability (Worldwide): Rollout begins in late August 2025 and is expected to complete by late August 2025.

How this affects your organization

This update introduces a new way for users to interact with SharePoint content using intelligent agents within Teams. The agents are personalized per user and cannot be centrally managed or hidden from the store by admins. This may increase visibility of SharePoint content and usage within Teams.

The feature is on by default and does not require configuration.

What you can do to prepare

• Review existing SharePoint agent management methods to ensure alignment with organizational policies.
• Inform users that agent visibility in the store is personalized and based on their activity and shared content.
• If a user has never used a SharePoint agent, it won’t appear—so there’s no need to worry about irrelevant agents showing up.
• No additional admin controls are available to manage agent visibility in the store.
• We will update this post with new documentation soon.

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Introduction:

Microsoft Purview Insider Risk Management is enhancing policy configuration by enabling the selection of multiple Data Loss Prevention (DLP) policies as triggering events. Previously, only one DLP policy could be selected per Insider Risk Management policy. This update provides greater flexibility and alignment with complex organizational risk scenarios.

This message is associated with Microsoft 365 Roadmap ID 493756

When this will happen:

• Public Preview: Rollout will begin in late August 2025 and is expected to complete by mid-September 2025.
• General Availability (Commercial and Government Clouds): Rollout will begin in early December 2025 and is expected to complete by late December 2025.

How this affects your organization:

This update does not change existing configurations or require any action. It simply allows eligible admins to select multiple DLP policies as triggering events when creating or editing Insider Risk Management policies. This enhancement supports more comprehensive risk detection scenarios and improves policy customization.

What you can do to prepare:

No preparation is needed. However, you may wish to review your current Insider Risk Management policies and consider whether leveraging multiple DLP triggers could improve your risk detection strategy. 

Compliance considerations:

• Enhanced configuration experience: Enterprises can view the number of available and used IP addresses in a subnet. They can also troubleshoot configuration issues when the Virtual Network isn’t configured on a Power Platform environment.
• Extended connectors support for Virtual Networks: Support is now available for more connectors, including Azure AI Search and data export to Application Insights.

• A daily summary of Microsoft Outlook meetings and Microsoft To Do items, allowing you to easily log time entries based on your agenda.
• The ability to see all projects and tasks assigned to you, along with the duration of each project assignment.
• A day-by-day overview of your time entries by status (Draft, Submitted, etc.), with options to edit or delete entries, submit for approval, or recall submissions.
• Access to a new timer function for tracking time spent on specific tasks. You can later assign a timer record to a project or task to create a corresponding time entry.

• A new calendar interface to view, create, and change time entries.
• The ability to track time across different timelines, such as weekly or monthly.
• Tighter integration of the work breakdown structure for assigned tasks and projects within the time entry creation step (quick create forms).
• Improved tracking with benchmarking of actual versus target hours and visualizations that help team members track their progress on project tasks.

• The existing validation in the Global project management and accounting parameters form is relaxed to allow legal entities with existing project data to enable resource and nonstock deployment types.
• The Global project management and accounting parameters validation checks that all projects are closed for the 10.0.43 release and allows for a new start. For the 10.0.45 release, we allow for projects to remain open with a subset of transaction types and processes supported for existing PMA projects.
• Evaluate business processes to make sure they restrict the appropriate deployment types. For example, you can create invoices for Dataverse-based projects only from Dataverse.
• We remove access or make read-only the legacy functions that exist in both deployment types. For example, when you enable this feature, you can’t edit resource management and project work breakdown structures in the finance and operations user interface for the resource/non-stocked deployment mode. For projects you create in resource/non-stocked deployment mode, use Unified Resource Scheduling experiences for resource scheduling, and Project for the Web experiences for project planning.

• Start or end a conversation.
• Start a conversation with an authentication token.
• Present options for persistent conversations and context variables.
• Send messages, including attachments and updates to context variables.
• Receive agent or system messages through webhook subscriptions.
• Check agent availability in a queue and retrieve both queue position and estimated wait time.

• KB5014754: Certificate-based authentication changes on Windows domain controllers.

Updated August 28, 2025: We have updated the timeline. Thank you for your patience.

What is happening: We have a systems update scheduled between (1 Feb – 2 Feb, 2025). This update is for Export-ContentExplorerData PowerShell Cmdlet

How it impacts you: During the update, any Cmdlet-based scripts running at that time might experience failures for some of the Cmdlet calls. To avoid any disruptions, we recommend running your scripts after 3 Feb 2025, when the updates will be fully in place and operational.

Which Cmdlets were impacted: 1. Export-ContentExplorerData

What do you need to do?

• Avoid running Cmdlet-based scripts during the (1 Feb – 2 Feb 2025) update.

• Resume running your scripts on 3 Feb 2025 to ensure smooth operation.

We apologize for any inconvenience this may cause and appreciate your understanding and cooperation. If you have any questions or need further assistance, please do not hesitate to reach out to our support team.

The current Content Explorer Export feature has a limitation of exporting data only after drilling down to specific location. The new feature coming to General Availability will allow admins to use a new cmdlet within the Security and Compliance PowerShell, Export-ContentExplorerData, to export all rows of data for the content that are scanned and shown on Content Explorer.

This message is associated with Microsoft 365 Roadmap ID 117546

[When this will happen:]

Rollout will begin late July 2025 (previously late April) and is expected to be complete by early September (previously mid-August 2025).

[How this will affect your organization:]

This feature can be accessed through the Security and Compliance PowerShell, Export-ContentExplorerData.

[What you need to do to prepare:]

There are no additional settings needed for this feature. You may want to notify your users about this change and update any relevant documentation as appropriate. 

Updated August 29, 2025: We have updated the timeline. Thank you for your patience.

Microsoft PowerPoint for Mac is introducing a new Copilot capability that helps users expand their presentations by generating new topic ideas and corresponding slides. These slides will match the look and feel of the existing presentation, ensuring a seamless experience.

This message is associated with Microsoft 365 Roadmap ID 496138

[When this will happen:]

General Availability: Rollout will begin in early September 2025 (previously mid-August) for PowerPoint on Mac desktop.

[How this will affect your organization:]

With this update, users can prompt Copilot to generate and insert new content into their existing presentations. Copilot will create slides that are visually consistent with the current deck. Users can initiate this by entering a prompt or referencing a file. This feature enhances productivity by streamlining content creation and maintaining design consistency.

A Microsoft 365 license is required to access this Copilot feature.

[What you can do to prepare:]

No admin action is required prior to rollout. You may wish to inform your users about this new capability and update any relevant training or documentation to reflect the change.

[Compliance considerations:]

• Alters how existing customer data is processed, stored, or accessed: Maybe – If users reference existing files or content, Copilot may process that data to generate new slides. However, it does not change how the data is stored or accessed within Microsoft 365.
• Introduces or modifies AI/ML capabilities that interact with customer data: Yes – This update introduces a generative AI capability (Copilot) that processes user input and referenced content to generate new slides, directly interacting with customer data.
• Provides end users a new way of interacting with generative AI: Yes – Users can now interact with Copilot to generate new presentation content, representing a new method of engaging with generative AI in PowerPoint.

Updated August 29, 2025: We have updated the timeline. Thank you for your patience.

Microsoft PowerPoint for Windows desktop is introducing a new Copilot capability that helps users expand their presentations by generating new topic ideas and slides. This feature ensures that added content matches the look and feel of the existing presentation, enhancing productivity and consistency.

This message is associated with Microsoft 365 Roadmap ID 496137

[When this will happen:]

General Availability (GA): Rollout will begin in early September 2025 (previously mid-August) for PowerPoint on Windows desktop.

[How this will affect your organization:]

With this update, users can prompt Copilot to generate and insert new topics and slides into their existing presentations. The generated content will maintain the visual style and formatting of the original presentation. Users can initiate this by providing a prompt or referencing a file. A Microsoft 365 license is required to access this feature.

[What you can do to prepare:]

No admin action is required before the rollout. You may want to inform your users about this new capability and update any relevant training or documentation to reflect the change.

[Compliance considerations:]

• Alters how existing customer data is processed, stored, or accessed: Maybe – If users reference existing files to generate new content, Copilot may process that data temporarily to generate results. However, it does not change how the data is stored or accessed long-term.
• Introduces or modifies AI/ML capabilities that interact with customer data: Yes – This feature introduces a new generative AI capability that processes user prompts and referenced content to generate slides, directly interacting with customer data.
• Provides end users a new way of interacting with generative AI: Yes – Users can now interact with Copilot to generate new presentation content, representing a new generative AI interaction model within PowerPoint.

Updated August 29, 2025: We have updated the timeline. Thank you for your patience.

Microsoft PowerPoint for Windows desktop is introducing a new Copilot capability that helps users expand their presentations with ease. This feature allows users to generate and insert new topic(s) and slides that match the look and feel of their existing presentation—streamlining content creation and maintaining visual consistency.

This message is associated with Microsoft 365 Roadmap ID 496136

[When this will happen:]

General Availability (Worldwide): Rollout begins in early September 2025 (previously mid-August) for PowerPoint on Windows desktop.

[How this affects your organization:]

With this update, users can prompt Copilot to generate new content or reference a file to add topic-specific slides. The generated slides will automatically align with the design and formatting of the current presentation, reducing manual effort and ensuring a cohesive experience.

This feature is on by default.

A Microsoft 365 license is required to access this Copilot functionality.

[What you can do to prepare:]

No admin action is required prior to rollout. However, you may want to:

• Inform your users about this new capability.
• Update internal training materials or documentation to reflect this enhancement.
• Ensure users have the appropriate Microsoft 365 license to access Copilot features.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Maybe – Copilot may reference existing content to generate new slides.
• Does the change introduce or significantly modify AI/ML or agent capabilities? Yes – Introduces new generative AI capabilities in PowerPoint.
• Does the change provide end users a new way of interacting with generative AI? Yes – Users can prompt Copilot to generate new content within presentations.

Updated August 29, 2025: We have updated the content. Thank you for your patience.

Disclaimer: The original message center post was published on August 1, 2025. We previously stated that this is a new feature when it is an expanded capability of the existing feature memory in Copilot. This expanded capability requires new processing of users’ data, which is outlined below. We have edited the content below for accuracy and clarity. Thank you to the customers who provided feedback over the past few weeks. We have adjusted our roadmap to address your needs and concerns. 

Starting September 1, 2025, Microsoft 365 Copilot will start remembering key highlights from your person-to-person communications in chats, emails, and meetings. Initially these memories will be used to improve the quality of Copilot responses to people-related questions. These memories are private to the user. This feature is available to Copilot-licensed enterprise users.

This message is associated with Microsoft 365 Roadmap ID 499153

Updated August 29, 2025: We have updated the timeline. Thank you for your patience.

The new Outlook for Windows and Outlook for the Web now support email templates, enabling users to create, save, and reuse templates for faster, more consistent communication. This update also supports importing existing templates saved as .oft files, streamlining the transition from classic Outlook experiences.

This message is associated with Microsoft 365 Roadmap ID: 485757

Targeted Release (Worldwide): Rollout will begin in early September 2025 (previously late August) and is expected to complete by mid-September 2025 (previously early September).

General Availability (Worldwide): Rollout will begin in mid-October 2025 (previously early October) and is expected to complete by early November 2025 (previously late November).

General Availability (GCC, GCC High, DoD): Rollout will begin in early November 2025 (previously early-October) and is expected to complete by early December 2025 (previously late November).

• Create, edit, and use templates directly from the compose window.
• Manage templates via the Settings page.
• Access saved templates across devices and between the new Outlook and Outlook on the web.

Templates are stored in the user’s account, allowing them to roam with the user for a consistent experience across devices. This feature is on by default and requires no admin configuration.

No action is required to prepare for this change. You may wish to inform your users about the new template functionality to help them take advantage of it once available.

#newoutlookforwindows

Updated August 29, 2025: We have updated the timeline. Thank you for your patience.

Sections with AI in SharePoint Pages

We’re introducing Sections with AI, a new SharePoint authoring experience that enables users to generate rich, full-fidelity page sections using natural language prompts. This feature leverages Copilot to understand page context, suggest relevant content, and generate dynamic sections that incorporate organizational knowledge, documents, and meeting transcripts. This enhancement simplifies content creation and improves productivity by reducing manual effort and enabling more intelligent, context-aware page building.

This message is associated with Microsoft 365 Roadmap 498547

General Availability (Worldwide): Rollout begins early September 2025 (previously mid-August) and is expected to complete by mid-November 2025 (previously mid-October).

Sections with AI will be automatically available to all SharePoint tenants with a Copilot license. This feature introduces a new way for users to create rich, full-fidelity sections on SharePoint pages using natural language prompts.

Users can:

• Add a section using AI

• Choose a prompt or write your own

• View and select multiple generated sections

• Refine your section with a prompt

These steps allow users to:

• Select or write prompts to generate new sections.
• Ground prompts in relevant files for more accurate results.
• Toggle between multiple generated options and choose their favorite.
• Refine both content and layout using natural language commands (e.g., “make the text more professional” or “add John Smith’s contact information”).
• Add the final section to the page canvas and edit it like any other section.

This feature is on by default for eligible tenants.

What you can do to prepare

• No admin action is required for enablement.
• Consider notifying your users about this new capability and its benefits. 

Updated August 29, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re expanding AI capabilities to SharePoint document libraries in Microsoft 365 on the web. AI file actions—already available in OneDrive—will now be accessible in SharePoint, enabling users to summarize content, compare files, generate FAQs, ask questions, and create audio overviews directly from document libraries.

This message is associated with Microsoft 365 Roadmap 488297.

• Targeted Release (Worldwide): Rollout will begin early September 2025 and complete by mid-October 2025.
• General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-September 2025 and complete by mid-October 2025.

Figure i. You can access AI actions from the “AI Actions” button in the toolbar in document libraries in SharePoint

Figure ii. You can also find these actions when you select or hover over an item in a document library

AI file actions will be available to all users with a Copilot license in SharePoint document libraries on the web. These actions mirror those currently available in OneDrive and offer enhanced productivity by enabling users to interact with files using natural language prompts.

This feature is on by default and does not require admin configuration.

• No action is required to enable this feature.
• We recommend informing your users about the new capabilities and reviewing Copilot licensing to ensure appropriate access.

Compliance considerations

Introduction

To improve email deliverability and reduce abuse, Microsoft is introducing outbound email throttling for default MOERA domains (e.g., contoso.onmicrosoft.com). These domains are intended for initial tenant setup and testing—not for regular email traffic. This change encourages organizations to adopt custom domains with independent reputations.

When this will happen

General Availability (Worldwide): Rollout begins mid-October 2025 and will complete by early June 2026. Rollout timing will vary based on organization seat counts. For detailed rollout information, refer to Limiting Onmicrosoft Domain Usage for Sending Emails.

How this affects your organization

Organizations sending outbound email from onmicrosoft.com domains will be subject to throttling limits:

• Outbound email to external recipients will be capped at 100 messages per organization per 24-hour rolling window.
• Once the limit is reached, senders will receive non-delivery reports (NDRs) with error code 550 5.7.236.
• Internal and inbound email traffic will not be affected.

This change is on by default and does not require admin enablement.

What you can do to prepare

Take the following actions:

• Use Message Trace in the Exchange Admin Center to identify mailboxes using MOERA domains.
• Purchase and configure a custom domain for your organization.
• Set the custom domain as the default domain in the Microsoft 365 Admin Center.
• Update user mailboxes to use the custom domain as their primary SMTP address.
• Review and update authentication credentials for devices and apps using MOERA-based usernames.
• Ensure apps like Bookings and Microsoft notifications are configured to use your custom domain.

Learn more: Limiting Onmicrosoft Domain Usage for Sending Emails

Compliance considerations

Introduction

Cloud Update is now generally available in the Microsoft 365 Apps admin center (config.office.com), bringing modern, cloud-based controls to help you keep Microsoft 365 Apps current, secure, and Copilot-ready with less effort.

With Cloud Update, you can assign custom rollout waves, set exclusion windows for business-critical freeze periods, pause deployments, and roll back if needed—all from a single, lightweight experience.

When this will happen

General Availability (Worldwide): The rollout began in early August 2025 and is now complete.

How this affects your organization

• If you participated in the preview: You will see the same experience, now without “Preview” labels.
• If you are new to Cloud Update: You can now simplify monthly update management for Microsoft 365 Apps using automation.

Key benefits:

• Simpler, safer monthly updating: Automate servicing while retaining control with pause, rollback, exclusion windows, and custom rollout waves.
• Copilot readiness: Keeping devices on a supported monthly channel and managed by Cloud Update helps ensure readiness for Microsoft 365 Copilot experiences.
• Centralized management: Enable and manage Cloud Update in the Microsoft 365 Apps admin center (config.office.com).

Screenshot 1 – Cloud Update dashboard shows overall progress and profile status: 

Screenshot 2 – Monthly Enterprise profile dashboard shows wave rollout progress and management controls: 

This feature is off by default and must be enabled by an admin.

What you can do to prepare

Before enabling Cloud Update, review the following prerequisites:

Supported admin roles:

• Office Apps Administrator (recommended)
• Security Administrator
• Global Administrator

Note: Global Reader is supported in the admin center but cannot manage Cloud Update.

Supported subscription plans:

• Education: Microsoft 365 A3, A5
• Business: Microsoft 365 Business Standard, Business Premium
• Enterprise: Office 365 E3, E5; Microsoft 365 E3, E5

Note: GCC, GCC High, DoD, and Microsoft 365 operated by 21Vianet are not supported.

Supported environments and versions:

• Devices must run supported versions of Microsoft 365 Apps on Windows 10/11 or supported Windows Server editions.
• Devices must have access to required endpoints (such as *.office.com, *.config.office.com).

Microsoft Entra group requirements:

• Groups can include both user and device objects.
• Devices must be Microsoft Entra joined or hybrid joined.
• Nested groups are supported.
• Groups should contain no more than 20,000 objects.

Update controls available:

• Pause: Temporarily stop update deployments (Monthly Enterprise Channel only).
• Rollback: Revert devices to one of the two previous monthly builds (Monthly Enterprise Channel only).
• Exclusion windows: Prevent updates during critical business periods.
• Exclude groups: Exclude specific devices or users from Cloud Update management.
• Rollout waves: Configure phased deployments across groups.
• Update deadlines: Enforce update installation within a defined time window.

No admin action is required before the rollout, but enabling and configuring Cloud Update is necessary to begin using it.

Enable and configure Cloud Update in the Microsoft 365 Apps admin center to begin using the feature.

Learn more:

• Cloud Update Reaches General Availability: Transforming Microsoft 365 Apps Management | Microsoft Community Hub
• Overview of cloud update in the Microsoft 365 Apps admin center – Microsoft 365 Apps | Microsoft Learn
• Enabling and configuring cloud update – Microsoft 365 Apps | Microsoft Learn

Compliance considerations

Introduction

Viva Engage is introducing a successor to legacy Private Content Mode (PCM) in Yammer: When explicitly enabled, Verified admins and Engage admins will be able to open, view, and take moderation actions on conversations in private communities they are not members of. This capability is intended to support timely moderation and safety response without requiring admins to join each private community. Network admins and corporate communicators are not included in scope. This is a feature available to all Microsoft 365 tenants but requires an explicit, per‑admin opt‑in via a toggle in the Engage Admin Center.

This message is associated with Microsoft 365 Roadmap ID 498493.

When this will happen

General Availability (Worldwide): We will begin rolling out mid-September 2025 and expect to complete by late September 2025.

How this affects your organization

When a Verified admin or Engage admin (Yammer administrator in Entra) turns on the new Private Content Mode toggle in the Engage Admin Center:

• They can view community feed, conversations, post conversations and moderate them for any private community that they are not a member of.
• Moderation actions supported in private communities (without membership) include delete, mute, close, plus other standard conversation actions. Admins may also start new conversations or reply in those communities; such activity appears in their All-activity feed on their storyline.
• Manage certain community settings like managing community experts, the files tab being shown. You can learn more on what they can and cannot do in the Monitor private content in Viva Engage documentation – which will be updated at the time of general availability.
• Private content mode will persist for that particular admin user until it is explicitly disabled in the Engage admin center.  

To enable/disable this mode:

Go to Engage Admin Center > Governance & Compliance > Data Management > and toggle Private Content Mode On or Off.

While enabled, a persistent, non‑dismissible banner appears across the Engage web UX. 

Important limits:

• Private messages can only be viewed via data export or the ediscovery tool going forward.
• Community specific files and events will not be visible in private communities unless the admin is a member; admins also cannot attach media/files when posting in such communities while operating under PCM. Access to SharePoint‑scoped content remains governed by SharePoint/Entra permissions.
• No accidental discovery: Private communities the admin isn’t a member of will not appear in Home feed and digests: content is only reachable via community navigation, or direct links.
• Network Analytics: no change to aggregation. Admins may continue to see aggregate counts, but drill‑down views only include posts from public communities or communities they are a member of.

What you can do to prepare

• Decide who should have access: Limit enablement to Verified admins and/or Engage admins with moderation responsibilities.
• Update policies and training: Clarify appropriate use of this mode (purpose‑bound moderation, least‑privilege, no browsing).
• Plan for audit and oversight: The enablement/disablement of this mode is audit‑logged (who and when). Review your audit pipelines and retention to ensure these events are captured and monitored. 

Compliance considerations

Introduction

We’re introducing support for certified Universal Touch Consoles in Microsoft Teams Rooms on Windows Touchboards. This update enables a center-of-table console experience, bringing the same familiar controls and features available on standard Teams Rooms systems to Touchboard configurations.

When this will happen

General Availability: Rollout begins in late September 2025 and completes by late October 2025.

How this affects your organization

This update enhances the in-room experience for users of Teams Rooms on Windows Touchboards by enabling a center-of-table console interface. It aligns Touchboard setups with standard Teams Rooms systems, improving usability and consistency. The feature is on by default for certified devices and does not require manual configuration.

What you can do to prepare

• If using Teams Rooms on Windows certified Touchboards, Admins should ensure that only certified Universal Touch Consoles are deployed and updated to the latest Teams Rooms on Windows app version once available.
• Review device certification status and update policies to ensure compatibility.
• Learn more: Microsoft Teams Rooms

Compliance considerations

No compliance considerations identified, review as appropriate for your organization.

Introduction

To improve consistency between portal and PowerShell configurations, Microsoft Purview will update how alert generation is handled for Data Loss Prevention (DLP) rules. This change ensures that alert settings in the portal accurately reflect rule configurations made via PowerShell.

When this will happen

This change will begin rolling out on September 26, 2025.

How this affects your organization

We’ve identified that a few tenants have one or more DLP rules with alert generation enabled in the Microsoft Purview portal, but the corresponding alert action was disabled or removed using PowerShell cmdlets.

To align portal behavior with PowerShell configurations, Microsoft will automatically disable the alert generation toggle in the Purview portal for these rules. The rules will remain active and continue to enforce DLP actions, but alerts will no longer be generated unless reconfigured.

This change does not impact the enforcement of DLP policies—only the alert generation behavior.

What you can do to prepare

No admin action is required unless you want to continue receiving alerts for affected rules. To re-enable alert generation:

• Open the rule in the Purview portal, make any update, and save the configuration.
• Use PowerShell to re-enable alert generation for the rule. You can refer to the following cmdlet documentation for guidance:
  • Set-ProtectionAlert
  • Set-DlpComplianceRule

Compliance considerations