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

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

You can now switch between accounts on the Copilot chat tab on iOS and Android. Simply swipe left to open the left-navigation and select from the list of supported accounts.

This message is associated with Microsoft 365 Roadmap ID 490213

[When this will happen:]

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

[How this will affect your organization:]

Currently, users are only able to access the Copilot Chat tab with their default account or privacy, even if they have other accounts that support Copilot. With account-switching on iOS and Android, users will be able to access Copilot Chat from other accounts that support Copilot, enabling them to access their chat history and graph data associated with those accounts.

iOS:

Android:

[What you need to do to prepare:]

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

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

Introduction

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

When this will happen

General Availability (Worldwide): We will begin rolling out this change in mid-September 2025 and expect the rollout to continue in the coming few months. We will share an update on the final GA date once that becomes available.

How this affects your organization

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

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

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

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

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

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

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

 What you can do to prepare

No admin action is required. However, we recommend:

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

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

[Introduction]

Microsoft is introducing new customization options for Microsoft 365 profile cards to help organizations enrich user profiles with relevant business information. This update enables the addition of properties such as Role, Division, Employee ID, Employee Number, and Cost Center, sourced from Microsoft Entra ID or external HR systems via Microsoft Graph connectors.

This update is associated with Microsoft 365 Roadmap ID 503111.

[When this will happen:]

[How this affects your organization:]

• Who is affected:
  • Admins managing Microsoft 365 user profiles and organizations using Outlook Web, New Outlook for Windows, Microsoft 365 Copilot app, or People Companion app.
  • Users who find the new properties once they are enabled.
• What will happen:
  • You can now add the following properties to profile cards:
    • Role
    • Division
    • Employee ID
    • Employee Number
    • Cost Center

    Screenshot 1: Profile card with new properties added

    

• Properties can be sourced from:
  • External systems via Microsoft Graph connectors
  • Microsoft Entra ID
• Properties are hidden by default and must be enabled in the Microsoft 365 admin center. Path: Settings > Org settings > People settings > Profile card > Contact info.
  • Screenshot 2: Settings for enabling the properties in M365 admin center

    

• Once enabled, properties will appear in the Contact Information tab of profile cards.
• Changes may take up to 24 hours to reflect across profile cards.

[What you can do to prepare:]

• Review which properties you want to display on profile cards.
• Ensure these properties are available in Microsoft Entra ID or your external HR system.
• Configure visibility in the Microsoft 365 admin center.
• Refer to the Microsoft Learn documentation for setup guidance.

Coming soon:

• Support for direct ingestion from SAP SuccessFactors and Workday.
• Future support for custom properties from third-party systems.

[Compliance considerations:]

Updated November 20, 2025: We have updated the timeline. This post has also been updated to remind customers that this feature is default-on for Copilot Dashboard users with full company-level data access. The export output remains de-identified, with each user represented by a hashed ID. Please review and take any actions as appropriate for your organization. Thank you for your patience.

This MC post is associated with Roadmap ID 500872.

[Introduction:]

To support deeper analysis of Copilot adoption, Microsoft is introducing a new export capability in the Copilot Dashboard. This feature allows dashboard users with company-level access to download de-identified Copilot usage metrics, aggregated by user and week, from the past six months. Organizations can use this data to track adoption trends, optimize licensing, and support AI transformation strategies.

This feature requires at least 50 Microsoft 365 Copilot licenses and applies to the Viva Insights web app.

[When this will happen:]

• Public Preview: Begins in early December 2025 (previously late November 2025), completes by late December 2025.
• General Availability (Worldwide): Begins in early February 2026, completes by late February 2026.

[How this affects your organization:]

Who is affected:

Copilot Dashboard users with full company-level data access, including senior leaders (as identified in Entra ID), admin-assigned company-level users, delegates with company-level access, as well as global analysts and admins. 

Note: Group managers with data access limited to their own teams will not have access to this feature.

What will happen:

• Users will be able to export de-identified, row-level Copilot usage metrics from the dashboard.
• The dataset includes weekly, user-level metrics from the past six months.
• The export supports Copilot usage analysis across apps (such as Word, Excel, Teams), and includes two attributes: Organization, and Job function.
• Organizations can use the data to track usage patterns, generate insights to inform adoption strategies, optimize licensing, and measure ROI.
• The feature is enabled by default for eligible users.
• Admins can manage access via Viva Feature Access Management (VFAM) settings, under Module: Viva Insights; Feature: Copilot Metrics Export.
• No impact to user workflow unless accessed by eligible users.

Screenshot 1 – View of the new Microsoft Copilot dashboard: 

Screenshot 2 – Example of output: 

