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

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

Coming soon to Microsoft Teams: When users connect to their organization’s Wi-Fi, Teams can automatically set their work location to reflect the building they are working in. This makes it easier for users to coordinate work with their coworkers and connect in person.

This feature is opt-in and requires you to take action to configure it. After you turn it on, end-users remain in control and can choose whether to share their work location with their coworkers.

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

This message is associated with Microsoft 365 Roadmap ID 488800.

[When this will happen:]

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

[How this will affect your organization:]

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

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

[What you need to do to prepare:]

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

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

Updated November 3, 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): Modern labels have been in Public Preview since July 7th 2025. This post announces the rollout of modern label scheme to new tenants and tenants with applicable parents.

General Availability (Worldwide): We will being rolling out early December 2025 and expect to be completed by late December 2025. As part of GA, customers with non-applicable parents will be auto migrated to the modern label scheme while migration for customers with applicable parents will continue to be opt-in for 12 months post-GA. We will auto-migrate customers with applicable parents to the modern label scheme once the 12-month extension ends in December 2026. 

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

[Introduction:]

To help users quickly identify external participants in Microsoft Teams and reduce the risk of oversharing sensitive information, we’re introducing Trust Indicators—visual labels (badges or icons) next to people’s names. These indicators signal whether someone is external to your organization, a guest, or an anonymous meeting participant.

This message is associated with Microsoft 365 Roadmap ID 515169.

[When this will happen:]

Public Preview: Begins rolling out late September 2025; expected completion by late November 2025.

General Availability (Worldwide, GCC, GCC High, DoD): Begins rolling out late November 2025; expected completion by early January 2026.

[How this affects your organization:]

Who is affected: All Microsoft Teams users across commercial, GCC, GCC High, and DoD environments.

What will happen:

• Users will see badges or icons next to names of external participants in Teams:





• The visual indicator will vary depending on the relationship (guest, external, anonymous):



• These indicators will appear across multiple Teams surfaces.
• No admin action is required to enable this feature; it will be ON by default.

[What you can do to prepare:]

No action is required to enable the feature.

Admins can:

• Review the documentation to understand the types of Trust Indicators and their behavior: Representation of users outside your organization | Microsoft Teams | Microsoft Learn
• Communicate this change to helpdesk or support teams.
• Update internal documentation if you reference user identity indicators in Teams.

[Compliance considerations:]

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

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

We’re introducing support for Model Context Protocol (MCP)-based agents in Microsoft 365 Copilot and the Microsoft 365 admin center. This update enables developers to build Copilot agents using MCP servers and allows users and admins to interact with these agents using familiar experiences. This change supports extensibility and improves agent management capabilities for organizations.

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

Who is affected:

• Admins managing Microsoft 365 Copilot
• Users accessing Copilot agents

What will happen:

• MCP-based agents will appear in the Copilot Agent Store
• Users can install MCP-based agents directly from the store
• Admins can deploy MCP-based agents to users via the store or custom packages
• Admins will see MCP agent details, including server information, in the Microsoft 365 admin center under Copilot > Agents
• Existing extensibility controls and lifecycle management policies for Copilot agents will apply to MCP-based agents
• The feature will be ON by default for all tenants

Screenshot 1 – Admin view:

Screenshot 2 – User view:

[What you can do to prepare:]

• No action is required at this time
• Review the MCP-based agent catalog to ensure agents align with your organization’s policies
• Update internal documentation if you track agent types or deployment methods
• Communicate this change to helpdesk or support teams as needed

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

Updated November 3, 2025: We have updated this message to clarify the new experience and to clarify that the AI disclaimer will always be visible

[Introduction:]

We’re updating the AI Disclaimer experience in Microsoft Copilot Chat based on customer feedback. To address this, we’re introducing an admin control that allows organizations to customize how the disclaimer appears, improving user awareness and flexibility.

[When this will happen:] 

Rollout will begin in late November 2025 and complete by:

• Worldwide & GCC: Early December 2025
• GCC High & DoD: Mid-December 2025

[How this affects your organization:]

Who is affected:

• All users of Microsoft Copilot Chat on desktop and web experiences.

What will happen:

• The AI disclaimer will remain visible in the user experience.
• Admins will gain the ability to heighten this message and to provide a link to their own documentation:
  • The disclaimer will display bolded text for increased visibility.
  • Admins can configure a custom URL pointing to their AI policy documentation.

We’re retiring the “When a device isn’t eligible to run Windows 11, install the latest Windows 10 feature update” option in the Feature Updates policy within Intune. As we reach the end of support for Windows 10, this setting no longer provides value add. This change is part of our ongoing efforts to simplify update management and reduce configuration complexity across tenant environments. This functionality will also be retired from programmatic controls for Windows feature updates via Microsoft Graph API, following the same deprecation timeline.

[When will this happen:]

The deprecation will be rolled out starting February 17th, 2026.

[How will this affect your organization:]

This change applies to both standalone and multi-phase feature update policies. For devices in existing Feature Update policies where this option is selected, those that are not eligible for a Windows 11 upgrade will continue to receive Windows 10, 22H2 updates until the deprecation date of February 17, 2026. The same timeline applies to programmatic controls via Microsoft Graph API.

[What you need to do to prepare:]

If you plan to upgrade devices to Windows 10 22H2 to enable Extended Security Updates (ESU), you can continue to use the Feature Update workflow in Intune and programmatic controls via Graph API until the deprecation date. This serves as a 3-month advanced notice, and the option will remain available during this period to help transition smoothly to Windows10 22H2.

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

[Introduction:]

We are expanding inline protections for uploads in Microsoft Edge for Business to cover more unmanaged consumer generative AI (GenAI) apps. With this update, admins can apply Microsoft Purview collection policies and Purview Data Loss Prevention (DLP) policies to detect and prevent sensitive data sharing in the Edge browser when users interact with these additional unmanaged app locations. Inline protections are built directly into Edge for Business and work for users on Intune-managed Windows devices. This enhancement complements existing capabilities, giving organizations greater flexibility to enforce data security controls across a broader set of GenAI apps.

This message is associated with Microsoft 365 Roadmap ID 518643.

[When this will happen:]

• Public Preview: Begins mid-November 2025, expected to complete by early December 2025.
• General Availability (Worldwide): Begins in early December 2025 and is expected to complete by the end of the month.

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft Purview DLP and collection policies for Edge for Business
• Users on Intune-managed Windows devices using Edge for Business

• Admins can extend current Purview collection and DLP policies to include new unmanaged GenAI app locations for inline protection.
• No additional deployment steps are required.
• Inline protections are built directly into Edge for Business.
• Automated behaviors will block use of unprotected browsers for users included in policies that block activities in unmanaged GenAI apps.

[What you can do to prepare:]

No action is required to enable this feature. To learn more or update your policies, review the following resources:

• Cloud apps detection – Collection policy reference | Microsoft Learn
• Data Loss Prevention policy reference | Microsoft Learn
• Learn about Data Loss Prevention for Cloud Apps in Edge for Business | Microsoft Learn

[Compliance considerations:]

Microsoft is introducing the ability to start, stop, and restart meeting recording and transcription directly from Microsoft Teams Rooms on Android devices. This enhancement supports a more seamless meeting experience by removing the need for a companion device to initiate these actions. Spoken language for the meeting can also be changed during the session. This functionality is available with Teams Rooms Pro licensing.

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

General Availability (GCCH and DoD): We will begin rolling out in early January 2026 and expect to complete by the end of January 2026.

Who is affected:

• Users joining Teams meetings from Microsoft Teams Rooms on Android devices.
• Organizations with Teams Rooms Pro licensing.

What will happen:

• Users can start, stop, and restart recording and transcription directly from a Teams Rooms device running Android. To do this, they can select More on the meeting interface, then choose Record and transcribe to initiate or stop the recording and transcription.
• The spoken language for the meeting can be changed during the session.
• Previously, users needed a companion device to initiate recording or transcription.
• Recording and transcription are supported in meetings where a participant belongs to the same tenant as the organizer.
• For Meet now or Whiteboard sessions initiated from a Teams Rooms on Windows device, users must invite themselves to the meeting to access the recording file via Teams desktop or mobile app.
• To use the start and stop recording and transcription feature, both the meeting organizer and the room account must have permission to record and transcribe. If either party lacks the required permissions, the button to initiate or stop recording and transcription will not appear.
• If the meeting organizer removes recording or transcription permissions from the room account using meeting options, the button will also be unavailable.

