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

Introduction

We’re introducing a new feature that enables AI-generated audio briefings for SharePoint news in Viva Connections. This feature provides users with a hands-free way to catch up on top news items using playback controls such as play, pause, skip, and speed adjustment. A Microsoft 365 Copilot license is required to access this summarization capability. This new feature applies to Teams, Surface Devices, and Web. This message is associated with Microsoft 365 Roadmap ID 497142.

When this will happen

Targeted Release (Production tenants): The rollout begins on August 28, 2025, and is expected to complete by September 3, 2025.

General Availability (GCC, GCC High, DoD): The rollout begins on August 28, 2025, and is expected to complete by September 15, 2025.

How this affects your organization

This feature introduces a new way for users to consume SharePoint news through AI-generated audio summaries of the top 10 news items. These clips will play sequentially in the Viva Connections app on Teams desktop and in the browser experience. This hands-free format supports accessibility and productivity for users who prefer audio content.

The feature will be on by default for users with a Microsoft 365 Copilot license.

What you can do to prepare

• Inform your users about this new audio briefing capability in Viva Connections.
• Ensure eligible users have a Microsoft 365 Copilot license.
• Review your SharePoint news publishing practices to optimize content for summarization.
• No admin action is required to enable the feature.

Learn more: The news reader in Viva Connections | Viva Connections | Microsoft Viva | Microsoft Learn

Screenshot 2 – Playback speed controls allow users to adjust the pace of audio briefings to suit their listening preferences:

Compliance considerations

Introduction

To strengthen security across Azure environments, Microsoft is introducing enforcement of multifactor authentication (MFA) for all Azure resource management actions. This change helps protect your organization from unauthorized access and aligns with industry best practices for identity protection.

This effort is part of Microsoft’s commitment to enhance security for all customers and follows Azure’s Phase 1 rollout completed last year. Phase 2 enforcement ensures that all Azure clients – including CLI, PowerShell, SDKs, and REST APIs – are protected against unauthorized access.

When this will happen

Phase 2 enforcement will begin rolling out on October 1, 2025, and will be applied gradually across tenants. Customers may postpone enforcement until July 2026 if additional time is needed to become compliant.

How this will affect your organization

Users will be required to set up MFA before performing Azure resource management actions (via Azure CLI, PowerShell, Mobile App, Identity SDK, IaC tools, or REST APIs).

Enforcement applies to all Azure tenants in the public cloud and all users. This includes automation and scripts using user identities (instead of application IDs). The Phase 2 Azure Portal experience will show when enforcement is active on a tenant.

If your organization cannot meet the enforcement deadline, you can postpone your tenant’s enforcement date.

What you need to do to prepare

• Verify MFA Readiness: Ensure all users performing Azure resource management actions are enrolled in MFA.
• Apply Azure Policy: To understand the potential impact, apply a built-in Azure Policy definition in audit or enforcement mode to assess impact.
• Upgrade Azure CLI or PowerShell Versions: For the best compatibility experience, users in your tenant should use Azure CLI version 2.76 or later and Azure PowerShell version 14.3 or later. 
• Postpone If Needed: Global administrators can self-serve postponement in the Azure Portal before enforcement begins.

This change will happen automatically. No admin action is required unless you need to delay enforcement.

Learn more: 

• How it works: Microsoft Entra multifactor authentication | Microsoft Learn
• How to verify that users are set up for mandatory MFA | Microsoft Learn
• Planning for mandatory multifactor authentication for Azure and other admin portals | Microsoft Learn
• Tutorial: Self-enforce MFA through Azure Policy – Azure Policy | Microsoft Learn

Compliance Considerations

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

• Recall* opens to a personalized homepage that puts your recent activity and top-used apps and websites front and center, making it easy to pick up where you left off. After turning on snapshot collection, the homepage highlights key productivity features like Recent Snapshots, which show the latest snapshots to help you quickly resume tasks, and Top Apps and Websites, which display the three apps and websites you’ve used most in the past 24 hours.
• When you launch Click to Do* for the first time, you’ll see a quick, interactive tutorial. It shows how to complete tasks faster by demonstrating actions on both text and images—such as summarizing large blocks of text or removing image backgrounds.
• When an app requests access to location, camera, microphone, or other device capabilities, Windows shows a redesigned system dialog box. To emphasize the privacy prompt, the screen dims slightly, and the prompt appears at the center of the screen.
• When you use Search from the Windows taskbar, a new grid view will help you more quickly and accurately identify the desired image within your search.
• More widget options and support for lock screen widget personalization (previously referred to as “Weather and more”) are rolling out. 

• Windows 11, version 24H2: KB5064081

• Improved Clarity: Access the most relevant reports without unnecessary clutter.
• Streamlined Usability: Move between sub-reports to monitor agent performance, call volumes, and resolution times.
• Expanded Viewing Area: Maximized available screen space, allowing for a more focused and immersive reporting experience.

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

You are receiving this message because our reporting indicates you may be using new Microsoft Outlook for Windows in your organization.

Coming soon for new Outlook for Windows: an updated People Hub with a modern contact management experience that will retrieve and display high-quality, complete, coherent, and up-to-date information about the people that matter the most to you.

This message is associated with Microsoft 365 Roadmap ID 413114.

[When this will happen:]

Targeted release: We have initiated roll out and we’re currently at 50%. We expect to complete by mid-September 2025 (previously end of August 2025)

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

[How this will affect your organization:]

Before this rollout: The People Hub can contain multiple entries for the same contact and organizational profile information may not be included.

After this rollout: The People Hub will contain a unified view of a person with profile enriched contacts and auto-hidden duplicates. To access the People Hub, select the People icon from the left side of the new Outlook for Windows.

As part of the new contact management experience, your contacts will automatically be enriched with profile information from your organization’s directory and other sources. We have updated the profile card with a new Manage sources feature where a user can manage links to the contact sources:

After a user selects Manage sources, the user can manually Unlink contact sources, Edit contact sources that are not from their organization, and manage sources.

Also, to improve the contact management experience, contacts that are exact duplicates will be automatically hidden.

These changes will be on by default.

[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 want to notify your users about this change and update any relevant documentation.

After the feature is rolled out, please ensure that you are using new Outlook for Windows to get access to the updated People Hub.

Learn more: Add, find, edit, or delete a contact in Outlook – Microsoft Support (will be updated when rollout begins)

#newoutlookforwindows

• AI generative email responses
• AI-generated email and opportunity summaries
• Tracking Outlook activities to CRM
• Creating and editing contacts or other CRM objects

1. Add Files as a knowledge source
2. Add Dataverse as a knowledge source
3. Virtual Agent

1. Sales Copilot
2. Customer Service Copilot
3. Contact Center Copilot
4. Field Service Copilot

1. Copilot Chat
2. Dataverse search

1. In Power Apps / Power Automate
2. In Microsoft Copilot Studio
3. Power Apps / Power Automate – Custom AI Prompts

Introduction

Coming soon to Microsoft Teams Rooms on Android: We are excited to announce that captions will soon support additional languages and translation capabilities. This enhancement aims to improve accessibility and inclusivity of meetings for non-English speaking users using Teams Rooms on Android.  

This message is associated with Microsoft 365 Roadmap ID 499800.

When this will happen

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

How this affects your organization

Before the rollout:

Currently, captions in Teams Rooms on Android only support the English language, which limits usability for non-English speaking users as the captions will result in gibberish if the actual spoken language in the meeting is non-English. There is also no way for admins to set default caption settings.

After the rollout:

• Additional languages: Users can select from a list of supported languages for captions, ensuring that captions are accurate and meaningful for non-English speakers. Users can change the meeting spoken language directly from Teams Rooms devices by selecting More > Captions > Meeting spoken language. 
• Real-time translation: Users can translate the meeting spoken language if the room account has a Teams Rooms Pro license or if the meeting organizer has a Teams Premium license, allowing for real-time translation of captions. Users can translate captions by selecting More > Captions > Translation language. 
• Admin controls: For room accounts with Teams Rooms Pro license, admins will have the option to turn on/off captions by default for calls and meetings as well as turn on/off filtering of any profanity in captions as necessary using the Meetings menu of local device settings. 

Note that you can also control this feature using calling and meeting policies in the Teams admin center.

Learn more: 

• Manage live captions – Microsoft Teams | Microsoft Learn
• Enable call captions – Microsoft Teams | Microsoft Learn

What you can do to prepare

After your Teams Rooms on Android devices are updated to the latest version, configure the desired policy and setting, notify your users about this change, and update your training and documentation as appropriate. This rollout will happen automatically by the specified date with no admin action required before the rollout. 

Introduction

Microsoft Editor browser extensions for Microsoft Edge and Google Chrome—AI-powered writing assistants offering grammar, spelling, and style suggestions—will be retired and no longer supported after October 31, 2025. This change reflects our ongoing efforts to consolidate writing assistance into the built-in proofing experience in Microsoft Edge.

When this will happen

The Microsoft Editor browser extensions will be retired on October 31, 2025. After this date, they will no longer receive updates or support.

Why this change?

Microsoft Editor extensions have helped users write with clarity, correctness, and confidence. As we continue to evolve our AI capabilities, we are consolidating writing assistance into the built-in proofing tools in Microsoft Edge. This approach simplifies the experience and ensures users benefit from the latest AI-powered enhancements without needing separate installations.

What’s next?

The core capabilities of Microsoft Editor—such as grammar checks and spelling corrections—are now part of the standard Edge experience. This transition will offer:

• Smarter, enhanced suggestions for grammar, spelling, and writing style.
• Seamless built-in proofing experience directly in Edge without requiring additional extensions.

How this affects your organization

• Users who rely on the Microsoft Editor extensions will transition to the built-in capabilities in Microsoft Edge.
• No action is required from administrators.
• Users can continue using the extensions until the retirement date and will automatically benefit from the integrated writing assistance in Edge thereafter.

What you can do to prepare

• We recommend informing users of the upcoming retirement and encouraging them to explore the built-in writing assistance in Microsoft Edge.
• Learn more: Microsoft Editor

We appreciate your continued use of Microsoft 365 and look forward to supporting your writing with even more powerful tools.

Compliance considerations

Introduction

We are enhancing the hybrid meeting experience in Microsoft Teams Rooms with the introduction of the Facilitator Agent. When a Facilitator Agent is invited to a scheduled meeting, participants joining from a Teams Rooms device will see a more structured and interactive view on the front-of-room display. This includes the agent’s chat interactions, real-time AI-generated notes, and an agenda timer.

This message is associated with Roadmap ID 499891.

When this will happen

Public Preview (Worldwide): Rollout began late March 2025 and completes by late September 2025.

General Availability (Worldwide): Rollout begins late September 2025 and completes by late October 2025.

Meeting experience:

• In-room participants will have controls on the center-of-room console to toggle the main screen between the AI notes and the meeting chat.
• Users can also view or dismiss the agenda timer.
• This allows for a more focused and productive meeting environment.

What you can do to prepare

No action is needed

Compliance considerations

Updated September 2, 2025: Upcoming SharePoint Online changes may impact your organization. Please review the below.

We are implementing the following changes to custom scripting and classic publishing in SharePoint Online.

1. Disablement of custom scripting

Custom scripting will be disabled by default (setting DenyAddAndCustomizePages to 1 or $true) for sites created with the following templates:

• BLANKINTERNETCONTAINER#0 = Classic Publishing Portal Site
• CMSPUBLISHING#0 = Classic Publishing Site
• BLANKINTERNET#0 = Classic Publishing Site Blank
• CSPCONTAINER#0 = SharePoint Embedded Site

NOTE:

• Existing classic publishing sites created with the templates listed above will have custom scripting disabled by default.
• Disabling custom scripting does not affect the execution of scripts that have already been added to a site or page.

Refer to this documentation to learn more about the security considerations of ungoverned scripting.

2. Ability to set site property bag valued without requiring custom scripting enablement.

Users no longer need to set DenyAddAndCustomizePages to $false or 0 (i.e. enable custom scripting) in a site to manage site property bag values. We have introduced a new AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled setting at the site level and at the tenant level to allow adding/managing site property bag values. Please see documentation here for tenant level setting and here for the site level setting. 

3. Classic publishing sites creation and feature activation changes

Users will no longer be able to create new classic publishing related site collections or activate publishing features in existing site collections. This applies to both UX and API interactions.

Sites collections with the following templates cannot be created:

• BLANKINTERNETCONTAINER#0 = Publishing Portal Site
• CMSPUBLISHING#0 = Publishing Site
• BLANKINTERNET#0 = Publishing Site Blank
• ENTERWIKI#0 = Enterprise Wiki
• SRCHCEN#0 = Enterprise Search Center
• SPSSITES#0 = Site Directory
• SPSNHOME#0 = News Home Site
• PRODUCTCATALOG#0 = Product Catalog
• SPSREPORTCENTER#0 = Report Center
• SPSTOPIC#0 = Topic Area Template

Existing classic publishing enabled site collections are unaffected and can continue regular usage, including creation of sub sites.

[When this will happen]

Both changes, the extended custom scripting governance and the new classic publishing restrictions, will take effect starting September 15, 2025.

[How this will affect your organization]

• When custom scripting is disabled in classic publishing sites, users will no longer be able to use script editor web parts, create custom master pages or page layouts, and utilize several other features. More details on features affected when custom scripting is disabled can be viewed in this documentation.

• With the change to stop the creation of new classic publishing site collections and publishing feature activation, SharePoint admins will no longer be able to create new classic publishing enabled site collections or enable publishing features at site collection level.

[What you need to do to prepare]

We recommend taking the following actions to prepare for these upcoming changes.

1. Inform owners of the classic publishing sites in your organization of these upcoming changes. Promote switching to use of Modern sites. Refer to this guide.

2. To temporarily opt out of the custom scripting enforcement in classic publishing sites for your tenant until March 15, 2026, use the following PowerShell command:

Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites $true

3. To temporarily opt out of custom scripting enforcement for a specific site (with any template) with tenant admin approval (effective for 24 hours), use the following PowerShell command:

Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $false

4. If you need to allow the creation of new classic publishing site collections or enable publishing feature activations, use the following PowerShell command set the flag to allow.

Set-SPOTenant -AllowClassicPublishingSiteCreation $true

NOTE:

• You need to install the latest (16.0.26211.12010 or higher) SharePoint Online Management Shell in order to run the commands above.
• The DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites command is scheduled to end starting on March 15, 2026, while all other commands are expected to remain functional beyond that date. 

[Compliance considerations]

There is no impact or change to compliance.

[Referenced content]

Security considerations of allowing custom script – SharePoint in Microsoft 365 | Microsoft Learn

Allow or prevent custom script – SharePoint in Microsoft 365 | Microsoft Learn

SharePoint modernization guidance | Microsoft Learn

Updated September 2, 2025: We have updated the content. Thank you for your patience.

Introduction

We are reaching out to inform you of an important security and authentication update that may impact your integration with the Microsoft Teams PowerShell Module. As part of our ongoing commitment to strengthening security across Microsoft 365 services, we are updating the authentication requirements for application-based authentication with Administrative Units in the Teams PowerShell Module.

These changes are designed to ensure that Entra applications with Administrative Units used for backend access to Teams PowerShell are properly scoped and secured. If your organization uses Entra applications to automate or manage Teams via PowerShell, action is required to avoid service disruption. 

When will this happen

This change will take effect on Monday, September 15, 2025.

How this affects your organization

If your organization uses Entra applications to authenticate against the Microsoft Teams PowerShell Module, you must update the Application  permissions to avoid disruption.

Specifically:

• RoleManagement.Read.Directory: Required for all Entra applications to verify association with an Administrative Unit.
• GroupMember.Read.All: Required if your application with Administrative Units uses the following cmdlets:
  • *-CsGroupPolicyAssignment
  • *-CsGroupPolicyPackageAssignment

No changes are required for delegated permissions.

What you can do to prepare

To ensure uninterrupted access:

1. Review your Entra applications:

• Go to Microsoft Entra ID > Roles and administrators.
• Check the Teams Administrator roles for any Entra applications or service principals, under the scope of Administrative Units, used with Teams PowerShell.

2. Update API permissions:

• Navigate to Microsoft Entra ID > App registrations.
• • Locate the relevant application under the scope of Administrative Units and add the following permissions:
  
  • GroupMember.Read.All
  • RoleManagement.Read.Directory

3. Test your integrations to confirm continued functionality.

Learn more: Application-based authentication in Teams PowerShell Module.

Compliance considerations

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

Introduction

We’re introducing a new feature that enables AI-generated audio briefings for SharePoint news in Viva Connections. This feature provides users with a hands-free way to catch up on top news items using playback controls such as play, pause, skip, and speed adjustment. A Microsoft 365 Copilot license is required to access this summarization capability. This new feature applies to Teams, Surface Devices, and Web. This message is associated with Microsoft 365 Roadmap ID 497142.

When this will happen

Targeted Release (Production tenants): The rollout begins on August 28, 2025, and is expected to complete by September 3, 2025.

General Availability (GCC, GCC High, DoD): The rollout begins on August 28, 2025, and is expected to complete by September 15, 2025.

How this affects your organization

This feature introduces a new way for users to consume SharePoint news through AI-generated audio summaries of the top 10 news items. These clips will play sequentially in the Viva Connections app on Teams desktop and in the browser experience. This hands-free format supports accessibility and productivity for users who prefer audio content.

The feature will be on by default for users with a Microsoft 365 Copilot license.

What you can do to prepare

• Inform your users about this new audio briefing capability in Viva Connections.
• Ensure eligible users have a Microsoft 365 Copilot license.
• Review your SharePoint news publishing practices to optimize content for summarization.
• No admin action is required to enable the feature.

Learn more: The news reader in Viva Connections | Viva Connections | Microsoft Viva | Microsoft Learn

Screenshot 2 – Playback speed controls allow users to adjust the pace of audio briefings to suit their listening preferences:

Compliance considerations

1. Navigate to Power Platform admin center (new admin center)
2. Go to Manage > Tenant settings
3. Find Name: Hosted browser in computer use
4. Toggle On/Off and Save

• The ability to view Customer Insights – Data profile interactions on the Customer Insights -Journeys interaction timeline.
• The ability to unify customer engagement data from Customer Insights – Journeys and Customer Insights – Data.
• The ability to require CustomerID backstamping.

• Verify that the email address associated with the lead is a valid email address.
• Check if the email address is categorized as a work email or personal email.
• Update the validity and categorization of the email address if the assessment made by the agent is incorrect.

1. Click the presence icon in the navigation bar.
2. In the dropdown, update your presence to your preference.

• Create or update an account
• List all accounts
• Create or update a case
• Create a case note
• List cases
• Draft an email response
• Send an email response

• List leads
• Retrieve lead summary (using Copilot in Dynamics 365 Sales)
• Qualify lead to opportunity
• Get outreach email (using Copilot in Dynamics 365 Sales)
• Send outreach email

• Makers can customize Copilot chat with existing Copilot Studio component collections (Preview) or create their own components to enable custom workflows.
• Field Service work order and scheduling topics are now available as Copilot Studio component collections, allowing makers to enable them for Field Service or custom model-driven applications.

• Windows Backup for Organizations 
• Enabling virtualization-based security (VBS) for hotpatch readiness 
• Integrating Zero Trust with cloud-native Windows 
• Using GPT-5 in Microsoft 365 Copilot or Microsoft Copilot Studio  
• Pull print capability in Universal Print anywhere 
• Additional improvements released in August 

• Windows IT Pro Blog 
• Microsoft Intune Blog 
• Microsoft Security Blog 
• Windows 11 update history 
• Windows Server update history 

Updated September 2, 2025: We have updated the content. Thank you for your patience. 

Coming soon for Microsoft Teams: App centric management for admin app installation introduces new admin settings to control who in the tenant has specific Teams apps preinstalled. Similar to app centric management for app availability, as communicated in MC688930 (Updated) Teams admin center: App centric management and changes to app permission policies (November 2023), admins will be able to install apps for users, groups, or everyone in the organization.

After rollout, app centric management will replace Installed apps in the Teams admin center and give admins the ability to install apps individually. The Installed apps in your app setup policies will be migrated to app centric management based on your current user and group assignments for each policy. The rest of your settings in app setup policies will remain unchanged and will continue to work based on app setup policies, including Pinned apps. After this rollout, you can install Teams apps for selected sets of users, groups, or all users in the organization, and Installed apps in app setup policies will no longer be available.

This message is associated with Microsoft 365 Roadmap ID 394274 and 500637.

[When this will happen:]

App centric management will roll out in four General Availability phases.

• Phase 1 | We will begin rolling this feature for all tenants mid-October and complete rollout by end of October. phase applies to tenants who meet both conditions: 1) tenants with no Installed apps in the Global app setup policy and 2) tenants with no custom app setup policies created in the Teams admin center. After rollout, these tenants will have app centric management enabled for their app installs. Admins may see the Manage apps page in read-only mode for a short time.
• Phase 2 | We will begin rolling this feature for all tenants mid-October and complete rollout by end of October. This phase applies to all remaining tenants. This phase will migrate apps installed for users and groups through Installed apps in app setup policies to app centric management.

