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

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

Coming soon for Microsoft Teams: A new setting that allows users to view incoming calls in a small window in Teams to prevent disruptions. Users will be able to take a call in the small window and continue to see what they were working on before the call.

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

This message is associated with Microsoft 365 Roadmap ID 482747.

[When this will happen:]

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

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

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

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

[How this will affect your organization:]

Before this rollout: Teams users are disrupted by the larger Teams screen when viewing an incoming call.

After this rollout: Teams users can turn on this setting to view calls in a small window. Note that both large and small windows are resizable:

This feature will be on by default.

[What you need to do to prepare:]

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

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

Organizers, co-organizers, and presenters in a Microsoft Teams town hall will soon be able to join and view the event from an attendee’s perspective.

This feature will be available for customers who have access to town hall in Teams for Windows or Mac desktop, Teams for the web, or Teams for iOS/Android.

This message is associated with Microsoft 365 Roadmap ID 484126.

[When this will happen:]

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

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

[How this will affect your organization:]

After joining the town hall green room, event participants will be able to access the attendee view by joining from a different Teams platform. For example, an organizer who joins the green room from Teams for Windows desktop can access the attendee view from either Teams for the web or Teams for iOS/Android. Also, a select set of town hall features (such as Q&A) will be disabled just for the organizer, co-organizer, or presenter in the attendee experience they are monitoring. This feature has no impact to the broader attendee experience or on organizers, co-organizers, and presenters in the green room.

1. Primary use case: An organizer, co-organizer, or presenter has joined the event and opens the event again in another platform to preview as attendee. They will have a new option to Preview event as attendee below the options to Add this device or Transfer to this device. (Mobile and desktop/web screens shown)

2. Secondary use case: Organizer/Co-Organizer/Presenter has not joined the event as their designated role yet but first chooses to join as attendee. On desktop and web, they will see a pre-join screen with a new drop-down menu with the option to Preview as attendee. On mobile, they will have the option to Preview as attendee under the More join options. (Mobile and desktop/web screens shown)

This feature will be available by default for town hall organizers, co-organizers, and presenters to configure.

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

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

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

In Microsoft Teams, users will soon be able to add multiple emoji reactions to a single message. Before this rollout, each user can only add one emoji to each chat or channel post. After this rollout, users can select and add multiple emojis—including custom emojis—to the same message.

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

This message is associated with Microsoft 365 Roadmap ID 491468.

[When this will happen:]

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

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

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

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

[How this will affect your organization:]

After this rollout, a user who adds an emoji to a message will find a new More reactions button where the user can select and add additional emojis:

Reactions are displayed in order of popularity, while ensuring that each user’s own reactions are always visible. To maintain clarity and prevent clutter, emojis are limited to 20 reactions per user per message:

When there are too many reactions to show, users can hover over the number (+6 in this image) to see all reactions:

[What you need to do to prepare:]

This feature will be enabled by default and the rollout will happen automatically by the specified dates with no admin action required before the rollout. We recommend these steps:

• Inform users of the updated behavior to avoid confusion when they notice multiple reactions per message.
• If your organization uses custom emojis, note that custom emojis are supported as part of this feature.
• No changes to current admin settings or messaging policies are required.

Learn more: Send an emoji, GIF, or sticker in Microsoft Teams – Microsoft Support (will be updated before rollout)

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

We’re introducing a new capability in the Teams Admin Center that allows Teams administrators to remotely collect diagnostic logs from users’ Teams clients on Windows and Mac devices. This feature helps streamline troubleshooting by enabling secure, admin-initiated log collection without requiring user action or causing disruption.

This message is associated with Microsoft 365 Roadmap IDs 491439

[When will this happen:]

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

[How this will affect your organization:]

This update introduces a new tool in the Teams Admin Center for tenant administrators. Admins with the following roles will be able to remotely collect Teams client logs:

• Teams Administrator
• Teams Communications Administrator
• Teams Communications Support Engineer

To collect logs, navigate to the Manage users page in the Teams Admin Center, select a user, and choose Request client logs from the Client health tab or the user’s profile card. Admins can then download, view, share, or delete the collected logs as needed.

This process is seamless and does not interrupt the end user’s experience.

[What you need to do to prepare:]

• Review and update internal documentation and training materials for your support teams.
• Ensure that only authorized admin roles have access to this capability.