• Limitations – Recording and transcription are not supported in the following scenarios:
  • Peer-to-peer (P2P) calls: Direct one-on-one calls between two users.
  • Group calls: Ad-hoc calls involving multiple participants that are not scheduled meetings.
  • PSTN calls: Calls made through the Public Switched Telephone Network using Teams Calling Plans or Direct Routing.
  • External or cross-tenant meetings and calls: Meetings involving participants from outside the organizer’s tenant.
  • Third-party meetings and calls: Including Direct Guest Join and SIP-based meetings, which use the Session Initiation Protocol to connect external video conferencing systems (such as Cisco or Polycom) to Microsoft Teams. These integrations do not support native Teams recording and transcription features.

Screenshot – New recording and transcription controls in Teams Rooms on Android:

• Ensure room accounts and meeting organizers have permissions to record and transcribe meetings.
• Communicate this change to helpdesk and support teams.
• Update internal documentation to reflect the new functionality.
• Review meeting options to confirm room account permissions are correctly configured.

Compliance considerations:

[Introduction]

To help organizations adopt Microsoft 365 Copilot securely, Microsoft Purview is introducing new capabilities in Microsoft Admin Center. These enhancements allow AI and IT admins to gain visibility into oversharing risks, remediate issues, and apply a new Data Loss Prevention (DLP) policy directly within Microsoft Admin Center. This update supports secure usage of Copilot by enabling protection of sensitive interactions.

This message is associated with Microsoft 365 Roadmap ID 523212.

[When this will happen:]

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

[How this affects your organization:]

• Who is affected: Admins managing Microsoft 365 Copilot and data security policies via Microsoft Admin Center or Purview portal.
• What will happen:
  • A new Security pivot will be added to the Microsoft Admin Center.
  • Admins can create a policy to block specific sensitive information types from being used in Copilot.
  • Visibility into oversharing risks and sensitive Copilot interactions will be available.

[What you can do to prepare:]

• Review how Copilot is secure by default and assess if additional protections are needed.
• Once the feature is released:
  • Use an Entra AI Admin or Entra Global Admin role to create a policy to block sensitive information types in Microsoft Admin Center.
  • Collaborate with your data security admin to apply additional protections and ensure compliance with AI regulations.
  • These actions can also be performed in the Purview portal. Learn more: Use Microsoft Purview to manage data security & compliance for Microsoft 365 Copilot & Microsoft 365 Copilot Chat.

[Compliance considerations:]

Introduction

Microsoft’s eSignature service enables users to request simple electronic signatures directly from Word and PDF documents stored in SharePoint. This feature ensures documents remain within Microsoft’s trusted boundaries during the electronic signature workflow, enhancing security and compliance. This capability is now expanding to Türkiye.

When this will happen 

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

How this affects your organization

• Who is affected: SharePoint administrators and users in Türkiye. Microsoft 365 tenants with SharePoint eSignature enabled.
• What will happen:
  • Users will be able to request eSignatures from Word documents using Microsoft Word Desktop (Beta and Current Channels) when stored in SharePoint eSignature-enabled sites.
  • Users will be able to request eSignatures from PDF documents hosted in SharePoint eSignature-enabled sites.
  • This feature is off by default and requires admin configuration to enable.

What you can do to prepare

Enable eSignature:

• In the Microsoft 365 admin center, toggle the Word option ON for your tenant.
• Deploy the Group Policy setting Allow the use of SharePoint eSignature for Microsoft Word using:
  • Cloud Policy Service
  • Microsoft Intune
  • Group Policy Manager
• Note: eSignature for PDFs does not require Group Policy configuration.
• Inform your users about the new eSignature experience available in Word and PDF documents stored in SharePoint.

Compliance considerations

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

[Introduction:]