[What you can do to prepare:]

• Review the assignment of the Copilot dashboard users with full company-wide data access and adjust VFAM policies as needed.
• Communicate the upcoming feature to eligible users so they know what to expect.
• No admin setup is required to start using the export.
• Admins can disable the feature at the tenant or group level at any time using VFAM settings.

Learn more: 

Microsoft Viva Feature access management | Microsoft Learn

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

[Compliance considerations:]

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

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

[Introduction]

The Workforce Insights agent is a Microsoft 365 Copilot agent designed to help leaders and their support staff make informed, strategic decisions about organizational structure, staffing, and skills. Starting December 8, 2025, the Workforce Insights agent will be available in Frontier and can be found in the Microsoft 365 Copilot agent store. Additional features will roll out over the following month.

The Frontier program provides customers early, hands-on access to experimental Microsoft 365 Copilot innovations in their own environment. Features designated as “Frontier” are previews intended for evaluation and feedback. Availability and capabilities may change as these features are still in development.

The Workforce Insights agent uses two main data sources:

• Organizational data: Enables insights into current staffing and team structure.
• People Skills data: Powers skill-based queries and helps users find colleagues with specific skills.

Customers with Microsoft 365 Copilot and the Microsoft 365 Copilot in Productivity Apps service plan will see the Workforce Insights (Frontier) available to deploy in the Copilot Control Center within the Microsoft 365 admin center.

[When this will happen:]

• Public Preview (Worldwide): Begins December 8th 2025 (previously mid-November) and completes by late March 2026.
• General Availability (Worldwide): Begins late March 2026 and completes by late December 2026.

[How this affects your organization:]

Who is affected: Organizations with Microsoft 365 Copilot licenses and the Microsoft 365 Copilot in Productivity Apps service plan.

What will happen:

• Workforce Insights (Frontier) will be available for deployment in the Microsoft 365 admin center.
• The agent can be installed by all M365 Copilot licensed users within Copilot or Teams.
• Requires at least 50 Copilot licenses for full functionality.
• Users will be able to:
  • Understand current team staffing.
  • Access guidance and best practices for workforce planning.
  • Identify skills and receive recommendations on organizational structure.
  • Find team members and filter by attributes such as level, location, and title.

[What you can do to prepare:]

You can manage the deployment of the Workforce Insights agent using the following controls:

• Deploy the agent: Install on behalf of users by accepting Microsoft Entra permissions.
• Restrict access: Limit availability to specific users or groups.
• Remove/block the agent: Completely block or remove from inventory if needed.
• Set up prerequisites:
  • Organizational data can be uploaded or refreshed using the Organizational Data in Microsoft 365 service. As an Organizational Data admin, you can upload public attributes and customer attributes that will be powering the Workforce Insights agent
  • People Skills needs to be set up in your tenant as a pre-requisite for the Workforce Insights agent to respond to prompts that require skills data. Review setup documentation: Overview of People Skills | Microsoft Learn.
  • Users can request delegate access from managers via the Workforce Insights Manage data access page. Starting December 8, 2025, if you would like to disable the ability for the user to assign delegates you can control access to this feature in M365 using PowerShell with the module name WorkforceInsights.
  • Licensing: Ensure at least 50 Copilot licenses are active.

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

[Compliance considerations:]

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

Expected in mid-February 2026, as part of our modernization efforts, we are updating the Intune Data Warehouse with a new architecture to enhance scalability, performance, and align with the reporting infrastructure. The Intune Data Warehouse provides structured access to historical Intune data through an OData API, enabling you to build custom reports and dashboards using tools like Power BI and Excel. This update includes several key changes to be aware of:

• Historical data reset: Once updated, the data will be reset and there will only be approximately 30 days of data.
• Updated licensing definition: The “IntuneLicensed” property will now include all forms of Intune licensing and grace periods.
• Surrogate key refresh: Surrogate keys will be regenerated as part of the infrastructure update.

[How this will affect your organization:]

If your organization is using the Intune Data Warehouse you will need to be aware of this upcoming change. Additionally, if you are using the Intune Data Warehouse (beta) Power BI connector, support for this connector will be discontinued. A new connector will be available, requiring use of the OData feed link within the Intune admin center.

[What you need to do to prepare:]

• Ensure your reporting tools are configured to use the OData feed from the Intune admin center.
• If you are using the Intune Data Warehouse (beta) Power BI connector, transfer to the OData feed. For instructions refer to: Connect to the OData feed for the Intune Data Warehouse for your tenant
• Back up any historical data you wish to retain before this update.
• Review any dependencies on surrogate keys and prepare for key refreshes.
• Familiarize yourself with the updated licensing definitions and reporting behavior.