[Compliance considerations:]

• Does the change store new customer data? Yes (diagnostic logs may contain user-specific data).
• Does the change alter how existing customer data is processed, stored, or accessed? Yes.
• Does the change modify, interrupt, or disable any of the following capabilities (Purview)? Maybe (logs may contain data relevant to DLP or audit scenarios).
• Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)? Maybe (logs may be subject to data subject rights requests).

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

Coming soon to Microsoft Purview | Information Protection: To help improve label usability and configuration, the sensitivity labeling scheme will be simplified to only consist of labels and label groupings.

This move to a dynamic architecture will make it easier to move a child label into label groups, out of label groups, and between label groups without losing referential integrity, allowing customers to better scale and reorganize their labels across their entire data estate.

Tenants in scope for manual migration to the new label scheme will see a message on the Sensitivity labels page in the Purview portal, where the tenant admin can access a simple manual migration wizard to opt in to the migration, which should complete in less than a few minutes or even seconds, depending on the label configuration.

If you do not see this message, your tenant does not meet the criteria for manual migration (your tenant lacks applicable parent labels). This new label scheme will be rolled out to your tenant in the coming months. (and we will send a separate MC post in advance).

This message is associated with Microsoft 365 Roadmap ID 386900.

[When this will happen:]

Public Preview (Worldwide): We will begin rolling out early December 2025 (previously early July) and expect to complete by late December 2025 (previously late August).

General Availability (Worldwide): We will communicate the plan for General Availability in a future post.

[How this will affect your organization:]

During migration, to ensure label scoping integrity, any applicable parent label will be converted to a child label under a new label group, and then both parent and child label will have the same display name as the original parent label. Non-applicable parent labels will automatically be converted to label groups.

A parent label is deemed applicable if it has a different scope from any of its children, has label actions, or is published separately from its children.

The manual migration wizard provides a preview of the migrated scheme so admins can better understand how their sensitivity label scheme will change after the migration.

After migration, admins are free to make changes to their migrated label scheme, including unpublishing applicable parent labels that were converted to children during migration.

Users will not notice any change in how labels are viewed or applied. This change will be on by default.

Example of a migrated label scheme:

[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 tenant’s label scheme to ensure it is up to date. You may want to notify your admins about this change and update any relevant documentation.

Optionally, before you migrate your production tenant, consider migrating a test tenant configured with a label scheme that is representative of your production tenant, to become familiar with the migration process and the modern label scheme.

Learn more: Learn about sensitivity labels | Microsoft Learn

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

[Introduction]

We’re introducing new Viva Engage role management APIs in Microsoft Graph, now available in beta. These APIs allow IT admins to programmatically manage Viva Engage-specific roles—such as Corporate Communicator, Network Administrator, and Verified Administrator, enabling automation, scalability, and integration with existing identity systems.

This message is associated with Microsoft 365 Roadmap ID 497131.

[When this will happen:]

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

[How this will affect your organization:]

These new APIs provide greater flexibility and control for IT admins by enabling:

• Automated role assignments
• Programmatic retrieval of role data
• Streamlined admin workflows across large organizations

This expands on existing Microsoft Graph support for roles like Global Administrator and Yammer Administrator, now including all Viva Engage-specific roles. The update does not change the current UI-based role management experience—it simply adds a new programmatic option for admins and corporate communicators to provision Viva Engage roles.

[What you need to do to prepare:]

No immediate action is required. If your organization is interested in using these APIs, you can:

• Begin testing the beta APIs using either delegated (user-authenticated) or app-only access models
• Ensure the appropriate roles are assigned—Entra admin or Corporate Communicator—as these are required to use the APIs
• Share feedback to help improve the experience ahead of general availability

Learn more:

• Introducing Viva Engage Role Management APIs on Microsoft Graph API | Viva Engage | Viva Engage Blog
• Use the Microsoft Graph API to work with Viva Engage | Microsoft Learn

[Compliance considerations]

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

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

Introduction

We’re retiring the Deploy Shifts to your frontline teams at scale feature in Microsoft Teams Admin Center. Starting September 5, 2025, this functionality will no longer be available. We recommend using the Teams web or desktop app to manage Shifts, where ongoing investments will continue to enhance scheduling capabilities.

When this will happen

The retirement will begin and complete on September 25, 2025 (previously September 5).

How this affects your organization

You’re receiving this message because your organization uses Microsoft Teams. If you do not currently use the Deploy Shifts to your frontline teams at scale feature in Teams Admin Center, no action is required.

After September 5, 2025:

• Admins will no longer be able to deploy Shifts at scale via Teams Admin Center.
• Shifts management will continue to be supported in the Teams web and desktop apps.

What you can do to prepare

No admin action is required. This change will occur automatically on the specified date.

To continue managing Shifts, use the Teams web or desktop app:

• Learn more: Deploy Shifts to your frontline teams at scale

Compliance considerations

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

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

We’re introducing a new capability in Microsoft 365 Copilot for PowerPoint that allows users to reference Excel files when creating a slide. This enhancement helps users seamlessly reuse data from Excel to generate more informative and data-driven presentations.

This message is associated with Microsoft 365 Roadmap IDs 497537, 497538, and 497539.

When this will happen

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

How this will affect your organization

With this update, users can now reference an Excel file when selecting “New Slide with Copilot” from the PowerPoint ribbon or “Add a slide” from the Copilot button above the slide. This enables more efficient content creation by leveraging existing Excel data directly within PowerPoint.

Key details:

• Users can reference one Excel file at a time when creating a slide.
• The Excel file must be stored in OneDrive or SharePoint.
• Recommended file size for optimal performance is 24MB.
• Users can include a topic in their prompt to focus the slide content.
• Copilot can generate slides that include charts or tables based on the Excel data.
• This feature is available on web, Win32, and Mac platforms. There are no browser-specific limitations.

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

What you need to do to prepare

• This feature requires the Microsoft 365 Copilot add-on license. It is not included in standard Microsoft 365 SKUs (e.g., E3/E5).
• Available only to tenants with Microsoft 365 E3/E5 plus the Copilot license.
• There are no admin controls to enable, disable, or scope this feature.
• Users can reference a file by clicking the paperclip icon or typing a backslash to select a file.
• Only one file can be referenced per slide. The file must be an Excel format and stored in OneDrive and SharePoint.

No admin action is required for this feature to become available. We recommend informing your users so they can take advantage of this new capability.

Learn more: Reinvent productivity with Microsoft 365 Copilot

Compliance considerations

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

  Introduction

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

This message is associated with Microsoft 365 Roadmap ID 499615.

When this will happen

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

How this will affect your organization

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

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

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

This feature applies to Microsoft Teams Rooms on:

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

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

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

Users create voice and face profile using their own personal device and provide consent to participate in voice and face recognition.

What you can do to prepare

No action is required until rollout begins. Once available:

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

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

Compliance considerations

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

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

Introduction

We’re introducing a new tenant-level admin control in Microsoft 365 admin center that enables IT admins to manage who can create org-wide sharing links for user-built agents. This feature introduces granular control and governance over who in an organization can create org-wide sharing links for user-built agents in Microsoft Copilot Studio Agent Builder.

This feature is associated with Microsoft 365 Roadmap ID 500376.

When this will happen

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

How this affects your organization

By default, existing behavior remains unchanged. Once available, admins will be able to configure whether all users, no users, or only specific users or groups are permitted to create org-wide sharing links for agents built in Copilot Studio Agent Builder. This control helps organizations align agent sharing permissions with internal governance policies and collaboration needs.

What you can do to prepare

Admins can access the new control by navigating to:

Microsoft 365 admin center > Copilot > Settings > Data access > Agents

No action is required unless you want to customize sharing permissions. We recommend reviewing your organization’s sharing policies and updating settings as needed.

Learn more: Manage agents for Microsoft 365 Copilot in the Microsoft 365 admin center | Microsoft 365 | Microsoft Learn

Compliance considerations

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

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

On September 22, 2025, Apple will release new Terms and Conditions for Apple Business Manager. An IT admin will need to accept these terms when using Apple School Manager, Apple Business Manager, Apple Volume Purchasing Program, or Automated Device Enrollment to ensure that the managed devices can continue communicating with Microsoft Intune. 

[How this will affect your organization:]

This will only affect you if you use Apple Automated Device Enrollment, Apple School Manager, Apple Business Manager, or Apple Volume Purchase Program. You will need to accept the new terms and conditions to ensure your Intune service is not interrupted. If you do not accept the new terms and conditions the Intune service will receive the error – “T_C_NOT_Signed” from Apple.

[What you need to do to prepare:]

Simply login to the appropriate URL listed in the support article from Apple here: https://support.apple.com/102069. Once you have logged in and accepted the new terms and conditions, managed Apple devices will once again be able to communicate with Apple’s device management servers.

[Introduction]

Upcoming privacy-related changes in Chromium-based browsers (Google Chrome and Microsoft Edge) will increase restrictions on local network access. When enforcement begins, users accessing OneDrive for Web (and some integrated Microsoft 365 experiences such as Microsoft Lists and SharePoint Document Libraries) will encounter a browser permission prompt for local network access unless the required policy is in place. If the permission is not allowed, performance optimizations and offline capabilities powered by OneDrive and Share Point will not be available. This communication provides required administrator actions to prevent loss of functionality.

[When this will happen:]

Chrome and Edge will roll out this privacy related change as part of Chromium 141 at the end of September.

[How this will affect your organization:]

• Who is affected:
  • All users accessing OneDrive for Web, Microsoft Lists, and SharePoint Document Libraries via Chrome or Edge browsers.
  • Admins managing browser policies for Windows, macOS, and VDI environments.
• What will happen:

  If no action is taken:

  • Users will see a new browser prompt requesting permission for local network access when opening OneDrive for Web and Lists.
  • If users do not click Allow, the following results occur on that device:
    • Performance acceleration will not be available (loss of faster data access behavior).
    • Offline functionality in OneDrive Web will not be available.
  • The experience will be slower and less resilient, and helpdesk contacts will increase due to unexpected prompts and missing offline capability.

  When the recommended browser policy is deployed in advance, the prompt is suppressed for the specified trusted Microsoft 365 endpoints and existing performance, and offline behavior are preserved. The policy prevents loss of existing capability and avoids user confusion.

  [What you need to do to prepare:]

  1. Identify Required Domains
     1. Include your organization’s SharePoint Online and OneDrive endpoints, for example: https://YOURTENANT-my.sharepoint.com or https://YOURTENANT.sharepoint.com
     2. Add additional sanctioned SharePoint Online host variations if applicable (e.g., specialized cloud environments). Avoid overly broad wildcards—conform to internal security governance.
  2. Configure Browser Policy
     1. Set the Chromium policy LocalNetworkAccessAllowedForUrls (Chrome Enterprise / Edge policy) to pre-authorize the listed domains.
     2. Apply via: ADMX / JSON for Windows; plist or configuration profile for macOS (Chrome and Edge).
     3. Roll out to all managed device groups (Windows, macOS, VDI as applicable).
     4. Even if the following policies are currently enabled by policy, deploy the allow-list to prevent future prompts and avoid user confusion.
        1. DisableNucleusSync
        2. DisableOfflineMode
  3. Remediation for Users Who Already Clicked Block
     1. Deploying the managed LocalNetworkAccessAllowedForUrls policy will override any prior per-user deny state and enforce the allow setting once the policy is applied to the device/profile; no end-user action is required after policy propagation.
     2. If you need immediate remediation before policy reaches the device, have the user open the affected OneDrive site, use the site (lock) icon, reset or change the local/network device access permission to Allow, then refresh.

[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. Since Basic Mobility and Security for Microsoft 365 uses Intune infrastructure, customers may need to add Azure Front Door IP addresses, if 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 Basic Mobility and Security for Microsoft 365. 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 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. 

[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

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.

To support increased usage and productivity with Copilot, we’re significantly expanding the monthly transcription quota for users with a valid Copilot license. Starting September 2025, the quota will increase from 300 minutes to 30,000 minutes per user per month. This change applies to transcription services in Word for Microsoft 365, Word for the Web, and OneNote for Microsoft 365.

General Availability: We will begin rolling out mid-September 2025 and expect to complete by late September 2025. For MEC (Monthly Enterprise Channel) win32 expect a rollout of mid-December 2025.

Who is affected:

• Users with a valid Copilot license using transcription in Word for Microsoft 365, Word for the Web, or OneNote for Microsoft 365.

What will happen:

• Transcription quota will automatically increase to 30,000 minutes per user per month.
• No configuration changes are required.
• The quota is non-transferable and non-shareable across users or tenants.
• Applies only to individual users with an active Copilot license.

• No admin action is required.
• Notify eligible users about the increased quota.
• Update internal documentation where transcription quotas are referenced.
• Update helpdesk scripts or FAQs to reflect this change.

Introduction

We’re introducing a new AI audio briefing feature in Viva Connections for Teams mobile (iOS and Android). This feature provides users with a quick, AI-generated summary of top news items in their news feed, with playback controls such as play, pause, and speed adjustment. A Microsoft 365 Copilot license is required to access this feature.

This message is associated with Microsoft 365 Roadmap ID 498233.

When this will happen

General Availability: We will begin rolling out mid-September 2025 and complete by end-November 2025.

How this affects your organization

Users with the Microsoft 365 Copilot license will be able to access the AI generated briefings in their Viva Connections news feed.

This feature is on by default and requires no configuration.

What you can do to prepare

• No action is required. The rollout will be automatic.
• You may wish to inform licensed users about the new feature and its capabilities.

Compliance considerations

Introduction

We’re introducing a new capability in Copilot in Word that allows users to view key document statistics directly within the Dynamic Document Snapshot. This enhancement helps users quickly understand document activity and ownership, improving transparency and collaboration.

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

Users will be able to access important document metadata—such as author, last modified date, and number of times opened—by selecting the Activity tab in the Copilot Dynamic Document Snapshot. This feature is designed to improve document awareness and collaboration by making insights easily accessible.
This feature will be on by default and requires no admin configuration.

What you can do to prepare:

No action is required. This update will roll out automatically as part of Copilot in Word.

Compliance considerations

Introduction

We’re introducing new multitasking enhancements in Microsoft Fabric to help users work more efficiently across complex workflows. These updates improve navigation, context awareness, and workspace management—making the experience smoother, faster, and more intuitive.

When this will happen

• Public Preview (Worldwide): Rollout begins early September 2025 and is expected to complete by mid-September 2025.

How this affects your organization

• Horizontal tabs for open items: Users can easily switch between notebooks, pipelines, reports, and more, with clear labels showing name, type, and workspace indicators.
• Support for multiple open workspaces: Users can open and work across multiple workspaces side-by-side. Color coding and numeric labels help distinguish items by workspace, reducing confusion.
• Object Explorer: A structured view that allows users to browse and open items across all currently open workspaces without switching pages.
• Raised open item limit: The previous 10-item cap has been increased, allowing users to keep more tabs open and active for uninterrupted multitasking.

These changes apply only to the Fabric experience and do not affect Power BI.

What you can do to prepare

No action is required at this time. This message is for awareness only.

Compliance considerations

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

Introduction

To maintain uninterrupted access to Microsoft Whiteboard, organizations using explicit domain whitelisting must update their firewall configurations. This change supports backend service operations as part of Microsoft’s One Consolidated Domain Initiative (OCDI).

When this will happen

This change is effective immediately. We recommend updating your firewall rules as soon as possible to avoid service disruptions.

How this affects your organization

Microsoft Whiteboard has transitioned to the cloud.microsoft domain under OCDI. While many tenants have already whitelisted *.cloud.microsoft, some organizations using explicit domain whitelisting have only added whiteboard.cloud.microsoft.

To ensure full functionality, including backend service operations, the following domain must also be whitelisted:

• whiteboard.svc.cloud.microsoft

Failure to include this domain may result in issues with Whiteboard loading or sharing features. This has been confirmed in multiple support cases where backend calls were blocked by firewall rules.

What you can do to prepare

If your organization uses explicit domain whitelisting, please ensure the following domains are allowed:

• whiteboard.cloud.microsoft
• whiteboard.svc.cloud.microsoft

Learn more: 

• Microsoft 365 URLs and IP address ranges | Microsoft 365 for enterprise | Microsoft Learn
  
• MC1084637 – Product transitions to the cloud.microsoft domain
  

No action is required for tenants who have already whitelisted *.cloud.microsoft.

Compliance Considerations

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

Introduction

As previously announced in MC1087098 (June 2025), Microsoft is retiring the Semi-Annual Enterprise Channel Preview for Microsoft 365 Apps. This change supports our ongoing efforts to simplify update management and ensure customers benefit from the latest features and security improvements more quickly.

The Semi-Annual Enterprise Channel Preview reached end of service on September 9, 2025. The August 2025 security update is the final update available for this channel.

• Who is affected: Admins managing Windows desktop apps that with devices currently configured to use the Semi-Annual Enterprise Channel Preview.
• What will happen:
  • Devices using this update channel will no longer receive updates for Microsoft 365 Apps after September 9, 2025.
  • Microsoft recommends transitioning interactive devices to Monthly Enterprise Channel or Current Channel.
  • Non-interactive devices can use Monthly Enterprise Channel as a release candidate to preview changes coming to Semi-Annual Enterprise Channel.
  • No changes will be made automatically; admin action is required to move devices to a supported updated channel.

• Review your update channel configurations and transition devices to a supported channel.
  • Change update channel to prepare devices for Copilot
• For non-interactive devices that require Semi-Annual Enterprise Channel, consider using Monthly Enterprise Channel as a release candidate.
  • Using Monthly Enterprise Channel as the release candidate
• Communicate this change to your helpdesk and update internal documentation as needed.
• Ensure all devices are updated to the latest version of Microsoft 365 Apps.
  • Overview of update channels for Microsoft 365 Apps
    
  • Update history for Microsoft 365 Apps (listed by date)

Compliance considerations:

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

[Introduction:]

To streamline policy management and improve consistency across Excel-related admin controls, we’re moving the management of Office Scripts settings from the Microsoft 365 admin center to the Microsoft 365 Cloud Policy service. This change aligns Office Scripts with other Excel policies and simplifies administration.

[When this will happen:]

Rollout begins on October 27, 2025.

[How this affects your organization:]

Who is affected:
Admins managing Microsoft 365 Apps settings for Excel.

What will happen:

• The following three Office Scripts settings will be managed in the Cloud Policy service instead of the Microsoft 365 admin center:
• Let users automate their tasks in Excel
• Let users with access to Office Scripts share their scripts with others in the organization
• Let users with access to Office Scripts run their scripts with Power Automate
• These settings will retain their current names in the Cloud Policy service.
• After October 27, 2025:
  • Admins will no longer be able to modify these settings in the Microsoft 365 admin center.
  • Only settings configured in the Cloud Policy service will be honored.
  • If no action is taken, all three settings will default to enabled.

[What you can do to prepare:]

• Review your current Office Scripts settings in the Microsoft 365 admin center.
• Reconfigure the equivalent settings in the Microsoft 365 Cloud Policy service.
• If no changes were made from the default (enabled), no action is required.
• For guidance, see: Overview of Cloud Policy service for Microsoft 365

[Compliance considerations:]

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

[Introduction]

To help users stay protected from malicious content, we’re introducing message warnings in Microsoft Teams. This new feature displays a warning banner on messages containing URLs flagged as Spam, Phish, or Malware—whether the message is internal or external. These warnings enhance user awareness and complement existing security protections like Safe Links and ZAP.

This post is associated with Roadmap ID 502879.

This message center post was created in collaboration with Microsoft Teams and is related to the Teams post MC1148539.

Figure i. Recipient View: Users will find a warning banner on messages containing malicious URLs.

Figure ii. Sender View: Senders will also be notified if their message includes a flagged URL.

[When this will happen:]

• Public Preview (Worldwide): Begins early September 2025 and completes by mid-September 2025.
• General Availability (Worldwide): Begins early November 2025 and completes by mid-November 2025.

[How this affects your organization:]

• Who is affected: All Microsoft Defender for Office 365 (MDO) customers and Microsoft Teams enterprise customers.
• What will happen:
  • Message warnings will appear in two scenarios:
    • Known Malicious URLs: If a URL is already identified as malicious, the message will be delivered with a warning.
    • Post-Delivery URLs: If a URL becomes malicious after delivery, a warning will be added retroactively for up to 48 hours.
  • Recipient View: Users will see a warning banner on messages containing malicious URLs.
  • Sender View: Senders will also be notified if their message includes a flagged URL.
  • The feature will be enabled by default at General Availability.
  • Admins can manage the feature via Teams Admin Center > Messaging settings.
  • If at least one tenant has the feature enabled, message warnings will be active across the tenant.
  • Message warnings work alongside existing protections:
    • Safe Links: Continues to provide time-of-click protection in Teams.
    • ZAP message blocking: If ZAP is enabled, ZAP blocks take precedence over message warnings.

[What you can do to prepare:]

• Review and configure settings in Teams Admin Center > Messaging settings.
• Communicate this change to helpdesk and support teams.
• Update internal documentation to reflect new message warning behavior.
• For Public Preview, opt-in via the toggle in Teams Admin Center > Messaging settings.
• Learn more:
  • Malicious URL Protection in Microsoft Teams
  • Microsoft Defender for Office 365 support for Microsoft Teams

[Compliance considerations:]

[Introduction]

As announced in MC1096218, we are making Copilot Chat available as a side-by-side experience in Word, Excel, PowerPoint, Outlook, and OneNote to help users access AI in their flow of work. Users can open Copilot Chat from the app ribbon. Copilot Chat in the apps will respect the most recent user state (open or closed) when opening a file. During this transition, some previous Copilot Chat features available to licensed Microsoft 365 Copilot users in Word and PowerPoint will be improved, retired, or temporarily unavailable as we create a more unified Copilot Chat experience.

[When this will happen:]

• See MC1096218 for the latest on rollout of the new Copilot Chat experience.
• Feature availability in the new Copilot Chat experience in Word and PowerPoint varies by platform and capability. See the feature breakdown below.

[How this will affect your organization:]

Word features:

PowerPoint features:

Chat history transition

The new Copilot Chat experience in apps introduces shared memory and unified chat history across Microsoft 365 apps and the Microsoft 365 Copilot app, creating a more consistent experience. With this update, previous in-app chat history will not be accessible in the new experience.

• What’s changing: Chat history from the previous in-app chat experience in Word and PowerPoint will no longer be accessible.
• Why: The experience improvements are built on a new system and chat history will start fresh.
• Admin action: If needed, tenant admins may request previous in-app chat history via support. Users cannot download or save the previous in-app chat history themselves.
• New experience: Copilot Chat will maintain its own history, shared across all supported apps.

User experience images

Image 1: PowerPoint – Translate a presentation

Image 2: PowerPoint – Add speaker notes to current presentation

Image 3: PowerPoint – Create a presentation in the current presentation

Image 4: PowerPoint – Add a slide to the current presentation

Image 5: Word – Generate an audio overview of your document

[What you need to do to prepare:]

No admin action is required to reenable these features once they become available. You may want to update user materials to reflect these changes.

• Create multiple versions of a journey in various languages, customizing each one’s time zone, audience segment, and message assets to fit the intended language and region.
• Automatically initiate and launch a journey targeted at a specific segment whenever a defined event occurs, such as the announcement of lottery results.
• Produce a sequence of journeys to manage all stages of an event’s lifecycle—including sending invitations, reminders, and confirmations—whenever a new event is set up.

• The case owner will be updated.
• The WorkedBy field will be set to the assigned representative.
• The representative capacity will be consumed.
• The representative presence will be updated to reflect the new assignment.
• All downstream routing rules and policies are honored.

• Prompt the supervisor with a confirmation dialog.
• Allow them to proceed or cancel the assignment.

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

 Today, users can see Outlook contacts created with their Entra ID (AAD) account in Teams, but contacts created in Teams are not available in Outlook. To provide a consistent experience we are making changes to allow Teams contacts, created with a user’s Entra ID (AAD) account, to be visible in Outlook as well.

Upcoming changes to contacts in Teams and Outlook:

Currently, Teams and Outlook maintain separate contact lists for enterprise users. Based on your feedback, we plan to introduce a unified contact experience, ensuring a consistent contacts experience across Outlook and Teams. In future, changes to contacts in users’ organization (Entra ID) account in Teams will reflect in Outlook and vice versa. 

What’s Happened so far: 

• We have completed one round of migration of all Teams contacts to Outlook in January 2024. 
• As a result, users may see more contacts in Outlook, namely those created in Teams and potentially Skype for Business contacts (if enabled). 
• Existing Outlook contacts may also be enriched with additional details from corresponding Teams contacts. 
• Teams users can see Outlook contacts but cannot edit them inside Teams. 

What’s Coming: 

Users will gradually upgrade to the new unified experience from December 2024. The new experience will be enabled for each user across all endpoints (Desktop, Mobile, Devices etc.) simultaneously. Once the new experience is enabled for a user, they will see same set of contacts in Outlook and Teams. Any change in Outlook will reflect in Teams and vice versa. 

All Teams contact changes (creations and edits) made since January will be included in the unified store. During creations, a small set of users may see duplicate contacts in the unified store. To help users navigate the transition, category label ‘Teams Conflict’ will be applied to duplicate contacts. This label will help users see any conflicts (duplicates or inconsistencies) that need their attention. 

[When this will happen:]

This activity is expected to be completed for all active users by September 2025 (previously August) tentatively (previously June). Once this activity is complete, users will work with a single contact list across Teams and Outlook. 

[How this will affect your organization]

Once this change is complete, users will be able to see created contacts across both Outlook and Teams and vice versa.

[What you need to do to prepare]

Action Required: Update your organisation documentation and training materials to reflect the upcoming changes for the new unified contact experience.

You may consider updating your training and documentation as appropriate. If users wish to retain a snapshot of their existing contacts in Outlook, please encourage users to back-up their existing contacts using the export capability in Outlook.

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

Please note that information about meeting link expiry changes related to this rollout has been added.

We are reducing the length of Microsoft Teams meeting URLs for easier sharing. This rollout applies to all Microsoft Teams platforms (Teams for iOS, Android, Mac, Teams devices, desktop, and web).

This message is associated with Microsoft 365 Roadmap ID 381953.

[When this will happen:]

Targeted Release: We will begin rolling out mid-February 2025 (previously mid-January) and expect to complete by late February 2025 (previously late January). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase.

General Availability (Worldwide, GCC): We will begin rolling out mid-May 2025 (previously mid-April) and expect to complete by late May 2025 (previously late April). Only Meet Now use cases (except Meet Now in chats and channels) will be affected in this timeframe. There will be no impact on the scheduled meetings in this phase. Rollout for scheduled meetings and channel Meet Now will be started in early July 2025 and expected to be completed by mid-July 2025.

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

[How this will affect your organization:]

The new URL syntax is: https://teams.microsoft.com/meet/<meeting_id>?p=<HashedPasscode>

To make meeting URL shorter, we are removing several parameters such as tenant ID, conversation ID etc. This change serves two main goals: 1) improving usability of URL during sharing and 2) making the URL more secure and less susceptible to malicious attacks.

Here are some details about how meeting links work and when they expire:

1. In case the meeting organizer gets removed from the tenant, the links to the meetings scheduled by them automatically expire.
2.  Every meeting link expires in 60 days after the scheduled event or in 8 hours, if it was created as Meet Now. Learn more about expiration timelines for different types of meetings.

With the Short Meeting URL release, expiration limit will be applied to all newly created links.

Once the change to Short Meeting URL is released, all newly created meetings will expire as described in the documentation: 60 days after meeting ends for scheduled meetings and 8 hours after creation for Meet Now. Once this expiry period is over, in case someone clicks the link (e.g. outside of Teams app OR in the meeting details inside Teams calendar section), they will be unable to join the meeting.

Note: Old links created before short meeting URL release will continue working as it previously was (user will be able to join even after the documented expiry limits).

The reason why we are making this change is simple: security is our topmost priority. Maintaining a high security level is essential to protect sensitive data, prevent financial losses, ensure business continuity, and meet compliance and legal obligations. It is a critical aspect of modern digital life and business operations. This adjustment is designed to enhance the security of Teams meeting links, thereby better safeguarding the customer tenant. We want to be on par with modern security standards, that’s why the new behavior is a step in the right direction that we must take. It’s not possible to keep the current behavior. If you think it breaks some of your business processes, please leave comment to the MC post and describe your case there.

Recommendations in case the meeting link has expired:

For meeting organizer: We recommend scheduling a new meeting. If the meeting organizer got removed from the tenant someone else should reschedule their meetings from scratch.

For participant: Please reach out to the meeting organizer and ask them to reschedule the meeting or send you an updated link.

[What you need to do to prepare:]

You may want to check if you have any integrations that use parameters from URL. After the rollout, the URL will only contain the meeting ID. Parameters such as tenant ID, organizer ID, conversation ID and message ID will not be in the URL.

You may inform meeting organizers from your tenant who use expired meeting links, or you may want to make a tenant-wide announcement about this change.

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