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

Updated November 25, 2025: After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. 

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

This message is associated with Microsoft 365 Roadmap ID 482191

[When this will happen:]

General Availability (Worldwide): After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience. 

[How this will affect your organization:]

This will be a default on feature.

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

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

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

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

[What you need to do to prepare:]

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

Updated November 25, 2025: We have updated the timeline. Thank you for your patience.

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-November 2025 (previously mid-September) and is expected to complete by mid-December 2025 (previously late November).

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

Updated November 25, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing enhancements to OneDrive that simplify the process of managing files when employees leave your organization. These updates improve visibility, streamline bulk transfers, and help ensure important content remains accessible and shared appropriately.

This feature is associated with Microsoft 365 Roadmap ID 493946.

When this will happen

General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out in mid-October and expect to complete by early December 2025 (previously early November).

How this affects your organization

Managing OneDrive content for departing employees is now more efficient. Key improvements include:

• Redesigned notifications: Account cleanup emails are now more prominent, reducing the chance of being overlooked.
• Improved filtering: New filters help managers quickly locate shared or important files.
• Bulk file transfer with preserved sharing: The “Move and keep sharing” feature allows multiple files to be transferred while retaining existing sharing permissions.
• Consolidated alerts: When six or more files are moved, collaborators receive a single streamlined notification.

These updates help ensure a smooth handover and reduce the risk of losing critical files.

When a user account is deleted, OneDrive access is automatically granted to the manager or designated secondary owner. The recipient receives an email notification with access details and information about the OneDrive retention period. Seven days before the retention period ends, a second reminder email is sent, stating that the OneDrive will be permanently deleted in seven days.

Steps to transfer files:

1. From the email, click View files to access the departing user’s OneDrive.
   
2. Use the Shared filter to view only shared files, or All to see everything.
3. Select files using the checkbox in the table header.
   
4. Click Move to, choose a destination, and check Keep sharing with the same people.



5. Click Move to again to complete the transfer.

Collaborators will receive a single notification once the move is complete:

What you can do to prepare

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

• Inform managers and secondary owners about the new experience.
• Update internal documentation to reflect the new transfer process.
• Watch this guided walkthrough: Simplified file transfer for departing employees

Learn more: OneDrive retention and deletion – SharePoint in Microsoft 365 | Microsoft Learn

Compliance considerations

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

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

[Introduction]

We’re introducing a new capability that allows users to copy agents created in the lite Copilot Studio experience into the full Copilot Studio experience. This upgrade unlocks advanced authoring tools, broader publishing options, and enhanced governance features. It supports organizations looking to scale agent capabilities while maintaining control over lifecycle and data policies.

General Availability (Worldwide): Rollout begins the first week of November 2025 and is expected to complete by mid-December 2025 (previously mid-November).

Who is affected:

• Users authoring agents in the lite Copilot Studio experience within Microsoft 365.
• Admins managing environments and governance in Power Platform admin center.

What will happen:

• Users can copy agents from the lite experience into the full Copilot Studio experience.
• The original agent remains unchanged and usable.
• The copied agent becomes a Copilot Studio custom agent, enabling broader lifecycle and compliance controls.
• Users can edit the copied agent in Microsoft Copilot Studio and test it before sharing.
• As a Copilot Studio custom agent, the copied agent comes with enhanced lifecycle management, usage monitoring and analytics, and governance controls.
• Admins get more governance capabilities from applying Data Loss Prevention (DLP) policies to ensuring Application Lifecycle Management (ALM).
• Copied agents gain access to advanced features such as:
  • Topics and Automations
  • Publishing to additional channels
  • Lifecycle management and analytics
  • Governance controls including DLP and ALM
• Admins can apply Power Platform governance policies to copied agents.
• Licensing requirements:
• Users must have a Microsoft 365 Copilot license or be on a Pay-As-You-Go plan.
• Trial licenses are supported:
  • A user holding a trial license can use this feature.
  • Admins can block trial signups via the Power Platform admin center.
  • Trial licenses include limited capabilities (such as agents cannot be published beyond personal use).
• The copy process does not impact the original agent’s data; the copy is made separately.
• All agents in the full experience are managed using Power Platform environments.