[How this will affect your organization:]

Before the rollout: If you install an app to a user, the user cannot actually use an admin preinstalled app if you did not take the additional step to allow the user to use it. After the rollout, if you install an app through app centric management, the user will immediately be able to use the app.

Before the roll out, a user will only have apps installed from a single app setup policy, following the policy resolution precedence rules. After the rollout, if you have multiple custom app setup policies assigned to users or groups, apps from every policy will be installed to the user or group assigned to that policy, regardless of the policy resolution precedence rules.

 [What you need to do to prepare:]

No action needed for Phase 1 tenants. We will update this message with more information before the rollouts for Phases 2 tenants.

You may want to update any relevant documentation as appropriate.

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

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Coming soon for Microsoft Teams: A new Manage what attendees see feature will help organizers and presenters deliver polished town hall events by simplifying the attendee view and keeping the focus on participants brought on screen. The new feature allows assigned organizers and presenters to preview changes before applying them all at once.

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

This message is associated with Microsoft 365 Roadmap ID 487431.

[When this will happen:]

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

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

[How this will affect your organization:]

Before this rollout, when an organizer or presenter brings a participant or shared content on or off screen, the change is immediately reflected in the attendees’ view.

After this rollout, organizers and presenters will have the option to preview their changes before applying them. This allows for smoother, more polished transitions in the attendee’s view, without showing every adjustment made by the organizer or presenter managing the screen. Organizers can go to the town hall Meeting options to locate the Manage what attendees see feature.

We will change the Manage what attendees see option from a toggle to radio buttons. Manage what attendees see will have three options:

• Off: All participants will appear onscreen.
• On: Organizers and presenters can share content and bring attendees on screen to view the content.
• On with preview: Organizers and presenters can share content, preview the content, and then bring attendees on screen to view the content.

To use the new On with preview option, the organizer must select it before the event begins. By default, Manage what attendees see is set to Off when scheduling a meeting or webinar, and On when scheduling a town hall. The On with preview option is only available for town halls and does not require a Teams Premium license.

Limitations

• The On with preview option is not available in meetings or webinars. For these events, the organizer will only have the option to select Off or On for Manage what attendees see.
• Only assigned users joining through Teams for Windows desktop or Teams for the web will have the option to preview and apply changes. Any assigned users joining through mobile or Microsoft Teams Room will not have the ability to bring participants or shared content on or off screen.
• Users joining through older Teams versions will continue to see the existing behavior, where users don’t have the option to preview changes in Manage what attendees see.

Any new meetings or events created after mid-June 2025 will receive the new updates by default to the Manage what attendees see feature.

This feature will be available by default for meeting organizers to configure.

Select the presenter or content you’d like to preview before sending live to your event:

Select Send live to seamlessly send the content from the Preview window to the attendee view:

[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.

We recommend you review Manage what attendees see in Teams meetings (will be updated before rollout) for a comprehensive overview of the feature and conduct a test session with the feature turned on to get acquainted with the new controls.

Updated September 3, 2025:  the rollout has been postponed for GCC, GCCHigh, and DoD environments to a later date. We apologize for any inconvenience.

In Microsoft Purview | Insider Risk Management (IRM), policy tuning analysis provides admins with a real-time prediction of the number of users in a tenant that could potentially match a given set of policy conditions. After this rollout, policy tuning analysis will support insider risk policies that are scoped for priority content.

This message is associated with Microsoft 365 Roadmap ID 378409.

This message is associated with MC786326 (about the preview for this feature that started in May 2024).

[When this will happen:]

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

General Availability (GCC, GCCHigh, DoD): We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

After this rollout, admins can use real-time analytics for policies scoped for priority content to help predict the number of users that could potentially match a given set of policy conditions. This feature enables admins to quickly adjust the selection of indicators and thresholds of activity occurrence so they can efficiently translate their insider risk strategies into pragmatic controls and keep from having too few or too many alerts.

1. In IRM, Navigate to Settings > Insider Risk Management > Analytics, turn on Analytics, and then select Save.

2. Create/edit a policy scoped to all users in the organization.

3. When you get to Content to prioritize in the policy wizard, select the priority content types you want to prioritize:

4. Select the items for each priority content type as applicable.

5. On the scoring page, select Get alerts only for activity that includes priority content:

6. Configure the rest of the policy as applicable and save it.

7. 1-2 days after the policy is saved, edit the policy again and navigate to the indicator thresholds page where insights on user activity containing the scoped priority content for each indicator will be visible under Choose your own thresholds:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date 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.

This change will be available by default for admins to configure. To use this feature, admins will need to enable Analytics in Insider risk management > Settings. After Analytics is enabled and insights are populated, admins will be able to see real-time predictions in policies scoped to all users/groups and scored only for priority content.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

Learn more: Configure policy indicators in insider risk management | Microsoft Learn

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Coming soon for Microsoft Teams: Meeting organizers will be able to send one-way messages to attendees in the meeting lobby using the Lobby chat. The Lobby chat is intended to optimize the lobby experience for all participants, ensuring that organizers are better equipped to run external meetings and external attendees are well informed about the meeting when it begins. This feature is on by default and admins can choose to disable it in the Teams admin center (TAC).

This message applies to Teams on Desktop, Mac, Web

iOS and Android will be released shortly

This message is associated with Microsoft 365 Roadmap ID 480716.

[When this will happen:]

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

General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out late June 2025 and expect to complete by late September 2025.

[How this will affect your organization:]

Admin controls: After this rollout, the policy for Lobby chat will be on by default in the TAC. Admins can enable or disable Lobby chat with a meeting policy in the TAC. Under Meeting policies > Global (Org-wide default) > Meeting engagement, admins will find a new toggle option for Organizers can chat with lobby participant. When the option is enabled, participants who can’t bypass the lobby due to meeting policy will be able to view messages sent by the organizer in a Lobby chat. To enable this policy, Meeting chat in the TAC must be set to On for everyone or On for everyone but anonymous users.

Meeting organizer experience: When someone joins the lobby, the meeting organizer will see a new Lobby tab in their Chat experience. The meeting organizer will be able to send one-way messages to attendees in the lobby in the Lobby tab:

Lobby attendee experience: When the meeting organizer sends a message to the lobby, a new Lobby chat panel will open in the right panel of the pre-join screen and display the message. Lobby attendees cannot reply to these messages: 

[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.

For tenants where Meeting chat in the TAC is set to On for everyone or On for everyone but anonymous users, admins should assess the impact of the Lobby chat feature and update meeting policy settings as needed to suit their organization’s requirements.

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Introducing a new content picker for Teams Mobile Android. Attach any type of content, whether files or media, from the paperclip icon in the compose overflow menu. Our unified attach flow makes it easy and intuitive to attach content from any source location.

This message is associated with Microsoft 365 Roadmap ID 488091.

[When this will happen:]

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

General Availability (GCC, GCC High, DoD) We will begin rollout on Android late June 2025 and expect to complete by late September 2025

[How this will affect your organization:]

Users will see an improved content attach flow in the Teams Android app.

[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.

Updated September 3, 2025: We have updated the content. Thank you for your patience. 

Coming soon for Microsoft Defender for Office 365: We are excited to announce the new CampaignInfo and FileMaliciousContentInfo data tables in Advanced hunting under Email & collaboration schema.

[When this will happen:]

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

General Availability (Worldwide, GCC, GCC High, DoD): General Availability: We will begin rolling out early July 2025 and expect to complete by late November 2025, covering both Advanced Hunting and Sentinel availability.

[How this will affect your organization:]

The new tables will be available by default. SOC teams will be able to see two new data tables in Defender > Advanced hunting > Email & collaboration schema.

1. CampaignInfo

The CampaignInfo table in the Advanced hunting schema contains information about email campaigns identified by Defender for Office 365. The table will have this schema to help the security teams to investigate threats targeting their users and organization:

2. FileMaliciousContentInfo

The FileMaliciousContentInfo table in the Advanced hunting schema contains information about files that were identified as malicious by Defender for Office 365 in Microsoft SharePoint Online, Microsoft OneDrive, and Microsoft Teams. The table will have this schema to help the security teams to investigate threats targeting their users and organization:

Here are a few sample queries to get you started:

//Emails sent as part of phishing campaigns

CampaignInfo

| where Timestamp > ago(7d)

| where CampaignType has "Phish"

| project NetworkMessageId, RecipientEmailAddress, CampaignName, CampaignId, CampaignType

| join (EmailEvents | where Timestamp > ago(7d)) on NetworkMessageId, RecipientEmailAddress

| project Timestamp, NetworkMessageId, Subject, SenderMailFromAddress, RecipientEmailAddress, LatestDeliveryLocation, LatestDeliveryAction, CampaignId, CampaignName, CampaignType

//Files identified as Malware modified in last 1 day

FileMaliciousContentInfo

| where ThreatTypes == "Malware"

| where LastModifiedTime > ago(1d)

[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 your relevant documentation.

After the Public Preview rollout, we will update this post with new documentation.

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing enhanced presenter capabilities for Teams Rooms on Windows in Microsoft Teams Town Halls. When a Teams Room is assigned as a co-organizer or presenter, it can now start or end the event, manage what attendees see, and promote attendees to presenters. This update helps ensure a smoother, more organized event experience—especially in large-scale or hybrid meetings. This feature is available with Teams Rooms Pro.

This message is associated with Microsoft 365 Roadmap ID 490050

[When this will happen:]

General Availability (Worldwide, GCC): We will begin rolling out late June 2025 and expect to complete by early July 2025.

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

General Availability (DoD): We will begin rolling out late July 2025 and expect to complete by late September 2025.

[How this will affect your organization:]

Organizers of Teams Town Halls can now assign a Teams Room on Windows as a co-organizer or presenter, enabling it to manage key aspects of the event. This includes controlling the attendee view, starting or ending the session, and promoting attendees to presenters. These capabilities can help streamline event management and reduce the need for manual intervention by remote producers.

This feature is available only with Teams Rooms Pro and is on by default once deployed.

[What you need to do to prepare:]

• Review your current event workflows and determine if Teams Rooms should be included as co-organizers or presenters in Town Halls.
• Update internal training materials and documentation to reflect the new capabilities.
• Ensure Teams Rooms Pro licensing is in place for rooms you plan to use with this feature.

Learn more:

• Overview of meetings, webinars, and town halls

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Users will now be able to use File Type Filters and People Refiners to apply search criteria to get to relevant files faster.

This message is associated with Microsoft 365 Roadmap ID 481136

[When this will happen:]

General Availability (Worldwide): We will begin rolling out by early September 2025 (previously late August).

[How this will affect your organization:]

Users will now be able to refine their file searches more efficiently within the Files tab of the CIQ menu using two new filters:

• File Type Filters to narrow results by document type
• People Refiners to filter files by collaborators or owners

These enhancements are designed to help users quickly locate relevant files, improving productivity and reducing time spent searching.

[What you can do to prepare:]

No admin action is required. This feature will be enabled by default for all users. You may consider notifying your users about this update to help them take advantage of the new filters.

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Beginning mid-August 2025, we’re introducing a new Tools feature in the Copilot Chat prompt box. Tools acts as a lightweight entry point into high-value, task-specific Copilot features and capabilities directly from the prompt box. By selecting Tools, users get a menu where they can easily discover and trigger the right Copilot feature or capability for their current task, while also providing consistent interactions across tools. Based on the user’s license, Tools provides easy access to features and capabilities like Researcher, Analyst, Pages, and image generation.

This message is associated with Microsoft 365 Roadmap 497298.

When this will happen

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

How this affects your organization

Once this update is rolled out, users will see a new Tools button in the Copilot Chat prompt box. Selecting this button opens a menu of AI-powered features tailored to the user’s license. This enhancement improves discoverability and usability of Copilot capabilities, helping users complete tasks more efficiently.

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

What you can do to prepare

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

• Inform users about the new Tools experience in Copilot Chat.
• Update internal documentation or training materials if needed.

Compliance considerations

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

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing the Regional Settings Separation feature in Microsoft Teams to improve the globalization experience and provide users with greater control over their regional preferences. With this update, users can independently configure UI language, date format, and time format within Teams, either by syncing with their operating system or manually selecting their preferences. This change helps eliminate synchronization issues and ensures a more personalized and consistent experience across devices.

This update is associated with Microsoft 365 Roadmap ID 498895.

When this will happen

• Targeted Release: Begins early August 2025; expected to complete by mid-August 2025.
• General Availability (Worldwide): Begins mid-August 2025; expected to complete by late August 2025.
• General Availability (GCC, GCC High, DoD): Begins mid-August 2025; expected to complete by late September 2025.

How this affects your organization

Once this feature is rolled out, users on Teams Desktop Client for Windows and Mac will be able to view and modify their date and time format settings directly in Teams by navigating to:

Settings > General > Language and regional formats

By default, Teams will continue to follow the operating system settings unless users choose to override them manually. This update does not change existing behavior unless users take action.

What you can do to prepare

No admin action is required. The feature will be available automatically once users update to the supported Teams client build. There are no admin controls or configuration options for this feature.

You may consider notifying your users about this update to help them take advantage of the new customization options.

Compliance considerations

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

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

This feature requires a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 499809.

When this will happen

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

How this affects your organization

This update allows organizations to assign a new policy that enables specific users—such as those in legal or compliance roles—to interact with sensitive content in Copilot Chat. By default, this feature is turned off and will not affect users unless the policy is explicitly assigned.

Admins will see a new policy setting in the Microsoft 365 admin center (shown below), which enables assignment of harmful content access in Copilot Chat.

Admin UX for assigning harmful content access policy in Microsoft 365 Copilot:

For users who are assigned the policy:

• A new option will be available in Copilot Chat that allows them to disable harmful content protection for a specific conversation.
• The default setting is RAI-protected, and users must explicitly turn off protection per conversation.

What you can do to prepare

No action is required unless your organization wants to enable this capability for specific users. Admins can assign the policy to appropriate users based on role requirements. For more information, refer to the Microsoft 365 Copilot documentation (link to be added when available).

Compliance considerations

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

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing a new behavior in Outlook Mobile that improves draft handling. When users close a draft message in progress, it will now automatically minimize instead of closing completely. This allows users to quickly resume editing via a new button in the message list, enhancing productivity and reducing accidental draft loss.

When this will happen

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

How this affects your organization

Once this change is deployed, users will notice that closing a draft message no longer discards it or hides it from view. Instead, the draft will minimize and remain accessible via a button in the message list. This feature is on by default and does not require user or admin configuration.

This change is designed to reduce interruptions and improve the user experience by making draft recovery more intuitive.

What you can do to prepare

No admin action is required.

We recommend the following:

• Inform your users about this change to reduce confusion.
• Update internal documentation or training materials where applicable.

Compliance considerations

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

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Introduction:

We’re enhancing the search experience in Microsoft Teams Desktop to help users quickly find and take action on meetings. With this update, users can search for meetings by name or participant and take key actions directly from the search interface—improving productivity and meeting engagement.

This message is associated with Microsoft 365 Roadmap ID: 498496 

When this will happen:

• Targeted Release: Rolling out early August 2025; expected to complete by mid-August 2025.
• General Availability (Worldwide, GCC, GCC High, DoD): Rolling out mid-August 2025; expected to complete by late September 2025.

How this affects your organization:

This update introduces new capabilities to the Teams Desktop search experience:

• Users can search for meetings using the meeting title or participant names.
• From the search results, users can:
  • Join ongoing meetings
  • View recaps of past meetings
  • RSVP to upcoming meetings
  • Access meeting chats and shared artifacts
• A new “Meeting” pill in the Auto Suggestion canvas allows users to scope searches to meetings only.
• A dedicated “Meetings” tab on the search results page provides a focused view of meeting-related results.

These features are enabled by default and require no admin configuration.

What you can do to prepare:

No admin action is required. The enhanced meeting search experience will be available automatically to all Teams Desktop users. Consider notifying your users about these improvements to help them take full advantage of the new capabilities.

Compliance considerations:

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

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Loop Pages in Teams Channels introduces a flexible, integrated canvas for collaboration directly within Microsoft Teams. Users can create and organize Loop Pages as tabs in a channel, enhancing team workflows and content sharing across desktop and mobile platforms.

This post is associated with Roadmap ID 500634.

When this will happen

• Public Preview: Rolling out September 2025, expected to complete by end of September 2025.
• Targeted Release: Rolling out mid-September 2025 and expected to complete by end of September 2025.
• General Availability (all environments): Rolling out early October 2025 and expected to complete by mid-October 2025.

How this affects your organization

This feature is on by default.

Users will be able to:

• Create, edit, and share Pages as tabs directly in Teams channels
• Receive notifications in the Activity feed when mentioned in a Page
• View Pages on mobile

You may see increased usage of Loop components and may want to review permissions and visibility settings to ensure alignment with organizational policies.

What you can do to prepare

• Review permissions: Pages inherit channel permissions by default but can be shared externally. Ensure Teams policies align with your organization’s data sharing standards.
• Educate users: Provide guidance on how to create, customize, and collaborate on Loop Pages.
• Monitor usage: Consider updating governance policies to reflect increased use of Loop components.

Compliance considerations

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

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.

Updated September 3, 2025: We have updated the timeline and content. Thank you for your patience.

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 mid-September 2025 and expect to complete the rollout by the early November 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 “immediate” Community Announcement feature (where admins can still select the checkbox to send emails immediately —this functionality remains unchanged).

Can I still notify Community users via email immediately (along with other notification channels)? 

Yes! In Viva Engage, we offer an option to send an “immediate” Community Announcement. With this feature, Community admins can choose to send email notifications immediately after posting a Community Announcement, even if a user has opted out of receiving emails. All other notification channels will also send immediately along with email, including Teams and Mobile Push. Therefore, we recommend admins to use this feature when there is a Community Announcement that requires immediate attention from users. 

Community Admins can find this “immediate” Community Announcement option by firstly navigating to the announcement publisher and selecting the hyperlinked “option to send emails immediately” at the bottom of the publisher. Upon clicking this option, an additional pop-up box will open called “Immediate email delivery”. By selecting this checkbox, this will ensure that all three notification channels – Email, Teams, and Mobile Push – will send to customers immediately after a Community Announcement is made. 

 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

• AI generative email responses
• AI-generated email and opportunity summaries
• Tracking Outlook activities to CRM
• Creating and editing contacts or other CRM objects

Updated September 3, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We are enhancing the hybrid meeting experience in Microsoft Teams Rooms with the introduction of the Facilitator Agent. When a Facilitator Agent is invited to a scheduled meeting, participants joining from a Teams Rooms device will see a more structured and interactive view on the front-of-room display. This includes the agent’s chat interactions, real-time AI-generated notes, and an agenda timer.

This message is associated with Roadmap ID 499891.

When this will happen

Public Preview (Worldwide): Rollout began late March 2025 and completes by late September 2025.

General Availability (Worldwide): Rollout begins late October 2025 and completes by late November 2025.

Meeting experience:

• In-room participants will have controls on the center-of-room console to toggle the main screen between the AI notes and the meeting chat.
• Users can also view or dismiss the agenda timer.
• This allows for a more focused and productive meeting environment.

What you can do to prepare

No action is needed

Compliance considerations

Introduction

Starting October 1, 2025, we will retire the Add to existing remediation option under the Propose remediation action in Microsoft Defender for Office 365. This change is being made due to consistently low usage and is intended to streamline the remediation experience.

When this will happen

This change will take effect on October 1, 2025.

How this affects your organization

Our telemetry indicates negligible usage of the Add to existing remediation option. If users in your organization currently rely on this feature, they will need to transition to using the Create new remediation option under Propose remediation. No other functionality is impacted.

What you can do to prepare

No admin action is required. This change will occur automatically. We recommend:

• Informing relevant users about this change.
• Updating internal documentation or training materials that reference the retired option.

Compliance considerations

We’re introducing Benchmarks in the Microsoft Copilot dashboard (in Viva Insights). This new feature enables organizations to compare Copilot usage internally across cohorts and externally against similar companies. These insights help identify adoption trends and opportunities to improve Copilot engagement.

This message is associated with Microsoft 365 Roadmap ID: 495464.

• Targeted Release (Worldwide): We will begin rolling out in late September 2025 and expect to complete by early October 2025.
• General Availability (Worldwide): We will begin rolling out in mid-October 2025 and expect to complete by late October 2025.

Once available, the Copilot dashboard will include:

• External benchmarks to compare your percentage of active Copilot users with:
  • Top 10% and Top 25% of companies like yours
  • Top 10% and Top 25% overall benchmarks
• Internal benchmarks to compare cohorts within your company based on manager types, regions, and job functions:
  • Percentage of active Copilot users
  • Adoption by app
  • Returning user percentage

External benchmarks are calculated using randomized mathematical models to ensure privacy. Each benchmark group includes at least 20 companies and is not derived from any single company’s actual data.

• Review which users have access to the Microsoft Copilot dashboard and adjust permissions as needed.
• Assess the impact of benchmark visibility on your organization’s Copilot adoption strategy.
• Update training materials and documentation to reflect the new dashboard capabilities.
• Learn more about providing access to Microsoft Copilot dashboard: Manage settings for the Microsoft Copilot dashboard and Viva Insights web app – Viva Insights | Microsoft Viva | Microsoft Learn

Planned Maintenance: Viva Engage

To ensure continued reliability and performance, Viva Engage will undergo planned maintenance. During this period, Viva Engage will operate in read-only mode. Users will be able to view posts, messages, storylines, and communities, but will be unable to create posts, reply to conversations, post to their storyline, or make edits. Any attempt to perform these actions will result in error messages.

While the maintenance is timed outside typical business hours to minimize disruption, global users may experience varying levels of impact. We recommend reviewing your schedule in advance, as no workarounds will be available during the maintenance windows. This is the first of three planned maintenance windows.

We have maintenance planned for Viva Engage:

• Maintenance Window: Starting Saturday, September 13th, 2025 at 16:00 UTC. The maintenance window will last approximately 12 hours. This is the first of three planned maintenance windows scheduled:
  • Saturday, September 13th, 2025 at 16:00 UTC
  • Saturday, September 20th, 2025 at 16:00 UTC
  • Saturday, September 27th, 2025 at 16:00 UTC

How this will affect your organization:

During these maintenance windows, Viva Engage will operate in read-only mode. Users will be able to view posts, messages, storylines, and communities, but will be unable to:

• Create new posts
• Reply or react to posts
• Create or edit communities
• Perform any other write-related actions

When users attempt these actions during the maintenance windows, they will see error messages such as:

• “Your message wasn’t posted, please try again soon.”
• “Sorry, something went wrong, please try again soon.”

This maintenance is planned outside of normal business hours to help minimize any impact to your organization.

For organizations with users around the globe, we recognize that “outside of normal business hours” might affect you differently. We apologize for the impact this may have on your users. We are working hard to improve Viva Engage and to minimize these maintenance windows.

What you need to do to prepare:

During these planned maintenance windows, please plan accordingly. No specific workaround is applicable.

We appreciate your understanding and cooperation.

Thank you, The Viva Engage Team

Introduction

Organizations undergoing rebranding, mergers, acquisitions, divestitures, or tenant consolidations often need their SharePoint domain name in URLs to reflect their new identity. The SharePoint Online (SPO) Tenant Rename feature enables this change. We are announcing General Availability (GA) of Advanced Tenant Rename for tenants with up to 500K SharePoint sites, expanding support beyond the previous 100K site limit.

When this will happen

General Availability (Worldwide): We began rolling out in mid-August 2025 and expect to complete by early September 2025.

This feature will be generally available worldwide starting September 1, 2025.

How this affects your organization

This update allows rename support for tenants with up to 500K total SharePoint sites. It maintains high reliability across rename operations and ensures business-as-usual continuity during and after the rename. It is compatible with top Microsoft 365 partner scenarios such as Microsoft Teams and PowerApps.

Key capabilities include:

• Rename support for tenants with up to 500K total sites.
• High reliability maintained across rename operations.
• Business-as-usual (BAU) continuity ensured during and after rename.
• Compatibility with top Microsoft 365 partner scenarios (Teams, PowerApps, etc.).
• Enhanced telemetry to monitor rename operations and identify issues quickly.

Please note the following limitations for this release:

• Tenant rename for vanity domains is not supported.
• Tenant rename for Multi-Geo customers is not supported.
• Tenant rename for customers with more than 500K sites is not supported.

What you can do to prepare

Admins should:

• Confirm their tenant’s total site count using the SharePoint admin center (SPAC) or PowerShell before scheduling.
• Review unsupported features or limitations (such as Hub site limitations, vanity domains, or third-party integrations).
• Communicate any impact to site owners based on public documentation.
• Validate custom scripts, PowerShell automations, and integrations that rely on the old domain name.

Compliance considerations

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

Introduction

Microsoft Edge for Business will soon support Rewrite, a new feature powered by Microsoft 365 Copilot Chat. This capability helps users draft and rephrase editable text directly within Edge, enhancing productivity and writing quality. Users can access Rewrite by highlighting editable text and right-clicking to open the context menu.

This message is associated with Microsoft 365 Roadmap ID 420335.

When this will happen

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

How this affects your organization

• Rewrite will be enabled by default for Edge for Business users. 
• Users can access Rewrite by highlighting editable text and right-clicking to open the context menu.

• If Microsoft 365 Copilot is restricted from accessing page content due to Data Loss Prevention (DLP) policies, Rewrite will not function on that content.
• Admins can manage this feature using the InlineComposeEnabled policy setting.

What you can do to prepare

No admin action is required before rollout.

We recommend:

• Reviewing your current DLP configurations to understand how they may impact Rewrite functionality.
• Notifying users about this new capability.
• Updating internal documentation to reflect this change.

Learn more about how DLP affects Copilot access to page content: Microsoft 365 Copilot Chat in Edge and Access to Page Content | Microsoft Edge | Microsoft Learn

Compliance considerations

Introduction

We’re introducing a Unified Exclusion list in Copilot Analytics (Microsoft Viva Insights), a new feature that provides a single, consistent way to exclude specific users from all Viva Insights. With this update, administrators will have one consolidated exclusion list that applies across the Microsoft Copilot Dashboard (in Viva Insights), Manager and Team insights, Advanced Insights, and the upcoming Microsoft 365 Copilot Chat analytics (available in Copilot Dashboard). Admins can manage exclusions easily through one list, simplifying configuration and safeguarding sensitive user data without impacting other organizational HR data. This ensures consistent privacy controls and data reporting for both licensed and “free” (unlicensed) Copilot users in your organization.

Admins can use CSV upload and Azure Active Directory (Entra ID groups) to manage exclusions in the tenant.

This message is associated with Microsoft 365 Roadmap ID 500161.

When this will happen

General Availability (Worldwide): We will begin rolling out this feature update globally,  starting late-September 2025 and expect rollout to be completed by early-October 2025.

How this affects your organization

All of Viva Insights experiences will now honor the excluded users (available in the Unified Exclusion list), eliminating the inconsistencies between different surfaces. For example, if an employee is on the Unified Exclusion list, that user’s data will be omitted from all Copilot Dashboards, manager insights, and analyst queries uniformly. This replaces the legacy approach where the Microsoft Copilot Dashboard had its own exclusion list and Advanced Insights relied on license or service plan removal. 

The AI administrators, Viva Insights Administrators and Global Administrators will have access to configure this updated setting.

Note: Any users whom you previously excluded (via the old Microsoft Copilot Dashboard exclusion list) will automatically remain excluded under the new mechanism. Those users will continue to be fully excluded from all Viva Insights data, including the new M365 Copilot Chat usage analytics, without any additional action on your part. This ensures continuity of privacy controls for existing tenants. 

Advanced insights will additionally, continue to exclude users for whom Viva insights service plan is not available. 

What you can do to prepare

No immediate action is required to enable this feature. Once the updated Unified Exclusion list becomes available in your tenant, we recommend administrators:

• Navigate to the Microsoft 365 admin center: Setup > Microsoft Viva > Viva Insights > Manage user exclusion lists
• Verify that any users you intend to exclude (from Microsoft Copilot Dashboard (in Viva Insights), Manager and Team insights, Advanced Insights, and the upcoming Microsoft 365 Copilot Chat analytics) are listed. By default, the system will carry over users from your previous Microsoft Copilot Dashboard exclusion configuration that is already available.
• Review and update the exclusion list using CSV upload or Entra ID group membership.
• Notify relevant stakeholders about the new unified exclusion mechanism.

Note: The currently implemented exclusion list under Setup > Microsoft Viva > Viva Insights is accessible to only AI administrators and Global Administrators.

Learn more about Copilot Dashboard licensing requirements: Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Viva Insights | Microsoft Viva | Microsoft Learn

Before the release we will update the documentation about the Unified Exclusion list: https://learn.microsoft.com/viva/insights/advanced/admin/manage-settings-copilot-dashboard

Compliance considerations

Introduction

The migration of Microsoft Whiteboard storage from Azure to OneDrive has begun and will reach all tenants by the end of August 2025. This change enhances data accessibility, security, and compliance by aligning Whiteboard storage with OneDrive’s enterprise-grade capabilities.

This message is associated with Microsoft 365 Roadmap ID 117394.

When this will happen

• General Availability (Worldwide): Began in late February 2024
• Expected completion: Late December 2026
• Full tenant flighting: Expected by end of August 2025
• Azure storage deprecation: February 2026

How this affects your organization

• Any user who launches an eligible Whiteboard client (Windows app, Microsoft Teams desktop/web, or web app) will automatically initiate a non-blocking migration of their Azure-stored whiteboards to OneDrive.
• Once migration is complete, users will see their boards listed under OneDrive. Boards that fail to migrate will appear in a separate Not migrated section in the board picker.
• Following full flighting, we aim to continue supporting the migration experience for an additional six months. After February 2026, Azure-backed whiteboards that have not been migrated will no longer be accessible, as support for Azure board storage will be discontinued.

Users are strongly encouraged to complete their OneDrive migration by February 2026 to retain access to their whiteboards.

What you can do to prepare

Actions for users:

• Open the Whiteboard app to check if migration has started.
• Allow migration to complete and validate board contents.
• If any issues are found, please report them within 90 days of migration completion. After this period, migrated  Azure-stored boards will be permanently deleted.

Action item for Admins:

• Use the latest PowerShell cmdlets to monitor migration status and identify users whose boards remain in Azure.
• Encourage users to open the Whiteboard app to initiate migration.

Refer to:

• Migration of Whiteboards from Azure to OneDrive: for detailed guidance
• WhiteboardAdmin Module: for help with Powershell cmdlets

Compliance considerations

To enhance privacy and improve meeting reliability, we’re updating how live captions and real-time text (RTT) behave in Microsoft Teams meetings. These updates ensure that captions are more secure when transcription is off and improve the stability of caption display across devices and scenarios.

This message is associated with Microsoft 365 Roadmap ID 499616.

• Targeted Release: Began September 1, 2025, completes by September 15, 2025.
• General Availability:
  • Worldwide, GCC, GCC High: September 15–29, 2025
  • DoD: September 25–October 3, 2025

• When transcription is off, captions will now display only the last five minutes of dialogue, enhancing privacy by limiting visible history.
• When transcription is on, captions will show the full meeting conversation from the time transcription starts until the transcription ends.

• A previous issue where repositioning captions could cause text loss has been resolved. Captions will now remain intact when moved.
• These improvements also apply to real-time text (RTT), ensuring a consistent and reliable experience across both features.
• This update applies to Microsoft Teams on desktop and Mac platforms.

• Inform users about the new five-minute limit for captions when transcription is off.
• Update internal training materials and documentation for users who rely on live captions or RTT.
• No admin action is required to enable this feature.

Learn more:

• Use live captions in Microsoft Teams meetings | Microsoft Support
• View live transcription in Microsoft Teams meetings | Microsoft Support

Compliance considerations

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

Introduction

Live captions in Microsoft Teams meetings are now available on mobile devices with enhanced customization options. Users can personalize captions by adjusting font color, background color, and caption height—making captions easier to read and follow, especially in varying lighting conditions or while on the go. This update aligns mobile capabilities with Teams on desktop and web, supporting a consistent experience across platforms.

This message is associated with Microsoft 365 Roadmap ID 499620.

When this will happen

• Targeted Release: We will begin rolling out in early September 2025 and expect to complete by mid-September 2025.
• General Availability (Worldwide, GCC): We will begin rolling out in mid-September 2025 and expect to complete by late September 2025.
• General Availability (GCC High): We will begin rolling out in early October 2025 and expect to complete by mid-October 2025.
• General Availability (DoD): We will begin rolling out in late October 2025 and expect to complete by early November 2025.

How this affects your organization

Teams’ mobile users will be able to customize live captions during meetings. These settings include:

• Font color
• Caption background color
• Caption height

Changes made on mobile will sync across Teams Desktop and Web, ensuring a consistent experience.

These settings are saved locally and persist across sessions, so users do not need to reconfigure them each time they join a meeting. Additionally, caption customization respects mobile OS accessibility preferences such as system font size and contrast settings, helping users maintain a consistent experience across apps.

Caption style settings are only available when captions are turned on during a meeting.

This feature is on by default and requires no admin action. Caption customization is managed at the user level, and existing caption policies will continue to apply across all platforms.

Screenshot 1 – Customized live captions displayed during a Teams meeting on mobile demonstrating enhanced accessibility: 

Screenshot 2 – Live caption customization settings on mobile showing options to adjust font color, background color, and caption height for improved readability: 

What you can do to prepare

No admin preparation is required. We recommend informing your users about the new customization options to help them take advantage of improved accessibility and viewing comfort when joining meetings from mobile devices.

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

• Authenticate with Microsoft or Authenticate Manually – This allows you to force authentication through Microsoft Entra ID or set up manual authentication.
• No authentication allows anonymous access.

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 September 3rd, 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

• A fully interactive process overview dashboard
• Process map component that offers a full range of KPIs to display
• Process Overview page content that is dynamically recalculated based on filters you set
• View the Process Overview analysis without waiting for the Power BI report to generate

Updated March 20, 2025: We have updated the content. Thank you for your patience

Note: Users with EDU licenses assigned will not receive this change. 

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 settings are also updated to reflect this opt-in workflow. There are no changes to the on-demand hiding process.

This feature is enabled for Targeted Release, and we will roll out to General Availability later this year in 2025. 

In the interim, we are disabling the current generally available version of the feature which requires users to opt-out as well as the settings, for all users. Please note that all users in the public or general ring will not see the setting or have any of their channels hidden automatically. We will re-introduce the updated feature later this year in 2025. 

This message is associated with Microsoft 365 Roadmap ID 325780.

[When this will happen:]

Targeted Release: We will begin rolling out mid-July 2024 and expect to complete later in 2025.

General Availability (Worldwide) and all clouds: We will begin rolling out later in 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 in 2025: 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.  

Updated September 4, 2025: After further review, the original deprecation decision and goal remain unchanged. At this time, we are deferring the effective date. We will communicate the timeline when we are ready to proceed and remove these web pages. We apologize for any inconvenience.

ASP.NET DISCO and WSDL pages were the web service APIs for customers who wanted to create a proxy for their web services. The retirement of ASP.NET web services was announced in 2013 and should not be used. We encourage customers to move away from consuming these pages and use Microsoft Graph for remote operations where possible.

Please refer to the following information regarding the DISCO and WSDL endpoints

• These endpoints were originally designed for use with development tools from the early 2000s and were never a preferred or widely adopted method for generating proxy classes in SharePoint development.
•  These endpoints are not tenant-specific and are not associated with any individual tenant’s configuration or ownership.
• Usage across the SharePoint Online service is extremely rare. In fact, most of these endpoints show zero usage.
• These endpoints were primarily used in legacy development scenarios and are not required for modern SharePoint development practices.
• If your organization has an internal development team, we recommend consulting with them to confirm whether these endpoints are in use. However, it is extremely unlikely that they are being used in any current development workflows.

Learn more: Removal of deprecated DISCO & WSDL aspx pages from SharePoint Online – Microsoft 365 Developer Blog

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

We’re making changes to the sender email addresses by which admins receive Teams Data Loss Prevention (DLP) Generate Incident Report (GIR) emails.

[When this will happen:]

This rollout will start on December 30, 2025 (previously August 20) and complete by January 30, 2025 (previously August 30).

[How this will affect your organization:]

You are receiving this message because our reporting indicates one or more users in your organization may be using this GIR email functionality available with Teams DLP.

Currently, Teams DLP GIR emails are sent out via <[email protected]>.Starting June 2nd 2025 (for a period of 2 weeks), you will receive GIR emails from either <[email protected]> or <[email protected]>. After June 20th 2025, all Teams DLP GIR emails will be sent by the <[email protected]> email address.

[What you need to do to prepare:]

You will continue to receive Teams DLP GIR emails, but the sender email address will change. When this change takes effect, you will need to manage the downstream systems that you have configured (if any) by using the previous sender email address.

Learn more: Data loss prevention and Microsoft Teams.

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

Soon, users will be able to summarize PDF, Microsoft Word (.docx), and Microsoft PowerPoint (.pptx) email attachments with Copilot in Outlook. The new feature will be available in Microsoft Outlook for the web, the new Microsoft Outlook for Windows desktop, Microsoft Outlook for Android/iOS, and the new Microsoft Outlook for Mac desktop.

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

This message is associated with Microsoft 365 Roadmap ID 475249.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout, users will be able to pick a classic attachment from the email thread and summarize it with Copilot by selecting Summarize in the attachment’s three-dot context menu or in the attachment’s Preview, or by selecting Summarize a file in the Summary by Copilot card. The Copilot summary will display below the existing email summary inside the Summary by Copilot card:

We do not support encrypted files or files protected by Microsoft Information Protection (MIP).

This feature will be available by default for users with a Copilot license, but this feature will respect the Copilot control toggle setting in Outlook. Users who have turned off this toggle will not see this feature.

[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: Summarize an email thread with Copilot in Outlook – Microsoft Support (will be updated before rollout)

#newoutlookforwindows

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

Coming soon for Microsoft SharePoint: A new web part for FAQs, to help assist content owners keep their content fresh and relevant. Powered by Microsoft 365 Copilot, this new web part can help content owner easily curate FAQ by working with agents and connected grounding data.

Copilot license requirements:

• Reading: All readers can view FAQ web part content without a Copilot license.
• Creating & Editing: A Copilot license is necessary for creating and editing content using Copilot features.

This feature requires a SharePoint license and a Microsoft 365 Copilot license.

This message is associated with Microsoft 365 Roadmap ID 482198.

[When this will happen:]

Public Preview: We will begin rolling out early August 2025 and expect to complete by mid-October 2025 (previously late August).

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

General Availability (Worldwide, GCC): 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, authors can add the web part for FAQs directly to pages or news posts during editing:

By selecting one or more grounding source files, AI will automatically generate FAQ content, reducing the time and effort needed for manual creation of FAQs. The web part currently supports FAQ types such as Event, Product, and Policy, with the option for authors to provide additional descriptions to guide more targeted content generation.

FAQs created using the web part can be indexed for search and shared via email, making it easier to distribute consistent, up-to-date information to your organization.

This change will be available by default.

[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 September 4, 2025: We have updated the timeline. Thank you for your patience.

Based on your feedback, we are excited to announce that Microsoft 365 service health email notifications for Issues in your organization that require action will soon be available by default in your preferred language.

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, service health email notifications for Issues in your organization that require action were only sent in English. With this update, admins will receive alerts in their preferred language, making it easier to understand and act on service health issues that affect your organization. This change improves accessibility and ensures critical service health information is actionable for all admins, regardless of their language preference.

After this rollout, if you’ve already subscribed to service health notification alerts for Issues in your environment that require action, you will start receiving these email notifications in the language set in your Microsoft 365 admin center preferences. We will support these 72 languages for email translation:

1. af-za: Afrikaans (South Africa)
2. am-et: Amharic (Ethiopia)
3. ar-sa: Arabic (Saudi Arabia)
4. as-in: Assamese (India)
5. az-latn-az Azerbaijani (Latin, Azerbaijan)
6. bg-bg: Bulgarian (Bulgaria)
7. bn-in: Bengali (India)
8. bs-latn-ba Bosnian (Latin, Bosnia & Herzegovina)
9. ca-es: Catalan (Spain)
10. ca-es-valencia Valencian (Spain)
11. cs-cz: Czech (Czechia)
12. da-dk: Danish (Denmark)
13. de-de: German (Germany)
14. el-gr: Greek (Greece)
15. es-es: Spanish (Spain)
16. et-ee: Estonian (Estonia)
17. eu-es: Basque (Spain)
18. fa-ir: Persian (Iran)
19. fi-fi: Finnish (Finland)
20. fil-ph: Filipino (Philippines)
21. fr-fr: French (France)
22. ga-ie: Irish (Ireland)
23. gl-es: Galician (Spain)
24. gu-in: Gujarati (India)
25. he-il: Hebrew (Israel)
26. hi-in: Hindi (India)
27. hr-hr: Croatian (Croatia)
28. hu-hu: Hungarian (Hungary)
29. id-id: Indonesian (Indonesia)
30. is-is: Icelandic (Iceland)
31. it-it: Italian (Italy)
32. ja-jp: Japanese (Japan)
33. ka-ge: Georgian (Georgia)
34. kk-kz: Kazakh (Kazakhstan)
35. km-kh: Khmer (Cambodia)
36. kn-in: Kannada (India)
37. ko-kr: Korean (Korea)
38. lo-la: Lao (Laos)
39. lt-lt: Lithuanian (Lithuania)
40. lv-lv: Latvian (Latvia)
41. mi-nz: Maori (New Zealand)
42. mk-mk: Macedonian (North Macedonia)
43. ml-in: Malayalam (India)
44. mr-in: Marathi (India)
45. mt-mt: Maltese (Malta)
46. nb-no: Norwegian Bokmål (Norway)
47. ne-np: Nepali (Nepal)
48. nl-nl: Dutch (Netherlands)
49. or-in: Odia (India)
50. pa-in: Punjabi (India)
51. pl-pl: Polish (Poland)
52. pt-br: Portuguese (Brazil)
53. pt-pt: Portuguese (Portugal)
54. ro-ro: Romanian (Romania)
55. ru-ru: Russian (Russia)
56. sk-sk: Slovak (Slovakia)
57. sl-si: Slovenian (Slovenia)
58. sq-al: Albanian (Albania)
59. sr-cyrl-rs: Serbian (Cyrillic, Serbia)
60. sr-latn-rs: Serbian (Latin, Serbia)
61. sv-se: Swedish (Sweden)
62. ta-in: Tamil (India)
63. te-in: Telugu (India)
64. th-th: Thai (Thailand)
65. tr-tr: Turkish (Türkiye)
66. tt-ru: Tatar (Russia)
67. uk-ua: Ukrainian (Ukraine)
68. ur-pk: Urdu (Pakistan)
69. vi-vn: Vietnamese (Vietnam)
70. zh-cn: Chinese (Simplified, China)
71. zh-tw: Chinese (Traditional, Taiwan

To configure this feature:

• Go to Microsoft 365 admin center > Service Health Dashboard > Customize tab > Email tab to subscribe to Issues in your environment that require action (and Issues with priority accounts notifications, available for certain licenses).
• Keep the Translate emails to <preferred language> checkbox checked to start receiving these notifications in your preferred language. Note: This box will be checked by default.
• You can opt out of translation at any time to go back to receiving emails in English.

How to check Microsoft 365 service health – Microsoft 365 Enterprise | Microsoft Learn (will be updated before rollout)

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

We’re expanding the capabilities of the Researcher Agent by integrating it into Copilot Notebooks. This enhancement allows users to conduct complex, multi-step research across enterprise data sources—without leaving the Notebook experience—using OpenAI’s deep researcher model with chain-of-thought reasoning.

This change is associated with Microsoft 365 Roadmap ID: 493288

[When this will happen:]

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

[How this affects your organization:]

Users who currently have access to the Researcher Agent in Microsoft 365 Copilot Chat will now also be able to use it directly within Copilot Notebooks. This integration enables more seamless, in-context research workflows, especially for tasks that require iterative reasoning and synthesis across multiple data sources.

This feature will be on by default for tenants with access to both Copilot Notebooks and the Researcher Agent.

[What you can do to prepare:]

No specific action is required at this time. This update builds on existing capabilities in Copilot Notebooks and the Researcher Agent. You may wish to inform users who rely on research-intensive workflows so they can take advantage of the enhanced experience.

[Compliance considerations:]

• Alters processing/storage/access of existing customer data? Yes – Researcher Agent may access enterprise data sources for research tasks
• Introduces or modifies AI/ML capabilities that interact with customer data? Yes – Uses OpenAI’s researcher model with chain-of-thought reasoning
• Provides new ways for users to interact with generative AI? Yes – Enables generative research within Notebooks

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

We’re expanding offline capabilities in the new Outlook for Windows. Users will soon be able to create, edit, and delete single calendar events even when not connected to the internet. This enhancement improves productivity and flexibility when working offline.

This change is associated with Microsoft 365 Roadmap ID: 490059

[When this will happen:]

Targeted Release: Rollout will begin in late September 2025 and is expected to complete by late October 2025.

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

[How this will affect your organization:]

Users with offline mode enabled in the new Outlook for Windows will be able to:

• Create new single calendar events while offline.
• Edit or delete existing calendar events that have been previously synchronized within the offline timeframe set in Outlook settings.

Note: Support for recurring (series) events while offline is not currently available.

This functionality is controlled by the existing mailbox policy setting:

OWAMailboxPolicy -OfflineEnabledWin.

If this policy is set to True, offline calendar functionality will be available. If set to False, it will be disabled. This update does not change the default value of the policy.

[What you need to do to prepare:]

Ensure that offline mode is enabled for users who need this functionality. At the user level, this can be verified in the new Outlook under:

Settings > General > Offline

• Enable offline email, calendar, and people

Admins can manage this setting using the Set-OwaMailboxPolicy cmdlet. Learn more here: Set-OwaMailboxPolicy 

For end-user guidance, see: Work offline in Outlook

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Yes – calendar data is now accessible and editable offline

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

We’re enhancing the meeting experience in Copilot Chat. Users will now be able to select both individual meeting instances and entire meeting series from the Calendar Insights Queue (CIQ) to include in their prompts to Copilot Chat. This provides more context and continuity for Copilot responses, improving productivity and relevance.

This message is associated with Microsoft 365 Roadmap ID 481137

[When this will happen:]

General Availability (Worldwide): Rollout has begun and is expected to complete by late September 2025 (previously late July).

[How this affects your organization:]

Users can now insert meeting series—alongside individual meeting instances—into their Copilot Chat prompts. This enhancement enables more comprehensive context for Copilot, especially when referencing recurring discussions or decisions.

This feature is on by default and requires no admin action.

[What you can do to prepare:]

No preparation is required. This is a standard feature rollout.

[Compliance considerations:]

• Alters how existing data is processed/stored/accessed? Yes – Meeting series data is now accessible to Copilot
• Introduces/modifies AI/ML capabilities? Yes – Enhances Copilot’s contextual understanding
• New way of interacting with generative AI? Yes – Users can now reference meeting series in prompts

Updated September 4, 2025: Following further review, this item has been identified as a duplicate of MC1048631. Please refer to that record for additional information. We apologize for any inconvenience.

Users will now be able to use File Type Filters and People Refiners to apply search criteria to get to relevant files faster.

This message is associated with Microsoft 365 Roadmap ID 481136.

[When this will happen:]

General Availability (Worldwide): We will begin rolling out by early September 2025 (previously late August).

[How this will affect your organization:]

Users will now be able to refine their file searches more efficiently within the Files tab of the CIQ menu using two new filters:

• File Type Filters to narrow results by document type
• People Refiners to filter files by collaborators or owners

These enhancements are designed to help users quickly locate relevant files, improving productivity and reducing time spent searching.

[What you can do to prepare:]

No admin action is required. This feature will be enabled by default for all users. You may consider notifying your users about this update to help them take advantage of the new filters.

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

We’re introducing Role-Based Access Control (RBAC) in Microsoft Places to help IT administrators securely delegate management responsibilities to centralized Places administrators or local stakeholders such as building or desk managers. This update enhances operational efficiency and aligns access with real-world roles.

This change is associated with Microsoft 365 Roadmap ID: 488103

[When this will happen:]

General Availability (Worldwide): Rollout is expected to begin and complete in September 2025 (previously August).

[How this will affect your organization:]

With this update, Microsoft Places will support RBAC through Exchange Online and Microsoft Entra. This enables:

• Places administrator role (available in Entra): A centralized IT role responsible for onboarding, enabling/disabling features, and assigning local admin roles.
• Building administrators: Can manage one or more buildings and associated spaces (floors, sections, rooms, desks, workspaces).
• Desk administrators: Can manage desks within specific building sections, including desk modes, metadata, and assignments.

Building and desk administrator roles are managed via the Exchange admin center. This change decentralizes Places management, reduces IT overhead, and ensures only authorized users manage specific resources.

[What you can do to prepare:]

If your organization is using or planning to onboard to Microsoft Places, review the updated documentation (to be published at rollout) and plan for role assignments to support onboarding and daily operations.

[Compliance considerations:]

• Does the change alter how existing customer data is processed, stored, or accessed? Maybe – access to room and desk metadata is delegated, but no change to data storage.

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re streamlining the Know Your Customer (KYC) requirements for acquiring Microsoft telephone numbers in all markets. Teams administrators will need to submit general business information and supporting documents via Teams Admin Center before provisioning new telephone numbers. This is a one-time process that will allow Microsoft to validate businesses and fulfill regulatory requirements, helping protect our phone services from misuse, such as spam calls and voice phishing (vishing).

When this will happen

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

How this will affect your organization

This change updates the existing telephone number provisioning workflow. Teams administrators must now complete a KYC onboarding process in the Teams Admin Center before provisioning new telephone numbers.

• Admins will be required to submit business information and supporting documentation.
• The vetting process typically takes a few hours but may take up to two business days.
• No new telephone numbers can be acquired until the submitted information is validated.
• Existing telephone numbers are not affected.

These requirements apply globally and are consistent across all markets.

What you need to do to prepare

Ensure your Teams administrators are ready to provide the following information via the Teams Admin Center:

• Company name
• Tax ID, DUNS number, or Business Registration Number
• Business address
• A copy of the Business Registration, Registry Extract, or Articles of Incorporation

This process applies to all tenants, including those on free trials. No specific license tier is required to complete the KYC onboarding.

Learn more: Teams Phone Know Your Customer overview – Microsoft Teams | Microsoft Learn  

Compliance considerations

• Does the change store new customer data, if so, where, and is the data cached or permanently stored? – Yes. The KYC onboarding process requires submission of business information and supporting documentation, which will be stored by Microsoft to fulfill regulatory requirements.
• Does the change alter how existing customer data is processed, stored, or accessed? – Maybe. While existing telephone numbers are not affected, the process introduces new data collection and validation workflows that may interact with existing tenant metadata.
• Does the change include an admin control and, can it be controlled through Entra ID group membership? – Yes. The KYC onboarding process is managed through the Teams Admin Center, which supports role-based access control via Entra ID group membership.

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Microsoft Entra is updating how Conditional Access (CA) policies apply to Azure DevOps sign-ins. Azure DevOps will no longer rely on the Azure Resource Manager (ARM) resource during sign-in or token refresh flows. This change ensures that access controls are applied directly to Azure DevOps. Organizations must update their Conditional Access policies to explicitly include Azure DevOps to maintain secure access.

When this will happen

This change will take effect starting September 2, 2025, and will be fully enforced by September 18, 2025 (previously September 4), across all environments.

How does this affect your organization?

If your organization has Conditional Access policies targeting the Windows Azure Service Management API (App ID: 797f4846-ba00-4fd7-ba43-dac1f8f63013), those policies will no longer apply to Azure DevOps sign-ins. This may result in unprotected access unless these policies are updated to include Azure DevOps (App ID: 499b84ac-1321-427f-aa17-267ca6975798).

• Access controls such as MFA or compliant device requirements may not be enforced unless policies are updated.
• If you already have a policy that targets all users and all cloud apps and does not explicitly exclude Azure DevOps, no action is required—Azure DevOps sign-ins will continue to be protected.
• This change does not introduce any new user-facing experience or UI changes.
• Sign-in activity can be monitored using Microsoft Entra ID sign-in logs.
• Licensing requirement: Microsoft Entra ID P1 or P2 is required. There are no functional differences by license type. This is a feature change, not a new feature, so trial or preview options are not applicable.
• Unlicensed users may also be impacted.
• Existing Conditional Access policies will be affected, specifically those targeting the Windows Azure Service Management API.
• A small subset of tenants may see the app name as “Microsoft Visual Studio Team Services” instead of “Azure DevOps”—the App ID remains the same.

 What do you need to do to prepare?

To ensure continued protection of Azure DevOps sign-ins, administrators should:

• Review existing Conditional Access policies – Identify any policies that target the Windows Azure Service Management API.
• Update policies to include Azure DevOps:
  • Go to the Entra admin center.
  • Navigate to Entra ID > Conditional Access > Policies.
  • Select the relevant policy.
  • Under Target resources, choose Select resources and add Azure DevOps (App ID: 499b84ac-1321-427f-aa17-267ca6975798).
  • Save the policy.
• Use Entra ID group membership to scope policies to specific users or groups.
• Monitor sign-in activity using Entra ID sign-in logs.
• Review licensing requirements – Conditional Access requires Microsoft Entra ID P1 or higher. Organizations without the required license may explore trial options.

Learn more:

• Removing Azure Resource Manager reliance on Azure DevOps sign-ins | Azure DevOps Blog
• What is Conditional Access? | Conditional Access | Microsoft Entra ID | Microsoft Learn

Compliance considerations

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

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

Introduction

To improve clarity and alignment with OneDrive branding, we are renaming the background process that powers offline mode in both OneDrive and Lists. This update also includes a refreshed icon to reflect the change.

When this will happen

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

How this affects your organization

The following changes will be introduced in OneDrive sync version 25.145.0727.0001:

• Process name changes:
  • Windows: From Microsoft.SharePoint.exe to OneDrive.Sync.Service.exe
  • Mac: From Microsoft SharePoint to OneDrive Sync Service.app
• Task name changes:
  • Windows: from Microsoft SharePoint to Microsoft OneDrive Sync Service
  • Mac: from Microsoft SharePoint to OneDrive Sync Service
• Icon update:
  • From the SharePoint icon to the OneDrive icon

These changes may impact any custom tooling, scripts, or monitoring systems that reference the previous process or task names, or the icon.

What you can do to prepare

• Review and update any custom tools, scripts, or monitoring systems that reference the old process name or icon.
• Ensure IT support teams are informed to reduce potential confusion or help desk calls.

Compliance considerations

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

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

Introduction

Connectivity changes between cmdlets and other M365 services like SharePoint and Exchange will need a new flag to be specified. Starting August 31, 2025, customers will need to use at least Exchange Online PowerShell v3.9.0 and later, with – EnableSearchOnlySession parameter when running Connect-IPPSSession to run the following eDiscovery cmdlets.  

When this will happen

This change will take effect on September 12, 2025 (previously August 31).

How this affects your organization

To maintain functionality and align with modern authentication standards, customers must use Exchange Online PowerShell v3.9.0 and later and include the EnableSearchOnlySession parameter when running Connect-IPPSSession to execute the following cmdlets:

• New-ComplianceSearchAction
• New-CaseHoldPolicy, Set-CaseHoldPolicy, Remove-CaseHoldPolicy
• New-CaseHoldRule, Set-CaseHoldRule, Remove-CaseHoldRule
• New-ComplianceSecurityFilter, Set-ComplianceSecurityFilter, Get-ComplianceSecurityFilter, Remove-ComplianceSecurityFilter

This change does not impact users accessing eDiscovery through the Purview portal. These cmdlets also remain incompatible with Certificate-Based Authentication (CBA).

You are receiving this message because one or more users in your organization are actively using these eDiscovery features.

What you can do to prepare

• Update scripts and workflows to include the -EnableSearchOnlySession parameter when connecting to Security & Compliance PowerShell.
• Ensure your organization is using Exchange Online PowerShell version 3.9.0 or later.
• For more information, visit: Learn about eDiscovery solutions in Microsoft Purview

Compliance considerations

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

Updated September 4, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing enhancements to the focus area experience in Viva Glint to improve how organizations track and act on employee feedback. With this update, focus areas will now be tied to survey cycles, and goal periods will be retired. This change simplifies reporting and aligns focus areas more closely with survey insights.

This update is associated with Microsoft 365 Roadmap ID 498922.

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

After the update, focus areas will be organized by survey cycle instead of goal periods. Glint users will be able to create and report on focus areas based on survey cycles. Goal periods will be retired. Focus areas not linked to a survey cycle (for example, if the cycle has been deleted) will be labeled No survey cycle and remain accessible in the platform. No focus areas will be deleted as part of this change. This update will be enabled by default. 

• No admin action is required for the transition, but we recommend communicating this change to Glint users in your organization.
• Review and update any internal documentation or training materials that reference goal periods. 

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

Updated September 4, 2025: We have updated the timeline and content. Thank you for your patience.

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 mid-September 2025 and expect to complete the rollout by early November 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 “immediate” Community Announcement feature (where admins can still select the checkbox to send emails immediately —this functionality remains unchanged).

Can I still notify Community users via email immediately (along with other notification channels)? 

Yes! In Viva Engage, we offer an option to send an “immediate” Community Announcement. With this feature, Community admins can choose to send email notifications immediately after posting a Community Announcement, even if a user has opted out of receiving emails. All other notification channels will also send immediately along with email, including Teams and Mobile Push. Therefore, we recommend admins to use this feature when there is a Community Announcement that requires immediate attention from users. 

Community Admins can find this “immediate” Community Announcement option by firstly navigating to the announcement publisher and selecting the hyperlinked “option to send emails immediately” at the bottom of the publisher. Upon clicking this option, an additional pop-up box will open called “Immediate email delivery”. By selecting this checkbox, this will ensure that all three notification channels – Email, Teams, and Mobile Push – will send to customers immediately after a Community Announcement is made. 

 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

Expected with Intune’s September (2509) service release, the Resource explorer pane (Devices > select a platform > select a device > Monitor) will be renamed to Device inventory in the Intune admin center. This change is intended to better reflect the purpose of the pane and align with terminology used in related experiences.

[How this will affect your organization:]

This is a user interface change only; there is no change in functionality and data within the pane remains unchanged. The rename will only be visible to you if you have at least one corporate owned device or a Windows device targeted by a properties catalog policy.

[What you need to do to prepare:]

Update your documentation and inform your IT admins as needed. Otherwise, no action is required.

[Introduction]

To enhance detection capabilities in Insider Risk Management (IRM), we’re adding two new email indicators as triggers for data exfiltration activities. These indicators help identify potential data leaks when users send business-sensitive attachments to personal or public email domains. This update supports stronger data protection and aligns with customer feedback requesting broader coverage of email-based risks.

This message is associated with Microsoft 365 Roadmap ID 496149.

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

• Who is affected: Admins managing Insider Risk Management policies.
• What will happen:
  • Two new email triggers will be available:
    • Sending email with attachments to free public domains.
    • Sending email with attachments to self (personal email).
  • These indicators can be enabled from the IRM settings page.
  • Sequence detections will now include these indicators as exfiltration activities.
  • IRM quick policy templates will be updated:
    • Email exfiltration: These two indicators will be set as default triggers and indicators. Sending email with attachments to external recipients will not be enabled by default.
    • Data leaks: Both indicators will be added to triggers and indicators, with no changes to existing ones.
    • Data theft by users leaving your org: Indicators will be added; existing triggers and indicators remain unchanged.
    • Critical asset protection: Both indicators will be added to triggers and indicators, with no changes to existing ones.
  • Existing policies created from quick templates will not be affected.

• No action is required. The new triggers will automatically become available for configuration in the IRM policy wizard.

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

[Introduction]

A new capability of sharing export download links with external users will be available for Microsoft Purview eDiscovery (Premium) users. This feature enhances collaboration by allowing external legal counsel, auditors, or other stakeholders to securely access eDiscovery export files—without requiring tenant login credentials.

This message is associated with Microsoft 365 Roadmap ID 498160.

[When this will happen:]

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

General Availability (GCC, GCC High, DoD): We will begin rolling out early October 2025 and expect to complete by end of October 2025.

[How this will affect your organization:]

This feature will simplify the process of sharing eDiscovery export files with external parties, reducing manual steps and improving compliance workflows. Organizations can maintain strict control over data access while enabling secure collaboration with external users.

[What you need to do to prepare:]

Admins should review their organization’s policies for sharing sensitive data externally and familiarize themselves with the new export configuration options such as enabling link sharing and configuring link duration. Update internal guidance and training materials to reflect this new capability.

Planned Maintenance: Teams Q&A

To ensure continued reliability and performance, Teams Q&A will undergo planned maintenance. During this period, Teams Q&A will operate in read-only mode. This is the first of three planned maintenance windows.

We have maintenance planned for Teams Q&A:

• Maintenance Window: Starting Saturday, September 13th, 2025 at 16:00 UTC. The maintenance window will last approximately 12 hours. This is the first of three planned maintenance windows scheduled:
  • Saturday, September 13th, 2025 at 16:00 UTC
  • Saturday, September 20th, 2025 at 16:00 UTC
  • Saturday, September 27th, 2025 at 16:00 UTC

How this will affect your organization:

During this maintenance window, Teams Q&A will operate in read-only mode. Users will be able to view Q&A messages, but will be unable to:

• Create meetings, Town halls, or webinars with Q&A added
• Turn Q&A off/on in meeting options
• Edit Q&A engagement settings 
• Reply or react to Q&A messages
• Perform any other write-related actions

When users attempt these actions during the maintenance windows, they will see error messages such as:

• “Your message wasn’t posted, please try again soon.”
• “Sorry, something went wrong, please try again soon.”

This maintenance is planned outside of normal business hours to help minimize any impact to your organization.

For organizations with users around the globe, we recognize that “outside of normal business hours” might affect you differently. We apologize for the impact this may have on your users. We are working hard to improve Teams Q&A and to minimize these maintenance windows.

What you need to do to prepare:

During these planned maintenance windows, please plan accordingly. No specific workaround is applicable.

We appreciate your understanding and cooperation.

Thank you, The Teams Q&A Team

Introduction

We’re improving the alert experience in Microsoft Defender for Office 365 (MDO) to help security teams triage alerts more efficiently. These updates reduce alert fatigue by consolidating related signals into single, richer alerts—without compromising detection fidelity or coverage.

General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins mid-September 2025 and will complete by late November 2025. Updates will be delivered incrementally during this period.

• Fewer near-duplicate alerts: Closely related signals will be grouped, reducing clutter in the alert list.
• Richer alert detail: Alerts will include impacted entities (e.g., users, recipients), key identifiers (e.g., message/network IDs), and timelines. Evidence such as URLs, attachments, and IPs remains accessible.
• Preserved triage workflows: Existing pivots like Open message in Explorer, View timeline, and List impacted entities remain unchanged. Severity and categorization are unaffected.
• Incident correlation: Incidents may contain fewer child alerts but with denser evidence per alert.
• APIs and reporting: No schema changes. You may observe lower raw alert counts with higher per-alert density. Dashboards and automation referencing alert IDs will continue to function.

This feature is on by default and requires no configuration changes.

• Review automation logic: Ensure playbooks and scripts can handle alerts with multiple entities and richer context.
• Review alert metrics: If you track alert counts, consider also measuring how many users or messages are included in each alert, what actions are taken, and how long it takes to respond and resolve (mean time to acknowledge and mean time to resolve).
• Communicate with SecOps teams: Set expectations around reduced alert volume with maintained evidence depth.

No policy or configuration changes are required before rollout.

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

Introduction

AI Workflows in the Workflows app for Microsoft Teams provide users with intelligent automation templates powered by Microsoft 365 Copilot. These workflows are powered by scheduled Copilot prompts through predefined templates for easier setup, helping users automate complex tasks and streamline daily operations. Admins can enable this feature by allowing access to the Workflows app in Teams.

This feature is available only to users with a Microsoft 365 Copilot license.

This message applies to Teams for Web and Mac.

This message is associated with Microsoft 365 Roadmap ID 500379.

When this will happen

Targeted Release: Rolling out late September 2025; expected completion by early October 2025.

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

How this affects your organization

Users with a Microsoft 365 Copilot license and access to the Workflows app in Teams will see new workflow templates powered by scheduled Copilot prompts. These templates simplify setup and enhance productivity through intelligent automation.

Screenshot 1 – Workflow setup experience showing Copilot-powered workflow: 

Screenshot 2 – Examples AI workflow templates on the homepage of the new Workflows app in Teams:

This feature is off by default unless the Workflows app is enabled.

What you can do to prepare

To enable this feature for your users:

1. Familiarize yourself with Copilot scheduled prompts.
2. Enable the Workflows app in Microsoft Teams.

If you prefer to disable this feature, use Cloud Policy to set the “Allow the use of additional optional connected experiences in Office” policy to Disabled. This will also disable scheduled prompts in Microsoft 365 Copilot. For more information, see Admin controls for optional connected experiences. If the Workflows app in Microsoft Teams is available to users, then this will disable AI Workflows powered by Copilot for those users. 

Learn more: 

• Manage scheduled prompts for Microsoft 365 Copilot | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• Overview of optional connected experiences in Office | Microsoft 365 | Microsoft Learn

Compliance considerations

Introduction

We’re introducing support for sharing files protected with Microsoft Purview Information Protection sensitivity labels across Microsoft 365 cloud boundaries. This includes Worldwide, GCC High, and Microsoft 365 operated by 21Vianet. This enhancement enables secure collaboration across previously siloed environments, allowing recipients to view, edit, print, and more, based on the rights assigned by the document owner.

This message is associated with Roadmap ID 495000.

When this will happen

Public Preview (Worldwide): Begins mid-August 2025, completes by late September 2025

General Availability (Worldwide, GCC, GCC High, DoD): Begins late September 2025, completes by late October 2025

How this affects your organization

Organizations that need to collaborate across Microsoft 365 cloud boundaries will now be able to share Purview-encrypted documents securely. Once configured, recipients in other clouds will be able to access content based on the assigned rights. This feature is off by default and requires configuration to enable cross-cloud sharing.

What you can do to prepare

• Review the configuration and deployment guidance.
• Ensure your organization’s compliance and security teams are aware of the new sharing capabilities.
• Plan for any necessary training or documentation updates for users who collaborate across cloud boundaries.

Compliance considerations

Introduction

To simplify the transition experience, starting in October 2025, Microsoft Outlook will automatically set up users’ classic Outlook accounts and settings in the new Outlook for Windows—seamlessly and in the background—if certain conditions are met. This enhancement enables users to work across both Outlook experiences without manual setup or toggling.

Note: This update does not change the previously communicated migration opt-out timelines: January 2026 for EDU and April 2026 for Enterprise.

Note: This update does not force the launch or usage of the new Outlook, nor does it modify any existing classic Outlook settings or defaults.

When this will happen

• Current Channel Production (General Availability): We will begin the roll out in October 2025 and continue to expand it over the next few months.

How this affects your organization

If a user’s primary account in classic Outlook is an Exchange Online account, and the new Outlook toggle is available (not hidden by policy), and the new Outlook is installed on their device, then their accounts and settings will be automatically configured in the new Outlook when they launch classic Outlook. This setup occurs in the background and does not alter existing accounts, settings, or defaults.

Additional details:

• Users will receive an in-app notification in classic Outlook.
• If users have previously signed into new Outlook, their primary account remains unchanged.
• Any new accounts added in classic Outlook will appear as secondary accounts in new Outlook.
• Only accounts from the active profile in use will be set up in new Outlook.
• Shared mailboxes and delegate permissions will be preserved in the new Outlook setup.
• Users who launch the new Outlook directly from their device will be able to get started with the accounts and settings they use in classic Outlook, without any additional effort.
• This feature is on by default and does not require user interaction unless opting out.
• Users can opt out via Classic Outlook > Options > General > New Outlook Settings > Automatically set up my account and settings in new Outlook.

Note: If this policy is configured by the admin, users will not be able to change the opt-out setting in Outlook.

View the list of settings imported from classic Outlook.

Screenshot 1 – Teaching callouts informing users about the new Outlook background set up: 

Screenshot 2 – Teaching callout shown after the new Outlook is successfully set up in the background:

What you can do to prepare

Admins can manage this experience using the following policy:

Policy name: Manage automatic setup of classic Outlook accounts in new Outlook

Registry path: [HKEY_CURRENT_USER\Software\Policies\Microsoft\office\16.0\outlook\preferences]

Key: "NewOutlookAutomaticSetupUserSetting"

Values:

• Not Configured (Default): Users manage the setting themselves (enabled by default).
• Enabled: Enforces automatic setup, and users cannot change the setting.
• Disabled: Prevents automatic setup, and users cannot change the setting.

This setting can also be managed via:

• Cloud Policy in the Microsoft 365 Apps admin center
• Group Policy using the latest ADMX templates
• Microsoft Intune using administrative templates

Learn more: 

• Control the installation and use of new Outlook | Microsoft 365 Apps | Microsoft Learn
• Import settings and install add-ins on new Outlook for Windows | Microsoft Support

Compliance considerations

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

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

Android devices with Microsoft Teams will be commencing auto updates for firmware in order to migrate to Microsoft Intune Android Open Source Project (AOSP) device management.

Unlike other firmware updates, these firmware updates cannot be paused.

[When this will happen:]

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

[How this will affect your organization:]

Devices will receive the firmware auto updates following the phases set in Teams admin center:

• Validation: 0-15 days
• General: 16-45 days (default)
• Final: 45-60 days

[What you need to do to prepare:]

Please verify that all prerequisites for AOSP device management migration are completed for your organization to ensure a smooth process. Your devices may sign out during migration if the prerequisites are not carried out properly.

Please see the blog for further details and the full schedule of auto updates for your devices: Moving Teams Android Devices to AOSP Device Management.

There will be no exceptions to delay the auto updates further.

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

Coming soon: A new integration between Insider Risk Management (IRM) and Data Security Investigation (DSI) in Microsoft Purview. This enhancement allows data security admins to launch a pre-scoped DSI directly from an IRM case, enabling deeper investigation into risky user behavior and better post-incident impact assessment.

DSI is a new AI-powered solution that enables data security teams to identify incident-related data, conduct deep content analysis, and mitigate risk within one unified solution. DSI enables data security admins to efficiently identify incident-relevant content by searching their Microsoft 365 data estate to locate emails, Teams messages, Copilot prompts and responses, and documents. Once the investigation is scoped, DSI’s generative AI capabilities allow admins to gain deeper insights into the impacted data, revealing critical security risks and sensitive information. Investigative capabilities include the ability to categorize evidence, perform vector searches, and examine impacted data for security and sensitive data risks. To mitigate identified risks, DSI facilitates secure collaboration between partner teams. Post-investigation learnings can be used to refine existing policies to strengthen an organization’s security practices.

This message is associated with Microsoft 365 Roadmap ID 486827.

[When this will happen:]

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

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

[How this will affect your organization:]

After this rollout:

• Members of the Insider Risk Management Investigators role group can initiate a DSI directly from an IRM case.
• However, they must also be assigned the Data Security Investigation Investigator role to view the investigation results.
• This streamlines the investigation process by allowing admins to:
  • Go to Purview compliance portal > IRM
  • Go to Cases, and open any case listed
  • Select Case actions
  • Choose Investigate data security with AI from the dropdown menu
  • Name the investigation and select relevant content
  • Launch the investigation with a single click

This change will be available by default.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. DSI will need to be set up for successful investigation in DSI once an investigation is created from an IRM case. Prerequisite steps to configure DSI: Get started with Data Security Investigations (preview) | Microsoft Learn. You may want to notify your admins about this change and update any relevant documentation.

Microsoft Purview Insider Risk Management correlates various signals to identify potential malicious or inadvertent insider risks, such as IP theft, data leakage and security violations. Insider Risk Management enables customers to create policies based on their own internal policies, governance and organizational requirements. Built with privacy by design, users are pseudonymized by default, and role-based access controls and audit logs are in place to help ensure user-level privacy.

You can access the Insider Risk Management solution in the Microsoft Purview compliance portal.

Learn more

• Learn about Data Security Investigations (preview) | Microsoft Learn
• Accelerate data security investigations with AI-powered deep content analysis | Microsoft Community Hub
• Take action on insider risk management cases | Microsoft Learn (will be updated before rollout)
• Create an investigation in Data Security Investigations (preview) | Microsoft Learn (will be updated before rollout)

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

Prompt categories will be available in Microsoft Copilot Dashboard in Microsoft Viva Insights on the web to help you understand key Copilot use cases for your organization. In Microsoft Copilot Chat (work), which is grounded in work data, these prompt categories will include Ask and find, Catch up, Draft and brainstorm, and Other. These metrics will be added to the metrics library in the advanced insights app.

Learn more about Copilot Dashboard licensing requirements in Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

This message is associated with Microsoft 365 Roadmap ID 486698.

Public Preview: We will begin rolling out in early September 2025 (previously mid-September) and will complete by late September 2025

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

[How this will affect your organization:]

Users enabled to view Copilot dashboard will see these updates:

1. Adoption tab: Prompt categories will be available at Viva Insights > Microsoft Copilot Dashboard > Adoption > Adoption by app > Copilot Chat (work) dropdown:

2. Impact tab: Admins can go to Viva Insights > Microsoft Copilot Dashboard > Impact > Copilot chat card > Explore more button to access the prompt categories as metrics in the Copilot impact trend section and the Comparison between groups section:

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

Review and assess the impact for your organization. You might consider reviewing with your works council and updating your training and documentation as appropriate.

Learn more: Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

We’re enhancing the contact experience in Microsoft Outlook Mobile (iOS and Android) by introducing profile-enriched contacts and automatic duplicate contact management. These improvements aim to streamline contact views and provide richer organizational context.

This message is associated with Microsoft 365 Roadmap ID 493753.

This feature has previously been released to the People Hub in new Outlook for Windows. More details in MC927963 (Updated) New Microsoft Outlook for Windows: People Hub improvements (published November 2024, updated April 2025).

[When this will happen:]

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

[How this will affect your organization:]

Before this rollout, Outlook Mobile may have displayed multiple entries for the same contact and lacked organizational profile context.

After this rollout:

• Contacts will be unified into a single enriched view, displaying additional profile information from your organization’s directory (where available).
• Identical duplicate contacts will be automatically hidden.
• These enhancements will be on by default and apply to both iOS and Android versions of Outlook Mobile. No admin controls exist.
• Users can access their contact list by selecting Contacts from the Apps section in the Outlook Mobile app.

[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 internal documentation.

After the feature is rolled out, please ensure that users have updated to the latest version of Outlook for iOS or Outlook for Android.

Learn more: Manage Outlook contacts in your organization – Microsoft Support

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

When users report an email as junk, they’ll now see an option to unsubscribe—if the sender supports it. This helps reduce unwanted messages at the source and keeps users’ blocked sender lists from growing unnecessarily. If unsubscribing isn’t available, users can still block the sender as usual. This update simplifies inbox management and gives users more control over their email experience.

This change is associated with Microsoft 365 Roadmap ID: 495469

[When this will happen:]

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

[How this will affect your organization:]

This update enhances the junk email reporting experience by allowing users to unsubscribe from senders directly when reporting a message as junk (if supported by the sender). This reduces the need to manually manage blocked senders and helps keep inboxes cleaner.

There are no changes to existing junk, phishing, blocking, or unsubscribing rules—this feature simply adds a more efficient action path for users.

The feature will be on by default.

[What you can do to prepare:]

No admin action is required. You may wish to inform your users about this new option to help them take full advantage of the improved junk email handling experience.

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

We’re improving the presentation creation experience in Microsoft 365 Copilot. With this update, Copilot will generate presentations with greater depth in content, narrative flow, structure, and visual design—helping users create more compelling and professional presentations faster. Copilot will create a link to the presentation saved in your OneDrive for you to open and review. This enhancement builds on the existing “Create presentation” feature in Copilot Chat and interacts with Microsoft 365 services such as OneDrive and SharePoint.

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

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

After this rollout, users with Microsoft 365 Copilot will experience improved presentation generation capabilities. Copilot will automatically apply enhancements to content structure, storytelling, and design elements when creating presentations.

This feature will be available by default and requires no configuration.

Known limitations at launch:

• Template selection during presentation creation is not yet supported.
• Users can specify text content, but descriptions of graphical elements are not yet supported.

Example experience

Copilot prompt used to generate a presentation with structured narrative and visual design:

Generated slide screenshot” with enhanced design and content depth:

What you can do to prepare

No admin action is required before the rollout. You may want to:

• Inform your users about the enhanced presentation capabilities.
• Update internal documentation or training materials as needed.

Learn more: Microsoft 365 Copilot overview | Microsoft Learn

Compliance considerations

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

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing new capabilities in Microsoft 365 Copilot in Word that enhance how users interact with Copilot to create and refine content. These updates are designed to streamline document creation and editing through a more conversational and iterative experience.

This message is associated with Roadmap ID 499428

When this will happen

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

How this affects your organization

Users with a Microsoft 365 Copilot license will be able to use Copilot in Word to draft new documents or sections, reorganize content into formats like FAQs, update existing content, or rewrite sections. Users will maintain control on the content as they will be able to review and approve any changes. 

What you can do to prepare

No admin action is required for this rollout. We recommend informing users about the enhanced Copilot experience in Word and encouraging them to explore the new capabilities. Additional resources and documentation will be available closer to rollout. 

Compliance considerations

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

Updated September 5, 2025: Access to emails by typing ‘/’ in the prompt box will only be available when using Copilot Chat in Outlook. This applies to both the full app and side pane experience.

We’re enhancing Copilot Chat for users with a Microsoft 365 Copilot license with new capabilities that make it easier for them to include work content—such as files and emails—in their prompts when using Chat in Web scope. By typing ‘/’ in the prompt box, users can quickly search and reference relevant files or emails, streamlining prompt creation and improving Copilot responses. Additionally, some suggested prompts beneath the input box will now include relevant files or emails to help users get started quickly.

Note: Web scope in Copilot Chat is still grounded only in the web. Users can also choose to include additional content in the prompt for Copilot to reason over, such as with the methods described above. Users must switch to Work scope to have Chat automatically grounded in content from their organization’s graph or their personal graph.

This message is associated with Microsoft 365 Roadmap ID 500377.

When this will happen:

• Files: Currently available (Roadmap ID 497112)
• Emails: Rollout begins mid-September 2025 and completes by late September 2025 (Roadmap ID 500377)

[How this will affect your organization:]

This update improves usability and prompt relevance in Copilot Chat by allowing users to reference files and emails in their prompts (without uploading them manually) or as part of suggested prompts under the input box. Users will only see content they have access to, based on interaction signals (such as accessed, modified, or shared) and properties (such as creation or last update date).

No changes to default settings or user permissions are required.

What you can do to prepare:

No admin action is required. You may want to inform your users of these changes.

Learn more: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot and Copilot Chat

Compliance considerations

Updated September 5, 2025: Access to emails by typing ‘/’ in the prompt box will only be available when using Copilot Chat in Outlook. This applies to both the full app and side pane experience.

We’re enhancing Microsoft 365 Copilot Chat with new capabilities that make it easier for users to include work content—such as files and emails—in their prompts. By typing ‘/’ in the prompt box, users can quickly search and reference relevant files or emails, streamlining prompt creation and improving Copilot responses. Additionally, some suggested prompts beneath the input box will now include relevant files or emails to help users get started quickly.

Note: For users without a Microsoft 365 Copilot license, Copilot Chat is still grounded only in the web. Users can also choose to include additional content in the prompt for Copilot to reason over, such as with the methods described above. Chat is not automatically grounded in the organization’s graph or the user’s personal graph – this is only available for users with a Microsoft 365 Copilot license when using Chat in Work scope.

This message is associated with Microsoft 365 Roadmap ID 500377.

When this will happen:

• Files: Currently available (Roadmap ID 497112)
• Emails: Rollout begins mid-September 2025 and completes by late September 2025 (Roadmap ID 500377).

How this affects your organization:

This update improves usability and prompt relevance in Copilot Chat by allowing users to reference files and emails in their prompts (without uploading them manually) or as part of suggested prompts under the input box. Users will only see content they have access to, based on interaction signals (such as accessed, modified, or shared) and properties (such as creation or last update date).

No changes to default settings or user permissions are required.

What you can do to prepare:

No admin action is required. You may want to inform your users about the new reference capabilities.

Learn more: Using Context IQ to refer to specific files, people, and more in Microsoft 365 Copilot and Copilot Chat

Compliance considerations

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re updating the default behavior of Microsoft Teams Copilot in meetings. Copilot without transcription will become the default mode for newly scheduled Teams meetings where Copilot is allowed. Additionally, conversation history will now persist during meetings, improving multitasking and continuity of insights.

This update is associated with Microsoft 365 Roadmap ID 478611.

When this will happen

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

How this affects your organization

• Copilot without transcription becomes default:
  • Applies to new tenants and new users.
  • Existing users without a set policy will inherit the host configuration and receive this new default.
  • Custom policies will remain unchanged.
  • In Teams meeting policy, the default property value for “Copilot” will change from EnabledWithTranscript to Enabled. This affects how Copilot behaves in newly scheduled meetings unless overridden by custom policy.
  • Starting Copilot during a meeting will no longer automatically start transcription.
  • Transcription must be manually enabled in Meeting Options or during the meeting if users want post-meeting insights or access to Copilot conversation history.
• Conversation history now persists during meetings:
  • Users can switch between meeting features (chat, participant list) without losing Copilot insights.
  • This change applies to all users using Copilot without transcription.

What you can do to prepare

• Review your organization’s Teams meeting policies for dependencies on transcription defaults.
• Update internal documentation and training to reflect the new default behavior and conversation history persistence.
• Communicate to users how to manually enable transcription when needed, especially if they want to retain Copilot insights after the meeting.

Learn more: 

• Manage Microsoft 365 Copilot in Teams meetings and events | Microsoft Teams | Microsoft Learn
• Use Copilot without recording a Teams meeting | Copilot in Teams | Copilot | Microsoft Support

Compliance considerations

Updated September 5, 2025: Gallatin customers are advised to still implement multifactor authentication for user accounts to improve security, but there will not be Microsoft enforcement at this time.

Introduction

To strengthen security across Azure environments, Microsoft is introducing enforcement of multifactor authentication (MFA) for all Azure resource management actions. This change helps protect your organization from unauthorized access and aligns with industry best practices for identity protection.

This effort is part of Microsoft’s commitment to enhance security for all customers and follows Azure’s Phase 1 rollout completed last year. Phase 2 enforcement ensures that all Azure clients – including CLI, PowerShell, SDKs, and REST APIs – are protected against unauthorized access.

When this will happen

Phase 2 enforcement will begin rolling out on October 1, 2025, and will be applied gradually across tenants. Customers may postpone enforcement until July 2026 if additional time is needed to become compliant.

How this will affect your organization

Users will be required to set up MFA before performing Azure resource management actions (via Azure CLI, PowerShell, Mobile App, Identity SDK, IaC tools, or REST APIs).

Enforcement applies to all Azure tenants in the public cloud and all users. This includes automation and scripts using user identities (instead of application IDs). The Phase 2 Azure Portal experience will show when enforcement is active on a tenant.

If your organization cannot meet the enforcement deadline, you can postpone your tenant’s enforcement date.

What you need to do to prepare

• Verify MFA Readiness: Ensure all users performing Azure resource management actions are enrolled in MFA.
• Apply Azure Policy: To understand the potential impact, apply a built-in Azure Policy definition in audit or enforcement mode to assess impact.
• Upgrade Azure CLI or PowerShell Versions: For the best compatibility experience, users in your tenant should use Azure CLI version 2.76 or later and Azure PowerShell version 14.3 or later. 
• Postpone If Needed: Global administrators can self-serve postponement in the Azure Portal before enforcement begins.

This change will happen automatically. No admin action is required unless you need to delay enforcement.

Learn more: 

• How it works: Microsoft Entra multifactor authentication | Microsoft Learn
• How to verify that users are set up for mandatory MFA | Microsoft Learn
• Planning for mandatory multifactor authentication for Azure and other admin portals | Microsoft Learn
• Tutorial: Self-enforce MFA through Azure Policy – Azure Policy | Microsoft Learn

Compliance Considerations

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

Updated September 5, 2025: We have updated the timeline. Thank you for your patience.

Microsoft Purview eDiscovery (Premium) is introducing support for pre-authorized and non pre-authorized export download links, to enhance the reliability and performance of export download.

Introduction

A new capability in Microsoft Purview eDiscovery (Premium) enables organizations to configure export download links as either pre-authorized or non pre-authorized.

• Pre-authorized links offer faster downloads and maintain session continuity for a specified duration configurable by eDiscovery administrators.
• Non pre-authorized links require re-authentication after each connection loss and are needed for restricted environments that allow access only to limited Microsoft 365 IP ranges.

This message is associated with Microsoft 365 Roadmap ID 498160.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-September 2025 and completes by end of September 2025.

General Availability (GCC, GCC High, DoD): Rollout begins early October 2025 and completes by end of October 2025

How this will affect your organization

This update allows organizations to maintain strict control over data access while optimizing download performance based on environment needs.

What you need to do to prepare

Admins should:

• Review organizational policies and familiarize themselves with new export configuration options, including link type selection and duration settings.
• Update internal documentation and training materials to reflect this capability.

[Introduction]

The new Unified Permissions Management feature gives admins a consistent view of all required applications and delegated permissions, along with their associated risk levels. This enables clearer understanding of consents and supports more informed decision-making. From the Permissions tab, admins can now provide consent directly, and once granted by the Global Admin, the AI Admin Role can deploy agents.

This message is associated with Roadmap ID 502617.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: Admins managing agent deployment and consent in Microsoft 365.

What will happen:

• Permissions are now surfaced earlier in the agent lifecycle, rather than being embedded in deployment steps—supporting informed decision-making.
• Admins can manage these permissions directly from the Microsoft Admin Center (MAC), reducing workflow interruptions and improving operational efficiency.
• The AI Admin Role can deploy agents once consent is granted by a Global Admin.
• Each permission will display a risk level to help assess impact.
• Automation scenarios will be available to streamline low-risk agent enablement.

[What you can do to prepare:]

• Provide consent from the Permissions tab: Admins will be able to grant consent directly from the Permissions tab. (ETA: End of September)
• Deploy and consent independently: The AI Admin Role will be able to deploy agents once consent is granted by a Global Admin. (ETA: End of September)
• Review risk levels per permission: Each permission will display a risk level to support informed decision-making. (ETA: October)
• Plan for rule-based automation: Automation scenarios will be available to streamline low-risk agent enablement. (ETA: November)

[Compliance considerations:]

We’re introducing two new Microsoft 365 Copilot skills in the SharePoint Admin Center that improve administrative efficiency and governance:

• Step-by-step task guidance: Copilot now provides clear, sequential instructions to help admins complete common tasks confidently and quickly.
• Multi-variable site search: Copilot enables admins to search for sites using multiple conditions, such as inactivity, external sharing, and size, and suggests recommended actions.

This message is associated with Microsoft 365 Roadmap ID 501427.

When this will happen

General availability (Worldwide): Rollout begins on October 6, 2025, and is expected to complete by October 7, 2025.

How this affects your organization

• Improve admin efficiency: Step-by-step guidance reduces the need for documentation searches or trial-and-error, helping both new and experienced admins complete tasks faster.
• Strengthen governance at scale: Multi-variable site search allows admins to ask complex questions and receive actionable results, making it easier to detect risks and enforce lifecycle policies across large environments.

These features are off by default and require a Microsoft 365 Copilot license to be enabled.

What you can do to prepare

Ensure that your organization has the appropriate Microsoft 365 Copilot for Microsoft 365 licenses to use these features. A Copilot license is required for these features to work. These features will not function without the appropriate licensing.

No additional configuration is required at this time.

Compliance considerations

As part of Microsoft’s ongoing Secure Future Initiative (SFI), starting on or shortly after December 2, 2025, the network service endpoints for Microsoft Intune will also use the Azure Front Door IP addresses. This improvement supports better alignment with modern security practices and over time will make it easier for organizations using multiple Microsoft products to manage and maintain their firewall configurations. As a result, customers may be required to add these network (firewall) configurations in third-party applications to enable proper function of Intune device and app management. This change will affect customers using a firewall allowlist that allows outbound traffic based on IP addresses or Azure service tags.

Do not remove any existing network endpoints required for Microsoft Intune. Additional network endpoints are documented as part of the Azure Front Door and service tags information referenced in the files linked below:

• Public clouds: Download Azure IP Ranges and Service Tags – Public Cloud from Official Microsoft Download Center 
• Government clouds: Download Azure IP Ranges and Service Tags – US Government Cloud from Official Microsoft Download Center 

The additional ranges are those listed in the JSON files linked above and can be found by searching for “AzureFrontDoor.MicrosoftSecurity”.

[How this will affect your organization:]

If you have configured an outbound traffic policy for Intune IP address ranges or Azure service tags for your firewalls, routers, proxy servers, client-based firewalls, VPN or network security groups, you will need to update them to include the new Azure Front Door ranges with the “AzureFrontDoor.MicrosoftSecurity” tag. 

Intune requires internet access for devices under Intune management, whether for mobile device management or mobile application management. If your outbound traffic policy doesn’t include the new Azure Front Door IP address ranges, users may face login issues, devices might lose connectivity with Intune, and access to apps like the Intune Company Portal or those protected by app protection policies could be disrupted.

[What you need to do to prepare:]

Ensure that your firewall rules are updated and added to your firewall’s allowlist with the additional IP addresses documented under Azure Front Door by December 2, 2025. 

Alternatively, you may add the service tag “AzureFrontDoor.MicrosoftSecurity” to your firewall rules to allow outbound traffic on port 443 for the addresses in the tag. 

If you are not the IT admin who can make this change, notify your networking team. If you are responsible for configuring internet traffic, refer to the following documentation for more details:

• Azure Front Door
• Azure service tags
• Intune network endpoints
• US government network endpoints for Intune

If you have a helpdesk, inform them about this upcoming change. If you need additional assistance, contact Microsoft Support and refer to this message center post.