We’re excited to announce a major milestone for Viva Amplify: the rollout of a new publishing stack that modernizes how content is created, distributed, and consumed across Microsoft 365. This upgrade powers both the Amplify app and Amplify from SharePoint, enabling faster, more reliable publishing to SharePoint, Viva Engage, Outlook, and Teams. The new stack replaces legacy timer job-based publishing with a parallelized, structured system that improves performance and error transparency.

[When this will happen:]

• Targeted Release: Begins mid-November 2025; expected completion by late November 2025.
• General Availability: Begins late November 2025; expected completion by early December 2025.

[How this affects your organization:]

Who is affected: Admins and users publishing content via Viva Amplify or Amplify from SharePoint.

What will happen:

• The legacy publishing stack, which relied on timer jobs and had reliability issues, will be replaced.
• Publishing operations will now execute in parallel, reducing latency from minutes to ~16 seconds.
• The new stack introduces structured error handling, providing detailed, actionable feedback to users (screenshots 1 & 2):
  • Screenshot 1

 

• Screenshot 2 



• Error infrastructure has been generalized into “results,” allowing multiple independent errors, warnings, and messages to be surfaced. This gives users and developers a clearer understanding of publishing outcomes and helps reduce frustration and build trust.
• Publishing will be more consistent across channels, improving delivery to Outlook, Engage, Teams, and SharePoint.
• The infrastructure supports scalability for increased publishing demand.
• Feature will be ON by default for all tenants.
• No changes to existing admin policies or user workflows.

[What you can do to prepare:]

No admin action is required. However, you may consider the following:

• Review any internal help or guidance materials you’ve created for end users.
• Communicate the performance improvements and error handling enhancements to relevant teams.
• Update internal documentation if you detail publishing workflows.
• Ensure that users who need access to Viva Amplify have either a Microsoft Viva suite license or a Microsoft Viva Employee Communications and Communities license.

[Compliance considerations:]

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

[Introduction]

We’re updating the People experience in Microsoft Places to better align with other Microsoft 365 apps. The ability to edit favorite contacts specific to Places will be removed, and Places will use the same “frequent contacts” logic as other Microsoft 365 apps. As part of this realignment, we’re also removing the ability for tenant admins to control whether specific users can be added to other users’ list of favorite contacts specific to Places, which was controlled by Set-PlacesSetting -AllowInConnectionsList.

Microsoft Places is a hybrid scheduling and workplace coordination app in Microsoft 365 that helps users understand where their colleagues plan to work—whether remotely or in the office—and coordinate in-person collaboration. It integrates with Outlook and Teams to surface location-aware insights like who’s coming into the office and when.

[When this will happen:]

• This feature will retire in early December 2025

[How this affects your organization:]

Who is affected:

• All users of Microsoft Places across Microsoft 365 tenants.

What will happen:

• Users will no longer be able to manage or view “favorite contacts” in the Places app.
• Tenant admins will no longer be able to control whether specific users can be added to other users’ list of favorite contacts specific to Places.
• Places Cards in Teams and Outlook calendars will display frequent contacts based on Microsoft 365 usage patterns.
• No admin action is required to enable this change; it will be applied automatically.

[What you can do to prepare:]

• Inform users about the upcoming change to avoid confusion.
• Update internal documentation and training materials that reference “favorite contacts” in Microsoft Places.
• Revise any custom workflows or helpdesk scripts referencing this feature.

[Compliance considerations:]

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

Microsoft Defender Application Guard for Office was retired in April 2024 and is now being removed from Office. This change aligns with the end of support for Windows 11 version 23H2 and helps streamline the security experience for users. Documents that previously opened in Application Guard will now open in Protected View, maintaining strong protection against threats.

Phase 1: Removal begins with Office version 2602

• Current Channel: early February 2026
• Monthly Enterprise Channel: April 2026
• Semi-Annual Enterprise Channel: July 2026

Phase 2: Full removal with Office version 2612

• Current Channel: early December 2026
• Monthly Enterprise Channel: February 2027
• Semi-Annual Enterprise Channel: July 2027

Who is affected: All Win32 users who previously used Microsoft Defender Application Guard for Office.

What will happen:

• Files that previously opened in Application Guard will now open in Protected View.
• Application Guard for Office will be disabled in Phase 1; support exceptions may be available until Phase 2.
• Application Guard for Office will be fully removed in Phase 2 with no workaround.
• Admins are encouraged to enable Microsoft Defender for Endpoint Attack Surface Reduction (ASR) rules and Windows Defender Application Control (WDAC).

No admin action is required for the removal itself. However, to maintain strong protection, we recommend:

• Enable Microsoft Defender for Endpoint ASR rules to block risky behaviors in Office files.
• Enable Windows Defender Application Control (WDAC) to ensure only trusted, signed code runs on devices.
• Review internal documentation and helpdesk guidance if your organization previously relied on Application Guard for Office.

For instructions on verifying if users are using Application Guard for Office, refer to Confirm that Application Guard for Office is enabled and working – Application Guard for Office for admins | Microsoft Learn.

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

[Introduction]

We’re introducing a redesigned Microsoft Teams Store that enhances the agent-first discovery experience. This update simplifies how users find, explore, and manage apps and agents, aligning with feedback for a more intuitive and efficient interface.

[When this will happen:]

Preview (Worldwide): We will begin rolling out late October 2025 and expect to complete by late January 2026.

[How this affects your organization:]

Who is affected:

• All Microsoft Teams users across commercial and education tenants.

What will happen:

• Users will see a modernized Teams Store interface.
• A new “Agent” filter pill will appear under every category for faster agent discovery.
• App tiles will be streamlined to show only essential information.
• Search will be prominently centered on the page.
• Categories will be simplified with subcategories for easier navigation.
• The app details page will be redesigned to highlight the most relevant information.
• A new “Your Apps & Agents” hub will allow users to view and manage all installed apps and agents in one place.
• No action is needed from users or admins.

[What you can do to prepare:]

No action is required at this time. However, you may wish to:

• Communicate this change to helpdesk staff to reduce potential confusion.
• Update internal documentation or training materials that reference the Teams Store interface.
• Review app and agent usage in your tenant to anticipate user questions.

[Compliance considerations:]

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

We are introducing Copilot-powered summaries and insights as a landing page within Copilot Notebooks. This feature is designed to help users quickly gain an understanding of the references in their notebooks.

The feature will initially be available in the web experience (Preview and General Availability), with mobile availability (iOS and Android) planned for a future release.

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

This message is associated with Microsoft 365 Roadmap ID 512430.

[When this will happen:]

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

[How this will affect your organization:]

Who is affected: All users of Copilot Notebooks with eligible licenses.

What will happen:

• Users will see summaries and insights as the default landing page in Copilot Notebooks:

 

• The landing page is powered by a fine-tuned prompt for Copilot.
• This feature is enabled by default.
• Existing Copilot Notebooks admin controls will continue to apply.
• No changes to user workflow unless customized by admin.

[What you need to do to prepare:]

No action is required to enable the feature. However, to ensure users can access it:

• Confirm that your organization has Microsoft 365 Copilot licenses assigned to intended users.
• Review your Microsoft 365 licensing documentation or contact your Microsoft account representative to verify eligibility.

[Compliance considerations:]

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

Outlook mobile users can now prepare for their meetings using Copilot chat with a single tap. This feature is available on Android and iOS platforms and requires a Microsoft 365 Copilot license. It helps users quickly access relevant meeting information, making preparation more efficient and personalized.

This message is associated with Microsoft 365 Roadmap ID 516568.

[When this will happen:]

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

[How this affects your organization:]

• Who is affected: Users of Outlook mobile on Android and iOS who have a Microsoft 365 Copilot license.
• What will happen:
  • Eligible users will see a new Copilot chat option to prepare for meetings directly within Outlook mobile.
  • The feature will be ON by default for licensed users. To turn off Copilot in Outlook review Turn off Copilot in Microsoft 365 apps | Microsoft Support.
  • No admin configuration is required.
  • Existing policies and permissions are respected.

Screenshots 1-3 provide a view of the previous experience:

Screenshots 4-5 provide a view of the new experience – Selecting Prepare will take users to Copilot Chat, enabling users to ask follow-up questions:

[What you can do to prepare:]

• No admin action is required at this time.
• If desired, communicate this feature to helpdesk staff.
• Update internal documentation if you detail this feature.
• Ensure users have the appropriate Microsoft 365 Copilot license to access this feature.