Admins should take the following steps:

• Understand Power Platform concepts: The lite version of Copilot Studio is managed via the Microsoft admin center and focuses on agents within Microsoft 365. The full version is managed through the Power Platform admin center, enabling users to build more advanced agents that can connect beyond Microsoft 365 and leverage Power Platform capabilities such as environments, Dataverse, and lifecycle management.
• Review security and governance capabilities: The full version uses Power Platform concepts, offering enhanced security and governance capabilities. Copied agents are stored in Dataverse for robust lifecycle and access management.
• Set up environments: The full experience manages agents using Power Platform environments. Admins should create or assign environments, optionally link them to groups, and configure role-based access control (RBAC). If no environments exist, users default to the standard environment. Environments are tied to a Power Platform region, so verify location settings.
• Enable environment routing: Admins can turn on Environment routing in the Power Platform admin center to guide users to preferred environments during agent copying.
• Prepare licensing: The system will verify Copilot Studio licensing before copying. Users with the Microsoft 365 Copilot license or on Pay-As-You-Go already have access. Trial licenses are available, but admins can restrict trial signups.
• Set up data policies: Define connector policies and data policies in the Power Platform admin center to restrict connections and ensure compliance. Ensure the Teams and Microsoft 365 channels are enabled for publishing.
• Add admin contact info: Including admin contact details helps users get familiar with Copilot Studio and know where to go for support.

More details will be available on Microsoft Learn starting the week of October 20, 2025.

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

Updated November 25, 2025: We have updated the timeline. Thank you for your patience.

[Introduction]

To support frontline workers using personal devices, Microsoft is introducing a dynamic onboarding wizard for Microsoft Teams. This experience is designed to simplify setup on Android and iOS devices, especially in environments with security policies like multi-factor authentication (MFA) and mobile application management. The wizard adapts automatically to your organization’s policies, helping drive secure and efficient Bring Your Own Device (BYOD) adoption.

This message is associated with Roadmap ID 523213.

[When this will happen:]

• Public Preview: Rollout begins in late November 2025 and is and expected to complete by mid-January 2026
• General Availability: Rollout begins in mid-February 2026 (previously late January) and is and expected to complete by end of February 2026 (previously end of January)

[How this affects your organization:]

• Who is affected: Frontline workers setting up Microsoft Teams on personal Android or iOS devices
• What will happen:
  • A new onboarding wizard will be available via web, optimized for desktop kiosks or shared PCs
  • The wizard dynamically adjusts based on your organization’s security policies
  • Supports MFA setup, with emphasis on Microsoft Authenticator push notifications
  • This tool is optional and designed to improve BYOD Microsoft Teams adoption

[What you can do to prepare:]

• Review the admin documentation to understand the onboarding wizard’s capabilities and limitations
• Consider integrating the wizard into your new user onboarding workflows
• Communicate availability to helpdesk and frontline managers
• Update internal documentation if you support BYOD Microsoft Teams deployment
• Review documentation at the following link: Set up frontline Teams on personal devices

[Compliance considerations:]

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

[Introduction]

The Learning agent is now available in Frontier. This agent helps employees build skills through personalized microlearning and structured learning experiences embedded directly into Microsoft 365 tools. These experiences include personalized task-based Copilot tips to augment workflows, learning recommendations tailored to user skills, curated learning paths, and interactive role-play exercises powered by LinkedIn Learning.

This message is associated with Roadmap ID 490154.

About Frontier

The Frontier program gives customers early, hands-on access to experimental Microsoft 365 Copilot innovations in their own environment. The agents and AI features designated as “Frontier” are previews, built for evaluation and feedback purposes. As these features are still in development, their availability and capabilities may change at any time.

[When this will happen:]

Frontier Availability (Worldwide): Available now.

[How this affects your organization:]

• Who is affected: Customers with Microsoft 365 Copilot and the Microsoft 365 Copilot in Productivity Apps service plan (excluding faculty and student SKUs).
• What will happen:
  • Learning agent (Frontier) will be available to deploy in the Copilot Control Center within Microsoft 365 admin center.
  • Users will be able to install and use the Learning agent within Microsoft 365 Copilot or Teams.
  • Admins have controls to manage deployment, including install, restrict, or remove the agent.
  • Feature is opt-in; admins must deploy or allow access.