[Additional information:]

For more details on the data warehouse and alternative solutions, please refer to:

• Intune Data Warehouse API Endpoint
• Integrating Azure Data Factory and the Microsoft Intune Export API

[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 mid-December 2025, expected completion by mid-January 2026.

[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 introducing a private chat feature for organizers, co-organizers, and presenters in structured meetings and webinars in Microsoft Teams. This separate chat enhances collaboration by allowing key participants to communicate privately before, during, and after the event, without involving attendees. Additionally, we are unifying backroom chat behavior in town halls to ensure consistent functionality across all structured meetings. Currently, backroom chat behavior varies depending on whether streaming chat is enabled for town halls and whether the organizer has a Teams Premium license. This update removes that inconsistency.

This message is associated with Roadmap ID 392328 and applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, Teams for iOS/Android, MTR-W and MTR-A devices.

[When this will happen:]

• Targeted Release: Rollout begins in early January 2026 and is expected to complete by mid-January 2026.
• General Availability (Worldwide and GCC): Rollout begins in mid-February 2026 and is expected to complete by late February 2026.

[How this affects your organization:]

Who is affected: Admins managing Microsoft Teams meetings, webinars, and town halls.

What will happen:

• New private chat for organizers, co-organizers, and presenters: This chat is separate from attendee chat and is available before, during, and after the event.
• Unified backroom chat policy for town halls: The default setting will be ON for all town halls, regardless of streaming chat availability or license type.
• Existing town halls will adopt the new policy once meeting options are updated.
• If admins turn the backroom chat policy OFF, previously enabled town halls will lose access after update.
• Non-TPre town halls (those without a Teams Premium license) will have backroom chat ON by default after rollout and update.

Two potential impacts:

• If an admin explicitly turns the new backroom chat policy OFF, any already-scheduled town hall that previously had backroom chat ON will lose access once the meeting options are updated.
• For non-TPre town halls where backroom chat was previously OFF, it will switch to ON by default after the rollout and a meeting options update.

[What you can do to prepare:]

• Review your Teams meeting policies and decide whether to enable private chat for organizers and presenters.
• Communicate this change to helpdesk staff and event organizers.
• Update internal documentation to reflect the new backroom chat behavior.
• If you want to disable backroom chat, adjust the policy in the Teams admin center.

[Compliance considerations:]

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

[Introduction:]

Based on your feedback, we’re introducing a new capability in the Service Health Dashboard (SHD) that allows admins to archive “Issues in your organization that require action” posts. You can archive issues for yourself or for your entire organization, giving you more control over how service health information is displayed.

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

Who is affected: Admins managing Service Health Dashboard in Microsoft 365 Admin Center.

What will happen: 

You can now archive issues in two ways:

• For yourself:
  • Moves the issue to the Issue history tab (visible only to you).
  • Other admins still see it in the Overview tab.
  • You can restore the issue if needed.
  • The issue still appears on the M365 Admin Center homepage.
• For your entire organization:
  • Moves the issue to the Issue history tab for all admins.
  • Other admins see that it was archived for the organization and the reason provided.
  • They can restore the issue if needed.
  • The issue is dismissed from the M365 Admin Center homepage.

Screenshot 1 – Archive an issue:

Screenshot 2 – Choose archive preferences:

Screenshot 3 – View archived issues in Issue history:

>

Screenshot 4 – Restore an archived issue:

Additional details:

• Archived issues remain in the Issue history tab for 7 or 14 days from the original publish date.
• Dismissing an issue on the M365 Admin Center homepage does not remove it from the Overview tab in the Service Health Dashboard. It will continue to appear in SHD unless archived.

Admin controls:

• Enabled by default for admins with Service Health Dashboard access.
• No toggle or policy in the Microsoft 365 admin center to disable archiving.
• Role-based access applies: Global Admins can archive issues.
• No additional configuration steps required.

[What you can do to prepare:]

No action is required.

Optional:

• Review your organization’s process for managing service health issues.
• Communicate this change to helpdesk or admin teams.
• Update internal documentation if you track SHD workflows.

[Compliance considerations:]

No compliance considerations identified. Review as appropriate for your organization.

[Introduction:]

Microsoft Edge for Business is introducing a “What’s New” webpage to inform and educate users about the latest features and enhancements in Edge and Microsoft 365 Copilot. After a major browser version update, this page will automatically open in a new tab the first-time users launch the updated browser. This one-time experience provides an overview of new capabilities, allowing users to explore and try out these features directly or simply close the tab and continue working as usual.

This message is associated with Microsoft 365 Roadmap ID 526798.

[When this will happen:]

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

[How this will affect your organization:]

• Who is affected: All users signed in with their Entra ID using Microsoft Edge for Business.
• What will happen:
  • After a major browser update, the “What’s New” page will open automatically in a new tab the first time the browser launches.
  • This feature will be on by default.
  • Admins can disable this experience using the Microsoft365CopilotUpdatePage policy, which will be available once the feature rolls out.

[What you need to do to prepare:]

No admin action is required before rollout. However, you may:

• Review your current configuration to determine the impact on your organization.
• Notify your users about this change.
• Update any relevant internal documentation.

[Compliance considerations:]

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

[Introduction]

We’re introducing a new way to collect files and metadata in SharePoint document libraries using modern file upload forms. This update enables library owners and editors to create custom forms—similar to Microsoft Lists forms—that can be shared internally to gather files and related information without exposing the full library. This simplifies scenarios like onboarding, campaign submissions, or invoice collection.

This message is associated with Roadmap ID 489834.

[When this will happen:]

General Availability (Worldwide, GCC, GCCH, DoD): We will begin rolling out late November 2025 and expect to complete by early January 2026.

[How this affects your organization:]

Who is affected:

• SharePoint document library owners and editors with edit permissions.
• Internal users submitting files via shared forms.

What will happen:

For file upload form creators:

• A new Forms button will appear in the command bar of document libraries and folders.
• Clicking Forms allows users to create and design a custom intake form using the library’s columns as fields.
• Form creators can show/hide fields, mark required info, and apply a theme using the library’s metadata schema.
• Files are stored in a folder associated with the form; storing files at the library root is not supported.
• Once ready, forms can be shared via link with anyone in the organization.
• Creators can stop accepting responses at any time and view/edit forms they’ve created from the Forms menu.
• External or guest sharing of forms is not supported.
• Document library forms respect existing sharing settings. If a site or library is configured to disallow shareable links to the organization, the Forms feature will not be available on that library (similar to Microsoft Lists forms).

For form respondents (contributors):

• Anyone in your organization with the form link can access and submit it.
• Respondents sign in with their organization credentials and see a web form to upload files and fill out metadata.
• Submissions can be made from any desktop or mobile browser.
• Submitters only see the form and do not see the library’s contents or other submissions.
• Once submitted, files and metadata are saved to the target folder in the library.
• Submitters cannot edit or view their submission unless they already have access to the library.
• Standard file upload methods (e.g., New, Upload, or drag-and-drop) remain unaffected. Users with direct access to the library can continue using these methods; forms provide an additional optional method for gathering files from others.

• No admin action is required to enable this feature—it will be on by default.
• Inform document library owners and editors about the new Forms capability.
• Update internal documentation to reflect this new file collection method.
• Review site and library sharing settings to ensure org-wide sharing is enabled if you plan to use this feature.
• If you want to hide the Forms button in specific libraries, use command bar customization via JSON formatting. Refer to: Command bar customization syntax reference.
• A Microsoft blog post with additional details will be published closer to rollout. We recommend checking the SharePoint Blog for updates.

Learn more: UX Updates, AI Actions & Forms in Document Libraries | Microsoft Community Hub

[Compliance considerations:]

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

[Introduction:]

We’ve improved the multilingual meeting experience in Microsoft Teams, focusing on the Interpreter agent to make it more seamless and intuitive. These updates help participants communicate more effectively in multilingual meetings.

• Automatic spoken language detection – Teams now automatically detects and updates the spoken language across Interpreter, live captions, and transcription—no manual setup required:

 

• “Preparing” status indicator – A new visual cue shows when the Interpreter is initializing, helping users know when it’s ready:

 

• Simplified settings – Interpreter settings now include clear explanations for each option, making setup easier and reducing confusion:

 

Note: When Interpreter is turned off, live captions and transcription still work, but automatic language updates won’t apply—so captions may become inaccurate if participants switch languages mid-meeting.

Important: Interpreter is only available for Microsoft 365 Copilot licensed users.

This message is associated with Microsoft 365 Roadmap ID 520389.

[When this will happen:]

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

[How this will affect your organization:]

• Who is affected: All users participating in multilingual meetings in Microsoft Teams.
• What will happen:
  • Users will experience automatic spoken language detection across Interpreter, captions, and transcription.
  • A new “Preparing” status indicator will appear when Interpreter initializes.
  • Interpreter settings will include clearer explanations for each option.
  • No impact to admins or tenant configurations.
  • Platform availability: Android, Desktop, iOS, Linux, and Mac

[What you need to do to prepare:]

• No action is required from admins. This update will automatically apply as part of the standard Teams client update.
• You may choose to inform users about these enhancements to improve their meeting experience.

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

[Compliance considerations:]

No compliance considerations identified, review as appropriate

We’re bringing the power of Microsoft 365 Copilot directly into your daily file experience in Windows. This new feature enables users to generate summaries of files and share them directly from the share dialog in File Explorer and the OneDrive activity center. This enhancement is designed to streamline collaboration and improve productivity by making it easier to provide context when sharing files.

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

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout begins in early January 2026 and is expected to complete by late January 2026.

• Who is affected: All users of OneDrive and File Explorer in Windows with Microsoft 365 Copilot enabled.
• What will happen:
  • Users will be able to summarize files and include the summary when sharing via File Explorer or OneDrive activity center:

   

  • The feature is enabled by default.
  • No admin configuration is required.

No admin action is required to enable this feature.

If your organization uses or plans to use Copilot, consider:

• Informing users about the new summary-sharing capability.
• Updating internal documentation to reflect this new functionality.
• Reviewing Microsoft Copilot licensing and availability details: Which Copilot is right for me or my organization? | Microsoft Learn

Introduction

Starting October 2027 and ending November 2027, we will retire the isAttestationEnforced and keyRestrictionsproperties from the existing fido2AuthenticationMethodConfiguration API schema. This change aligns with the latest update to the passkey policy API schema, which introduces support for granular group-based configurations with passkey profiles.

During the retirement period, isAttestationEnforced and keyRestrictions will remain in sync with their counterparts attestationEnforcement and keyRestrictions within the Default passkey profile.

When this will happen 

Retirement begins in mid-October 2027 and is expected to complete by early November 2027.

How this affects your organization:

You are receiving this message because our reporting indicates your organization may be using this feature.

Who is affected: Admins managing FIDO2 authentication configurations and any custom automations or third-party integrations using these properties.

What will happen

• isAttestationEnforced and keyRestrictions properties will be retired.
• New properties are available in the updated passkey policy API schema.
• Existing properties will sync with new ones during the transition period.
• Automations or integrations using retired properties will stop working after the change.

What you can do to prepare

• Review your current configuration.
• Update any custom automations and third-party integrations to support the new schema.
• Notify your admins and update internal documentation.

Screenshot – The read arrows indicate the properties to be retired:

Learn more: fido2AuthenticationMethodConfiguration resource type | Microsoft Graph | Microsoft Learn

Compliance considerations:

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

We’re introducing user-level (federated) connectors in Microsoft 365 Copilot, enabling users to securely connect external apps such as Notion, Canva, or Hubspot directly within Copilot experiences like Researcher. Unlike traditional indexed connectors, federated connectors use the Model Context Protocol (MCP) to access data in real time. This allows users to fetch and read information from connected sources using their own credentials, while maintaining admin-level visibility, control, and governance in the Microsoft 365 admin center.

This feature will be available on the web platform.

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

This message is associated with Microsoft 365 Roadmap ID 501585.

Public Preview: Rollout will begin by November 15, 2025.

• Who is affected: All tenants using Microsoft 365 Copilot with access to the Microsoft 365 admin center.
• What will happen:
  • End users will be able to connect to Microsoft-published federated connectors (such as Canva, Notion, Intercom) directly within Copilot experiences to search or fetch live data.
  • Admins will have visibility and control from the Copilot > Connectors section, where they can
    • View all default user-level connectors enabled by Microsoft.
    • Disable any connectors that are not relevant or compliant for their organization.
    • Use staged rollout to enable these connectors for a limited group of users
  • Admin can also create and manage custom user-level connectors for internal or specialized data sources using an MCP endpoint.

Screenshot 1 – Admin experience:

Screenshot 2 – User experience:

• Review the list of default connectors that will appear in your tenant under Copilot > Connectors > Your Connections.
• Ensure all available connectors align with your organization’s data and compliance policies. Disable any that do not meet requirements directly from the admin center.
• For custom connectors, configure your MCP endpoints with the required tools (search and fetch) and proper authentication (OAuth2).
• Communicate this change to helpdesk staff and update internal documentation as needed.

• This update makes quality improvements to the servicing stack, which is the component that installs Windows updates.
• This update addresses an issue where File Explorer sometimes didn’t respond to mouse clicks until you closed and reopened it.
• This update addresses an issue with extracting .tar files when file or folder names contain more than 34 commonly used Chinese characters.
• This update addresses an issue where the HideRecommendedSection policy didn’t work in Windows 11 Enterprise multi-session environments, such as Azure Virtual Desktop (AVD).

• Windows 11, version 23H2: KB5070312