[Compliance considerations:]

Microsoft is introducing a new capability in Teams that enables Channel Agent to orchestrate tasks with select third-party Model Context Protocol (MCP) servers, including GitHub, Asana, and Atlassian (JIRA). This integration supports collaborative workflows that reflect real human teamwork, allowing agents to transparently reason through tasks and gather information across tools. This change helps reduce manual switching between apps and improves task completion efficiency—all within the familiar Teams environment.

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

This message is associated with Microsoft 365 Roadmap ID 515466.

• Targeted Release (Worldwide): Begins in mid-November 2025 and is expected to complete by mid-December 2025.

Who is affected: Microsoft 365 tenants using Teams and Channel Agent integrations.

What will happen:

• Channel Agent will be able to collaborate with Model Context Protocol (MCP) servers like GitHub, Asana, and Jira.
• Users can ask Channel Agent questions and receive coordinated responses across tools:

          Screenshot 1

Screenshot 2



• The feature will be available in preview and requires admin enablement.
• A Microsoft 365 Copilot license is required.
• There is no impact unless enabled by tenant admins.

What you can do to prepare

• Enable Channel Agent usage in Teams for your tenant.
• Allow apps that integrate with Model Context Protocol (MCP) servers such as GitHub, Asana, or Jira.
• Ensure users who need access have a Microsoft 365 Copilot license.
• Review internal documentation and update helpdesk guidance as needed.

Compliance considerations

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

[Introduction]

We’re introducing AI-powered enhancements to the SharePoint FAQ web part to help content owners keep FAQs accurate and fresh with less effort. These updates are based on customer feedback and aim to improve content reliability and reduce manual upkeep. Key improvements include AI-suggested updates, seamless import of existing FAQs, and the ability to ground answers in SharePoint Pages.

This message is associated with Roadmap ID 482198.

[When this will happen:]

• Targeted Release: Rollout begins in late November 2025 and completes by early December 2025.
• General Availability (Worldwide, GCC): Rollout begins in late December 2025 and completes by early January 2026.

Who is affected: Content authors using the SharePoint FAQ web part with a Microsoft 365 Copilot license.

What will happen:

The following enhancements will be available to improve FAQ management and content accuracy:

• On-demand AI-suggested FAQ updates: Authors can manually trigger a freshness check. AI will analyze grounding files and viewer-submitted questions to identify outdated or inaccurate FAQ entries and suggest revisions.
Screenshot 1: FAQ authors can trigger an on-demand update check whenever new AI-generated update suggestions are available.



Screenshot 2: FAQ authors can review and approve AI suggestions to keep the content accurate and up to date.



• Seamless import of existing FAQs: Authors can copy and paste curated FAQ content directly into the SharePoint FAQ web part, enabling quick integration of existing knowledge assets.

Screenshot 3: FAQ authors can easily import Q&A pairs by simply pasting content.



• SharePoint Page as grounding source: FAQ answers can be grounded in SharePoint content, including the current page or other selected pages, improving response reliability and contextual relevance.

Screenshot 4: FAQ authors can use the current page or existing pages as reference sources.

[What you can do to prepare:]

• No admin action required: The feature will be enabled by default for eligible users.
• Notify content authors and site owners about the new capabilities.
• Update internal documentation or training materials as needed.
• Review the updated FAQ web part documentation when available (expected late November).

Use a FAQ web part in SharePoint (documentation will be updated in late November)

[Compliance considerations:]

[Introduction]

We’re introducing the Adaptive Front-of-Room Experience for Microsoft Teams Rooms on Android in Town Hall scenarios. This update helps create a distraction-free experience for attendees while giving presenters full control over what’s shown on the front-of-room display. It’s designed to support hybrid Town Halls where presenters and attendees share the same physical space.

A Microsoft Teams Rooms Pro license is required to use this feature.

This message is associated with RMID 500378.

[When this will happen:]

General Availability (Worldwide): Rollout will begin by the second week of December 2025.

[How this affects your organization:]