[What you can do to prepare:]

• Ensure People Skills is set up in your tenant: People Skills Overview
• Confirm licensing: Users must have an active Microsoft 365 Copilot license.
• Approve or deny access at tenant or user level in Microsoft Admin Center under Copilot > Settings.
• Review admin controls for agents: Settings for Agents

Frontier features are experimental and subject to change. Participation in the Frontier program is optional.

[Compliance considerations:]

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

[Introduction]

We’re introducing new Word, Excel, and PowerPoint agents in Microsoft 365 Copilot to help users create documents, workbooks, and presentations more efficiently in Copilot Chat within the Frontier program. These agents assist with creating documents, workbooks, and presentations by using web and enterprise grounding. Each agent supports multi-turn chat, enabling user to refine content through an interactive back-and-forth conversation.

[When this will happen:]

• Frontier Public Preview (Worldwide): November 18, 2025

[How this affects your organization:]

If your organization is part of the Frontier program and has enabled Anthropic usage in your tenant, users will be able to access Word, Excel, and PowerPoint agents via the navigation pane in the M365 Copilot app or within the Tools menu in Copilot chat across Word, Excel and PowerPoint. Additionally, users can invoke these agents by typing “@” followed by the agent name (for example, @PowerPoint).

Who is affected:

• Copilot Chat users in the Microsoft 365 Copilot app in the Frontier Program.

What will happen:

• Users will have access to the following Copilot agents:
• Word agent: Assists with research, formatting, layout, and content refinement for documents such as strategic plans, policy documents, and technical papers.
• Excel agent: Supports data analysis, formula generation, trend identification, and summarization of insights.
• PowerPoint agent: Helps generate presentations from outlines or documents, suggests layouts, and refines visual storytelling.
• Each agent supports multi-turn chat for iterative content development.
• Users can perform high-level iterations on the generated files via chat directly in the Word, Excel, and PowerPoint agents. For more extensive or granular editing, users can open their documents in the respective applications.



• The feature will be ON by default for tenants with Copilot access, Frontier enabled, and for tenants who have opted into Anthropic usage. If Anthropic usage is disabled by the admin, the agents will not appear in the user experience. Learn more: Connect to Anthropic’s AI models | Microsoft Learn.

[What you can do to prepare:]

• No action is required at this time.
• Communicate availability to helpdesk or content teams.
• If desired, review internal documentation or training materials to reflect the new capabilities.

Learn more: Get started with Word, Excel, and PowerPoint Agents in Microsoft 365 Copilot (Frontier)

[Compliance considerations:]

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

[Introduction]

We’re introducing Opal (Frontier), a new Computer Use Agent experience available under the Frontier program for Microsoft 365 enterprise users. This experience is designed to be managed by tenant admins and will be accessible only to selected user groups. Opal will appear in the Microsoft 365 Copilot app and website once enabled.

[When this will happen:]

• Public Preview (Worldwide): Begins mid-November 2025.

[How this affects your organization:]

Who is affected:

• Tenant admins managing Copilot Settings in the Microsoft 365 admin center.
• Enterprise users with Microsoft 365 Copilot licenses in selected groups.

What will happen:

• This feature will be off by default for all tenants.
• Tenant admins can enable Opal (Frontier) via Copilot Settings in the Microsoft 365 admin center.
• Additional setup will be required in Opal.
• Once enabled, users will find Opal in the left navigation of the Microsoft 365 Copilot app and website.

[What you can do to prepare:]

• Ensure all intended users have a Microsoft 365 Copilot license.
• Confirm your organization has an Intune license.
• Select user groups for access via Copilot Settings in the Microsoft 365 admin center.
• Complete Opal setup steps in the Opal Admin Portal:
  • Set up the Cloud PC pool.
  • Define website allowlist.
  • Provide organization-specific instructions.
• Review internal documentation and communicate changes to helpdesk staff.

Learn more:

• Setting up and Managing Project Opal (Frontier)
• Get started with Project Opal (Frontier)

[Compliance considerations:]

Updated November 25, 2025: We have updated the timeline. Thank you for your patience. 

[Introduction]

The Interpreter agent is now available in Microsoft Teams Rooms on Windows for devices with a Teams Rooms Pro license. This feature enables real-time interpretation in up to nine languages, allowing participants to speak and listen in their preferred language. It also offers an option to simulate a participant’s personal voice for a more inclusive experience. No additional Copilot license is required.

Screenshot 1: Console

Screenshot 2: Front of room display

This message is associated with Microsoft 365 Roadmap ID 516571.

[When this will happen:]

• General Availability (Worldwide): Rolling out early January 2026 (previously mid-December 2025), expected completion by late January 2026 (previously mid-January).

[How this will affect your organization:]

Who is affected: Organizations using Teams Rooms on Windows with Teams Rooms Pro licensing.

What will happen:

• Users can turn on Interpreter during a meeting:
  • Go to More > Turn on Interpreter, then select the language and voice option.
• Supported languages: Chinese (Mandarin), English, French, German, Italian, Japanese, Korean, Portuguese, Spanish.
• Voice representation options: Simulated my voice (default) or Automated voice.
• Privacy: Voice samples or biometric data are never stored; original audio is analyzed in real time and not retained.
• Interpretation is simultaneous and may introduce a short delay; accuracy and latency improvements are ongoing.
• Tenant settings:
  • Interpreter is enabled by default. Admins can control whether the organization can use Interpreter and set the default voice option.
  • No device-level setting in the Pro Management Portal (PMP).
• Licensing: 20 hours of interpretation included per room account per month with a Teams Rooms Pro license. Access beyond included hours is subject to available capacity.

Learn more: Manage Interpreter agent for your organization – Microsoft Teams | Microsoft Learn 

[What you need to do to prepare:]

• Ensure room accounts have a Teams Rooms Pro license.
• Review tenant settings:
  • Confirm Interpreter is enabled (default).
  • Set the preferred default voice option in your tenant.
• Communicate this change to helpdesk and support teams.
• Update internal documentation to reflect the new functionality.

[Compliance considerations:]

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

[Introduction]

We’re updating the Copilot Chat experience in Microsoft 365 apps by moving the entry point button out of the ribbon and into the document canvas. This change makes Copilot Chat easier to discover and use, and introduces curated, contextual prompt suggestions relevant to the current document or selection.

[When this will happen:]

General Availability (Worldwide): Rollout begins early December 2025 and is expected to complete by late March 2026.

• Word, Excel, PowerPoint (Web, Desktop, Mobile): rollout will start for a % of Small Business and Enterprise users without a Microsoft 365 Copilot license who have pinning enabled. These users will see the entry point for Copilot move out of the ribbon, represented by the icon pictured below.
• We will continue the rollout progressively for users with a Microsoft 365 Copilot license in the new year.

Who is affected:

• Microsoft 365 users of Word, Excel, and PowerPoint across web, desktop, and mobile who are eligible for Copilot Chat.

What will happen:

• The Copilot Chat entry point will move from the app ribbon into the document canvas.
• Users will see a new Copilot icon in the canvas to open Copilot Chat.

  

• Contextual prompt suggestions will appear to help users engage with Copilot Chat.
• The feature remains ON by default for eligible users across web, mobile, and desktop.
• Admins can still disable Copilot Chat using the “Pin Microsoft 365 Copilot Chat” setting in the admin center.
• No changes to Copilot Chat functionality or value.

• No admin action is required.
• If your “Pin Microsoft 365 Copilot Chat” setting is configured to “Do not pin,” update it to “Pin” if you want users without a Copilot license to access Copilot Chat in Microsoft 365 apps.
• Learn more:
  • Manage Microsoft 365 Copilot Chat.
  • Pin Microsoft 365 Copilot Chat in the Microsoft 365 apps

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

Updated November 26, 2025: We have updated the content below to provide additional information. Thank you for your feedback.

[Introduction]

We’re improving the performance and startup time of calling features in the Microsoft Teams Desktop Client for Windows. To achieve this, we’re introducing a new child process named ms-teams_modulehost.exe that will handle the calling stack separately from the main application process (ms-teams.exe). This change optimizes resource usage and enhances meeting experiences.