• Who is affected: Organizations must have a Microsoft Teams Rooms Pro license to benefit from this feature. It applies to Teams Rooms on Android devices used in Town Hall scenarios.
• What will happen:
  • Teams Rooms added will join Town Hall meetings in a presenter role by default.
  • The front-of-room display will default to attendee view, showing only stage content and hiding backstage distractions.
  • The console will retain full presenter capabilities, including:
    • Green Room access
    • Backroom chat
    • Off-stage management tools
  • Presenters can switch the front-of-room display to presenter view when needed, without disrupting attendees.

Screenshot – New adaptive Front-of-Room Experience for Microsoft Teams Rooms on Android:

[What you can do to prepare:]

• Confirm your organization has a Microsoft Teams Rooms Pro license.
• When scheduling a Town Hall, add the Teams Room and assign it a presenter role.
• Ensure the room device is running the latest version of the Teams Rooms app.
• Communicate this new capability to Town Hall organizers and facilities teams.
• Update internal documentation if you provide guidance on Town Hall participation.

Learn more: Get started with town hall in Microsoft Teams | Meetings | Microsoft Teams | Microsoft Support

[Compliance considerations:]

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

[Introduction]

We’ve added a new Copilot button that gives users a quick and visible entry point to Copilot directly within the file previewer in OneDrive and SharePoint. This button appears near the bottom-right corner of the file previewer (instead of in the command bar) and surfaces contextual prompts for Copilot-supported file types. It also provides access to the Copilot chat.

This message is associated with Roadmap ID 513432.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Users in GCC, GCC High, and DoD environments who preview files in OneDrive or SharePoint.

What will happen:

• A new Copilot button will appear in the bottom-right corner of the file previewer.

• This button provides access to Copilot chat and contextual prompts based on the file type.
• The previous Copilot command in the command bar will be removed.
• No changes to admin policies or settings are required.
• The feature is enabled by default.

[What you can do to prepare:]

• No action is required at this time.
• Communicate this change to helpdesk or support staff.
• Update internal documentation to reflect the new location of the Copilot button.

[Compliance considerations:]

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

We’re announcing the general availability of four Microsoft 365 Copilot for admin skills in the Teams admin center (TAC). Admins can now use Copilot in TAC to quickly find information and resolve issues without switching tools. These skills help IT admins complete common tasks faster using natural language directly in TAC:

• Help and guidance
• Policy troubleshooting
• User search (TAC-specific criteria)
• Call quality troubleshooting

These capabilities reduce time spent navigating tools and improve troubleshooting efficiency.

When this will happen:

General Availability (Worldwide): The rollout began and was completed in November 2025.

How this affects your organization:

Who is affected:

• Admins managing Microsoft Teams via the Teams admin center.
• Tenants with at least one Microsoft 365 Copilot license.

What will happen:

• Admins can use Copilot in TAC to:
  • Get contextual help and step-by-step guidance for common admin tasks.
  • Diagnose and resolve policy misconfigurations across meetings, messaging, and external collaboration.
  • Search for users using Teams-specific filters (such as policy, number assignment, location, client version) via natural language.
  • Investigate poor call quality and receive a consolidated view with likely causes and recommended fixes.
• No additional configuration is required; permissions follow existing admin roles and policies.
• Admins do not need an individual Copilot license assigned to use these skills.

Screenshot 1 – View of the new Copilot experience in TAC:

Screenshot 2 – Copilot in action within TAC, providing step-by-step guidance for a common admin task:

What you can do to prepare:

• Share this update with your Teams administrators and help desk.
• Optionally validate common scenarios in a Public Preview ring.
• Refresh internal runbooks or documentation where applicable.

Suggested sample prompts for admins:

• “Why can’t Megan Bowen record meetings? Show which policy setting blocks it and how to fix.”
• “Find users assigned the Global messaging policy who have no phone number assigned.”
• “Investigate poor call quality for Diego last week and recommend next steps.”
• “How do I configure meeting policies for external participants?”

Learn more:

• Copilot in Microsoft 365 admin centers | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn
• How can I use Copilot in Microsoft 365 admin centers? | Microsoft 365 Copilot | Microsoft Learn

[Compliance considerations:]

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