Worldwide, GCC, GCC High, and DoD: Rollout will begin early January 2026 and complete by late January 2026.

Note: Timelines may shift due to year-end feature flag rollout freeze.

• Who is affected: All users running the Teams Desktop Client on Windows.
• What will happen:
  • A new process (ms-teams_modulehost.exe) will appear in Task Manager under the main Teams process (ms-teams.exe).
  • This process is dedicated to calling features and improves performance.
  • No changes to user workflows or UI; however, admins should ensure endpoint and security software allow this new process.

• Update endpoint management and security software to allowlist ms-teams_modulehost.exe alongside ms-teams.exe.
• Communicate this change to helpdesk staff to avoid confusion during troubleshooting.
• Update internal documentation if you reference Teams process names.
• Make sure the same QoS settings applied to ms-teams.exe are also applied to ms-teams_modulehost.exe. Refer to this page for details: Implement Quality of Service (QoS) in Microsoft Teams
  • DO NOT remove QoS settings of ms-teams.exe. Only add QoS settings for ms-teams_modulehost.exe.

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

Organizational Messages will soon include email as a delivery channel, expanding beyond existing surfaces such as the Windows Taskbar, Windows Notifications, Windows Spotlight, and Teams popovers. This enhancement helps organizations reach users through familiar communication channels, improving engagement and adoption.

This message is associated with Microsoft 365 Roadmap ID 503562.

[When this will happen] 

• Public Preview (Worldwide): Rollout began in mid-November 2025 and is expected to complete by late January 2026.
• General Availability (Worldwide): Rollout begins in late March 2026 and is expected complete by late April 2026.

[How this will affect your organization]

Who is affected: Admins managing Organizational Messages in Microsoft 365.

What will happen:

• Email will be added as a delivery channel for Organizational Messages.
• Admins can send premade, templatized messages via email in addition to existing surfaces like Windows Spotlight, Taskbar, Notification Center, and Teams popovers:



• During Public Preview, new pre-built email templates will be available:

 

• Two welcome messages: Welcome to Copilot and Welcome to Copilot Chat.
• Six weekly Great M365 Copilot Journey emails highlighting features and best practices to drive onboarding and adoption.

[What you need to do to prepare]

No action is required at this time.

[Compliance considerations]

No compliance impacts identified. Review your organization’s policies as needed.

We’re making some changes to the Microsoft eCDN configuration.

Starting with Chrome 142, browsers will enforce Local Network Access restrictions that may impact Microsoft eCDN peer-to-peer functionality.

[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 Microsoft eCDN. To maintain optimal performance for Teams Live Events and Town Halls, admins must configure the LocalNetworkAccessAllowedForUrls policy for Chrome-based browsers

[What you need to do to prepare:]

Admins will need to:

Add the following URLs to the LocalNetworkAccessAllowedForUrls policy in your environment:

• [*.]ecdn.teams.microsoft.com
• https://teams.microsoft.com
• [*.]ecdn.teams.cloud.microsoft
• https://teams.cloud.microsoft
• https://engage.cloud.microsoft/

Apply these settings via Group Policy or registry keys for:

• Microsoft Edge: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\
• Google Chrome: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\

For US Government tenants, use GCC/GCC High-specific hostnames as outlined in the documentation.

Additional Notes:

• This change aligns with Microsoft’s Unified Domains initiative. Ensure your network filters include both legacy and new domains.
• Pair this configuration with WebRtcLocalIpsAllowedUrls for full peer-to-peer functionality.
• Firefox restrictions are planned but not yet enforced.

See documentation for full guidance: Configure Local Network Access Policy for Microsoft eCDN

• Block the action based on the governance policy configured in Power Platform admin center.
• Create a notification message in Power Pages Studio.

• Allowing admins to enable/disable this governance control at the environment level with site level exception.
• Giving insights and recommendations related to site visibility in Action Center.

• Gain detailed visibility into messages blocked by the default protection mechanism, with the ability to drill down into specific cases.
• Receive proactive prompts to take immediate actions that ensure agents remain secure, compliant, and high performing.
• Access tailored recommendations to strengthen agent security and operational resilience.