To streamline Microsoft Word and focus on core productivity features, we are retiring the Send to Kindle integration, which allows users to upload documents directly to Kindle from Word.

[When this will happen:]

The retirement will begin on February 9th, 2026, and the feature will be fully removed by March 9th, 2026.

[How this will affect your organization:]

The Send to Kindle feature will no longer be available in Word for Window desktop, Word for Mac desktop, and Word for the web after the retirement period. (This feature was never available for iOS/Android.) Users will still be able to upload .doc and .docx files to Kindle using https://www.amazon.com/sendtokindle. Documents already sent to Kindle will not be affected by this retirement.

[What you need to do to prepare:]

No admin action is required. We recommend informing users of this change and updating any internal documentation or workflows that reference the Send to Kindle feature.

[Introduction]

To improve mobile productivity and streamline file access, Outlook for Android will soon support in-app PDF attachment previews. This update aligns with user feedback requesting faster, more integrated document viewing experiences without needing to switch apps.

This message is associated with Roadmap ID 520386.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• All users of Outlook for Android across commercial and education tenants.

What will happen:

• Users will be able to preview PDF attachments directly within the Outlook for Android app.
• The built-in previewer will launch automatically when a PDF is opened.
• Users can still choose to open PDFs in other apps via the overflow menu.
• This feature will be enabled by default; no admin configuration is required.

[What you can do to prepare:]

No action is required. This feature will be enabled automatically.

Optional steps:

• Communicate this change to helpdesk staff to reduce potential support inquiries.
• Update internal documentation if you reference mobile attachment handling.
• If your organization prefers users to use a specific PDF viewer, consider communicating usage guidance.

[Compliance considerations:]

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

[Introduction:]

We’re introducing a new capability that allows Microsoft Viva Glint admins to delete custom user attributes directly within the platform. This enhancement streamlines data management by removing the need to contact support for routine clean-up tasks. It helps ensure user data remains accurate and up to date, supporting more efficient and reliable reporting.

This message is associated with Microsoft 365 Roadmap ID 503148.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: Admins managing Microsoft Viva Glint

What will happen:

• Admins will be able to delete custom user attributes directly in the Viva Glint platform.
• This feature reduces dependency on support for routine data maintenance.
• It enables cleaner, more accurate datasets, improving reporting and analytics.
• There is no impact to end-user experience.
• The feature will be available by default once rolled out.

[What you can do to prepare:]

• Review existing custom attributes and identify any that are no longer needed or incorrectly configured.
• Update internal processes to reflect that attribute deletion is now self-serve.
• Communicate this change to relevant stakeholders (such as HR, IT, analytics teams) to plan for any downstream impacts on reporting or integrations.

Learn more [to be updated closer to release]: Update attributes in Viva Glint | Microsoft Learn

[Compliance considerations:]

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

[Introduction:]

We’re rolling out a refreshed “See All” experience for the SharePoint News web part (News.aspx page), bringing a modernized layout, improved visual rhythm, and new AI-powered capabilities to help users engage with news more effectively.  A Microsoft 365 Copilot license is required to access the AI capabilities. 

This message is associated with Microsoft 365 Roadmap ID 499654.

[When this will happen:]

Targeted Release: Rollout will begin in early November 2025 and completed in late November 2025.

General Availability:

• Worldwide: Rollout will begin in mid-November 2025 and is expected to complete by mid-December 2025.
• GCC, GCCH and DoD: Rollout will begin in late November 2025 and is expected to complete by late December 2025.

[How this affects your organization:]

Who is affected: Users of SharePoint sites with the News web part enabled.

What will happen:

• When users click the “See all” button in the News web part, they will see a refreshed dynamic mosaic grid layout.
• The update enhances hierarchy, legibility, and editorial rhythm.
• Core interaction patterns remain unchanged.
• AI-powered capabilities will be available to users with a Microsoft 365 Copilot license.
• Some users may see the new experience before others in your organization.

[What you can do to prepare:]

• No admin action is required.
• The new experience will apply automatically when using the News web part.
• There is no impact to existing News web part functionality.
• If needed, communicate this change to your helpdesk or internal support teams.

Learn more: Use the News web part on a SharePoint page | Microsoft Support

[Compliance considerations:]