Microsoft Roadmap, messagecenter and blogs updates from 13-12-2025

Updated December 11, 2025: No new updates on this feature rollout yet. We expect to share a status update by the end of January.

The My account portal will be replaced by a new modal dialog within the Microsoft 365 Copilot app (formerly Office.com) on web and desktop. The new modal will support end user self-installs that are currently available on the My account portal (Office, Project, Visio, and Skype for Business).

[When this will happen:]

Targeted Release: We will communicate via Message center when we are ready to proceed.

General Availability (Worldwide): We will communicate via Message center when we are ready to proceed.

[How this will affect your organization:]

End users will be able to download their apps by accessing the modal dialog in Apps > Install apps > Install Microsoft 365 apps in the Microsoft 365 Copilot web and desktop app. 

[What you need to do to prepare:]

If you allow users to self-install apps:

• Please remove direct links to the My account portal (https://portal.office.com/account) in your self-install communications. Instead, please refer your users to the official Microsoft documentation for installing Office (Download, install or reinstall Microsoft 365 or Office 2024 on PC or Mac). This article will be updated to describe the new self-installs experience when it is released.

If you do not allow users to install apps:

• You can continue to use the Microsoft 365 admin center installation options setting or the m365AppsInstallationOptions API to block self-installs. If you already configured these settings, users will still be blocked from installing apps in the new experience.

Blocking Microsoft Admin Portals using Conditional Access Policies will no longer block self-installs. If you have used this setting to block self-installations, you will need to use one of the settings listed above instead.

Updated December 12, 2025: We have updated the timeline below. Thank you for your patience.

To help you manage metered consumption costs for Microsoft 365 Copilot Chat, we will introduce a new Message consumption usage report in the Microsoft 365 admin center. The new report will give you visibility into billed messages associated with your Microsoft 365 Copilot pay-as-you-go billing policies and includes total messages consumed, cumulative and daily time series, and messages per user, per billing policy, per agent, and per agent-user pair. The new report will roll out in preview. During the preview stage, the report will display a maximum of 30 days of message consumption history. Usage information from prior to May 3, 2025, will not be available in the report.

This message refers to Microsoft Copilot in a pay-as-you-go model. A Microsoft Copilot license is not required.

This message is associated with Microsoft 365 Roadmap ID 490738.

[When this will happen:]

Public Preview: Available now.

General Availability (Worldwide): We will begin rolling out in March 2026 (previously late September 2025) and expect to complete by end of March 2026 (previously late September 2025).

[How this will affect your organization:]

After you have set up pay-as-you-go billing for Microsoft 365 Copilot, either in the Microsoft 365 admin center or the Microsoft Power Platform admin center, and you have enabled agent usage in your organization, you will see a new report including metrics for messages consumed at the levels of tenant, users, agents, and agent-user. To help you mitigate overspending, you will see alerts when users have consumed more than 2000 billed messages.

This new report will be on by default and will be available in the Microsoft admin center at Reporting > Usage > Microsoft 365 Copilot > Message consumption:

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify any admins that manage agents on the integrated apps page about this feature.

Learn more: Microsoft 365 reports in the admin center – Message consumption

Updated December 12, 2025: We have updated the timeline. Thank you for your patience.

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

This message is associated with Microsoft 365 Roadmap 497298.

When this will happen

General Availability (Worldwide): We will begin rollout in October 2025 (previously late September 2025) and expect to complete by end of January 2026 (previously end of November 2025).

How this affects your organization

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

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

What you can do to prepare

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

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

Compliance considerations

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

Updated December 12, 2025: We have updated the timeline. Thank you for your patience.

Introduction

We’re introducing a new way to quickly summarize email threads in Outlook using Copilot chat. With a single click, users can generate a summary of the current email conversation directly from the reading pane. This feature enhances productivity by helping users quickly understand long or complex threads.

This capability will be available to users with Copilot chat enabled—even if they don’t have a Microsoft 365 Copilot license—provided they have pinned Copilot chat to the navigation bar. It will be available in both Classic and New Outlook for Windows.

When this will happen

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

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

How this will affect your organization

• Users without a Microsoft 365 Copilot license who have Copilot chat and pinning enabled will see a new Summarize button in the reading pane. Selecting this button will open Copilot chat and generate a summary of the current email thread.
• This feature is on by default for eligible users and does not require additional configuration.
• Usage can be viewed in the Microsoft 365 admin center.
• Audit logging may apply if summaries are saved or shared.
• Data is processed according to Copilot chat’s privacy terms.

What you can do to prepare

Admins can manage access to the Summarize feature by controlling access to Copilot chat:

• Use policy settings and Entra ID group membership to manage access.
• Pin Copilot chat to the navigation bar to enable the feature.

Learn more: 

• Pin Microsoft 365 Copilot Chat to the navigation bar | Microsoft 365 Copilot | Microsoft Learn
• Microsoft 365 reports in the admin center – Microsoft 365 Copilot usage | Microsoft Learn
• Privacy and protections | Copilot | Microsoft Learn
• Entry point overview – (video) Summarize an email thread with Copilot in Outlook | Copilot in Outlook | Microsoft Support

Compliance considerations

Updated December 12, 2025: We have updated the timeline. Thank you for your patience. 

To ensure continued high-quality performance of the Read Aloud, Transcription, and Dictation features in Microsoft 365 Office apps, we’re upgrading the backend service that powers these capabilities. As a result, these features will no longer function on Office clients running versions earlier than 16.0.18827.20202 after September 2026.

We are extending the supporting period for customers to prepare and upgrade to the supported version. Here is the updated timeline:

• General Availability (Worldwide): End of September 2026 (previously end of January)
• General Availability (GCC, GCC High, DoD): End of November 2026 (previously end of March)

If your organization is using Microsoft 365 Office apps with version numbers lower than 16.0.18827.20202, users will lose access to Read Aloud, Transcription, and Dictation features after the dates listed above.
There is no change to the user experience for clients on supported versions.

To avoid service disruption, ensure that all Office clients are updated to version 16.0.18827.20202 or later before the applicable deadline.

You can learn more about these features using the following resources:

• Listen to your Word documents 
• Transcribe your recordings 
• Dictate your documents in Word 

Compliance considerations

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

Updated December 12, 2025: We have updated the timeline. Thank you for your patience.

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

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

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

Once available, the Copilot dashboard will include:

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

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

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

Updated December 12, 2025: We have updated the timeline. Thank you for your patience. 

To help you manage agent adoption for Microsoft 365 Copilot Chat, we are introducing a new usage report in the Microsoft 365 admin center. The report provides visibility into how users in your organization are actively using agents in Microsoft 365 Copilot Chat and includes metrics such as: 

• Total number of active agent users and active agents 
• Usage breakdown per user, per agent, and per user-agent pair 
• Segmentation by license state (licensed vs. unlicensed Microsoft 365 Copilot users) 
• Segmentation by agent creator type (i.e. agents built by your organization, Microsoft, or Microsoft partners) 

The new report is rolling out in preview and will be available under Reporting > Usage > Microsoft 365 Copilot > Agent. During the preview stage, the report will display a maximum of 30 days of history. In addition, usage information from prior to August 19 2025 will not be available in the report. This report only includes declarative agents. Usage data for SharePoint agents and Custom engine agents will be available in a future update.

This message is associated with Microsoft 365 Roadmap ID 497999

[When this will happen:]

Public Preview (Worldwide): Available now.

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

[How this will affect your organization:]

[What you need to do to prepare:]

Updated December 12, 2025: We have added documentation links. Thank you for your patience.

Agents in OneDrive lets you group files and folders together, so you can ask questions, get summaries, and find key details across your project—without having to reselect items each time. Agents are saved in your OneDrive and can be shared with your team, making collaboration and staying up to date easier. This new capability helps users work more efficiently by turning OneDrive into a workspace for AI-powered project assistance.

This message is associated with Microsoft 365 Roadmap ID 469503.

General Availability (Worldwide): Rollout will begin in mid-November 2025 and is expected to complete by end of January 2026 (previously late November 2025).

Who is affected: Users with a Microsoft 365 Copilot license assigned to either work or school accounts (Microsoft 365 commercial or education tenants). 

What will happen:

Users will see a new agent option in OneDrive.

How to use Agents in OneDrive:

• Create your Agent: When users first select the Copilot button in OneDrive or the +Create or upload button, a guided experience will introduce agents and walk users through how to create and use them. From there, users can create an agent from their OneDrive using the +Create or upload option and then select the Agent option (screenshot 1):

 

• Alternatively, users can select the files to include in an agent, then choose Create an agent from the Copilot toolbar dropdown menu (screenshot 2):

 

• Access your agent as a file in OneDrive (.agent extension), filter by file type “agent” (screenshot 3):

 

• Open the agent to ask questions and get answers from your documents.
• Edit or update your agent anytime to change its sources, name, or instructions (screenshot 4):

 

• Share your agent with your team to collaborate and keep everyone informed (screenshots 5 & 6):

 

No admin action is required at this time.

You may wish to:

• Communicate this change to helpdesk staff.
• Update internal documentation to reflect the new agent capabilities in OneDrive.
• Encourage users to explore agents to improve project efficiency using AI.
• Review documentation at the following links:
  • Get started with OneDrive agents
  • Create and use an agent in OneDrive
  • Find your agent files in OneDrive
  • Share an AI agent in OneDrive

Updated December 12, 2025: We have added additional content clarifying who is impacted by this feature. Thank you for your patience.

[Introduction]

Teams users in tenants with open collaboration policies have long been able to start a chat with anyone who has an email address. However, recipients without a Teams account were previously asked to sign up for one before being able to collaborate. We’re introducing a new capability in Microsoft Teams for certain tenants (see ‘Who is affected’ below) that allows these recipients to join the chat as a guest— no account needed, and as long as it is allowed by the tenant’s existing policy configuration.

This feature will be available across Windows, Mac, Web, iOS, and Android platforms.

This message is associated with Microsoft 365 Roadmap ID 513271.

[When this will happen:]

• Targeted Release: Rollout for users with the aforementioned licenses begun in early November 2025 and was completed in mid-November 2025
• General Availability (Worldwide): February 2026

[How this affects your organization:]

Who is affected:

This capability is currently available only to small and medium business customers enrolled in public preview with a Teams Essentials, Business Basic, Business Standard, or Business Premium license. It also only affects organizations with guest chat enabled and that do not limit guest collaboration to specific domains. Organizations without users enrolled in public preview or without users with these licenses may still see this post even if they are not affected.

What will happen for those who are affected:

• After Teams users start a chat with someone who is not on Teams, the recipient will receive an email inviting them to join the chat as a guest. Only Teams users in your organization can start the chat, as users without Teams accounts cannot initiate chats.
• Chats will remain within your organization’s boundary.
• This feature is enabled by default but will be governed by your organization’s Entra B2B Guest policies and Teams Admin Center Guest Access policies. It will not override any existing policy configurations.

[What you can do to prepare:]

• Update internal documentation to reflect this new capability.
• Inform helpdesk and support teams about the change.
• Review the documentation here: Chat with anyone not using Teams – Microsoft Teams | Microsoft Learn
• To disable the feature, set the UseB2BInvitesToAddExternalUsers attribute of TeamsMessagingPolicy to false. Set-CsTeamsMessagingPolicy documentation here.

[Compliance considerations:]

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

Updated December 11, 2025: We have updated the timeline. Thank you for your patience. 

You can now adjust the length of your presentation, the tone of your narrative, the style of your slides, and leverage AI-generated images when creating with Copilot. These enhancements are designed to give users more creative control and flexibility when building presentations, helping them tailor content to suit different audiences and contexts.

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

This message is associated with Microsoft 365 Roadmap ID 513430, 513422 and 513431.

General Availability (Worldwide): Rollout will begin December 15, 2025.

• Who is affected: All users with access to Copilot in Microsoft 365 on Desktop, Web and Mac platforms.
• What will happen:
  • Users will see new options to adjust presentation length, tone, and style:

   

   

  • Users can incorporate AI-generated images into presentations:

  

  • Features will be available by default.
  • No changes to existing admin policies are required.

No action is required. These improvements will roll out automatically.

Learn more: Create a new presentation with Copilot in PowerPoint | Copilot in PowerPoint | Copilot | Microsoft Support

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

Updated December 12, 2025: We have updated the document link. Thank you for your patience.

[Introduction]

We’re introducing a new pay-as-you-go (PAYG) experience in the Microsoft 365 Admin Center (MAC). This update provides a centralized way to manage metered services such as Microsoft 365 Backup and Copilot under the Billing node.

[When this will happen:]

General Availability:

• Available to new Microsoft 365 Backup and all Copilot customers starting December 15, 2025 (previously early December).
• Migration path for existing Backup customers will be announced later.

[How this affects your organization:]

Who is affected: Admins in Worldwide and GCC environments managing Microsoft 365 Backup and Copilot PAYG services.

What will happen:

• A new PAYG page will appear under the Billing node in MAC.
• Admins can create and manage billing policies directly in MAC.
• Services can be linked to billing policies, with support for departmental billing. Note: departmental billing for Backup customers will become available in Q1 2026.
• Budgets can be set, and notifications triggered when thresholds are met.
• Usage and spending can be viewed at the billing policy level.
• Subscriptions and resource groups can be created in MAC without navigating to Azure.
• PAYG setup for other services remains under Org Settings > PAYG until transitioned.
• Additional PAYG-enabled services will be added to the Billing node over time. Until then, the PAYG setup for other products (besides Backup) will continue to remain under Org Settings > PAYG.

[What you can do to prepare:]

No action is required.

Admins may decide to:

• Review the new PAYG page under Billing in MAC.
• Monitor announcements for migration timelines for existing Backup customers.
• Refer to Microsoft documentation for guidance on billing policies and budget notifications.

Learn more: Set up or disconnect pay-as-you-go billing for services in new billing node | Microsoft Learn (will be updated before rollout)

[Compliance considerations:]

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

Updated December 12, 2025: Thank you for the valuable feedback we’ve received. We are currently reassessing the rollout timelines to ensure alignment with your needs and operational requirements. You can expect a formal update from us by mid to late January 2026.

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

Updated rollout timing will be announced in 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.

Introduction

We’re updating the Public Preview of External Authentication Methods (EAM) to improve security, strengthen configuration validation, and prepare for General Availability planned for the end of March 2026. Tenants currently using EAM in Public Preview should review the changes below.

[When this will happen]

Registration enforcement begins December 8, 2025.

[How this affects your organization]

Who is affected: Tenants currently using External Authentication Methods (EAM) in Public Preview.

What will happen:

• Registration enforcement: Users must have an external authentication method registered to use EAM.
• In-line registration for new users:
• Existing users have been registered by Microsoft – which means there’s no action required.
• New users (any user joining your tenant after December 2, 2025) will be prompted during sign-in to complete in-line setup with your external provider.
• IT admins can register users on their behalf if needed.

[What you can do to prepare]

• Communicate to users that starting December 8, 2025, they may be prompted to configure an external method during sign-in if they don’t already have one.
• Review your external authentication method configurations to ensure they meet validation requirements.
• Update internal documentation, training materials, and helpdesk guidance.

Learn more:

Microsoft Entra multifactor authentication external method provider reference (Preview)

Manage an external authentication method in Microsoft Entra ID (Preview)

[Compliance considerations]

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

Updated December 12, 2025: We have updated the content. Thank you for your patience. 

Action Required: Trust the new DigiCert Certificate Authorities (CAs) for Microsoft Entra

Starting January 7, 2026, Microsoft Entra will migrate its DigiCert certificates from the G1 root CA to the G2 root CA. Clients that pin to the DigiCert G1 root or do not trust the DigiCert G2 root may experience authentication failures.

Certificate Authorities (CAs) issue digital certificates that establish trust for secure communications. A root CA is the top-level certificate in a trust chain. DigiCert Global Root G1 is the current root CA used by Microsoft Entra services. DigiCert Global Root G2 is the newer root CA that Microsoft is migrating to for improved security and compliance. If your systems do not trust the G2 root, authentication and secure connections to Microsoft Entra services will fail.

Why you’re receiving this message:

Our reporting indicates that one or more users in your organization may be using Microsoft Entra ID.

January 7, 2026.

• Who is affected: Organizations using Microsoft Entra ID services.
• What will happen:
  • If DigiCert G2 certificates are not trusted, authentication failures will occur when accessing Microsoft Entra services.
  • Impacted domains include:
    • login.live.com
    • login.windows.net
    • autologon.microsoftazuread-sso.com
    • graph.windows.net
    • Note: The login.microsoftonline.com domain has already been migrated to the DigiCert G2 root in Feb 2025. Customers using this domain will not be impacted, as their client systems already trust DigiCert G2.

• Trust all Root and Subordinate CAs listed in the Azure Certificate Authority details documentation.
• Ensure you trust the “DigiCert Global Root G2” root and its subordinate CAs (documented since September 2025).
• Remove any client-side pinning to the DigiCert Global Root CA root certificate.
• Update your settings now to avoid service disruption.

• For details about DigiCert certificates, refer to DigiCert documentation.
• For guidance on issuer/certificate pinning, see Azure documentation.
• Get answers from community experts in Microsoft Q&A.
• If you have a support plan and need technical help, create a support request.

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

• Unified Management: Streamlined experience for creating and managing environment settings.
• Role-Based Access: Available to system administrators and system customizers by default with options to grant additional roles.
• Preserves Extensions: Any existing extensions from Advanced Settings are retained and displayed in the new app.

[Introduction]

We’re introducing version storage management for video and audio files in SharePoint Online. This new capability allows admins to define and automate version expiration policies for large media files, helping reduce storage consumption, prevent version sprawl, and maintain consistent governance across sites and libraries.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-December 2025 and is expected to complete by mid-January 2026.

[How this affects your organization:]

Who is affected: Admins managing SharePoint Online sites and libraries that store audio or video files.

What will happen:

• Admins can apply file-type-specific version policies for audio and video files.
• Capabilities include:
  • Setting maximum retained versions.
  • Defining expiration periods.
  • Enabling auto-trim behaviors.
• PowerShell support includes:
  • Tenant, site, and library-level overrides.
  • Syncing policies across existing libraries.
  • Trimming existing versions to reclaim storage.
• Requires SharePoint Online Management Shell 16.0.26712.12000 or later.
• Policies apply forward unless libraries are manually synced; trimming jobs can delete older versions.

[What you can do to prepare:]

• Install the latest SharePoint Online Management PowerShell.
• Review media-heavy sites and plan version policies.
• Test cmdlets in non-production:
  • Tenant‑Level Controls
  • Set-SPOTenant (new parameter: FileTypesForVersionExpiration, RemoveVersionExpirationFileTypeOverride )
  • Get-SPOTenant (new property: VersionPolicyFileTypeOverride).
  • Site‑Level Contols
  • Set-SPOSite (new parameter: FileTypesForVersionExpiration, RemoveVersionExpirationFileTypeOverride ) 
  • Get-SPOSite (new property: VersionPolicyFileTypeOverride).
  • Document Library‑Level Controls
  • Set-SPOListVersionPolicy (new parameters: FileTypes, sync, RemoveVersionExpirationFileTypeOverride )
  • Get-SPOListVersionPolicy (new property: VersionPolicyFileTypeOverride).
  • Manage Version Policy Jobs
  • New-SPOSiteManageVersionPolicyJob
  • Get-SPOSiteManageVersionPolicyJobProgress
  • Remove-SPOSiteManageVersionPolicyJob
  • File Version Trimming Operations
  • New-SPOListFileVersionBatchDeleteJob (new parameter: TrimUseListPolicy)
• Decide whether to:
  • Override audio, video, or both.
  • Use default or custom expiration periods.
  • Sync all libraries or target specific file types.
• Communicate to site owners:
  • Old versions may be deleted.
  • Only new versions get expiration stamps unless trimming jobs run.

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

[Compliance considerations:]

The following compliance impacts may apply. Review as appropriate for your organization.

No new customer data is stored, and no changes to user-facing access or GDPR workflows.

We’re introducing a new Best Practice Configurations Monitoring Dashboard in the Teams admin center. This dashboard helps administrators monitor their tenant’s adherence to Microsoft-recommended best practices for an optimal collaboration experience in Teams meetings. The first focus area is Virtual Desktop Infrastructure (VDI) optimization, enabling admins to identify and remediate non-conformance quickly.

This message is associated with Microsoft 365 Roadmap ID 526781.

• General Availability (Worldwide): We will start rolling out in mid-January 2026 and expect to complete by late January 2026.
• General Availability (GCC): We will start rolling out in late January 2026 and expect to complete by early February 2026.

Who is affected: Teams administrators managing meeting experiences across M365 tenants.

What will happen:

• A new Best Practice Configurations Monitoring Dashboard will appear under the Meetings section in Teams admin center.
• The dashboard will:
  • Highlight non-conformance with best practices for VDI optimization.
  • Display subnet/IP details by city for impacted locations.
  • Provide exportable lists of users connected to VDI sessions without media optimization enabled.
• Supported roles for export functionality:
  • Teams Administrator
  • Teams Communications Administrator
  • Teams Communications Support Engineer
  • Teams Telephony Administrator
  • Teams Reader
  • Global Administrator
  • Global Reader
• Note: Export is not supported for admins scoped to an administrative unit.
• No changes to user workflows; this is an admin-only feature.

• No action is required before rollout; the feature will be enabled automatically.
• After rollout:
  • Visit Teams admin center > Meetings > Best Practice Configurations to review dashboard insights.
  • Use export functionality to plan targeted remediation for non-optimized VDI sessions.

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

We’re increasing flexibility in Microsoft Purview Insider Risk Management to help organizations better manage insider risk scenarios. Based on customer feedback, we are raising the variant limit per indicator and expanding detection group capacity, enabling more comprehensive policy configurations.

This message is associated with Microsoft 365 Roadmap ID 518291.

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

Who is affected: Admins managing Microsoft Purview Insider Risk Management policies.

What will happen:

• Variant limit per indicator increases from 3 to 10.
• Overall variant limit across all indicators increases to 100.
• Detection group capacity increases from 200 to 500 items.
• No changes to privacy controls: users remain pseudonymized by default, and role-based access controls and audit logs continue to apply.

• No action is required before rollout.
• If desired, review your Insider Risk Management policies to take advantage of expanded limits.

Learn more: Configure policy indicators in Insider Risk Management | Microsoft Learn

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

[Introduction]

Managers will soon be able to export the default sections from the Executive Summary report in Viva Glint directly into editable PowerPoint slides. This enhancement makes it easier and faster to share and customize reports outside Viva Glint compared to the previous method, which relied on static screenshots.

With this release, the new editable PowerPoint export feature will be available for Executive Summary reports, complementing the Team Summary report export capability introduced earlier.

This message is associated with Microsoft 365 Roadmap ID 499661.

[When this will happen:]

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

[How this affects your organization:]

Who is affected: Managers and users who access Viva Glint Executive Summary report.

What will happen:

• Native PowerPoint output: Executive Summary reports can now be exported as editable PowerPoint slides, allowing users to leverage built-in formatting and editing tools without needing to manipulate static images.
• Cleaner, customizable presentations: The new format improves layout and reduces whitespace, helping users create polished presentations more efficiently.
• Faster, more reliable export experience: The export process has been optimized for performance, reducing time-outs and improving reliability—especially for large reports with filters and visuals.
• Previous option remains available: The screenshot-based export option remains available for users who require custom PowerPoint template support, which is not yet supported in the new export feature.

[What you can do to prepare:]

• No admin action is required; the feature is on by default.
• Communicate this change to managers and report consumers who use Viva Glint.
• Update internal documentation if you reference report export options.

Learn more: How to Export Report to PowerPoint (will be updated before rollout)

[Compliance considerations:]

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

We’re enabling Microsoft 365 subscribers to use Copilot Chat when working in Microsoft Excel modern workbooks (.xlsx, .xlsb, .xlsm, .ods, .xltx, .xltm, and .xlam files) stored locally. This brings parity with workbooks stored in SharePoint or OneDrive, allowing users to query Copilot Chat regardless of storage location.

[When this will happen]

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

How this affects your organization:

Who is affected: All Microsoft 365 subscribers using Excel modern workbooks stored locally.

What will happen:

• Microsoft 365 subscribers will be able to query Copilot Chat when opening and working in locally stored Excel modern workbooks.
• This feature is enabled by default; no admin action is required.
• There is no impact to existing workflows for workbooks stored in SharePoint or OneDrive.

[What you can do to prepare]

All locally stored Modern Excel workbooks are blocked today from querying Copilot Chat. We are enabling M365 subscribers who open these workbooks and query Copilot Chat. See Manage Microsoft 365 Copilot Chat to manage that chat experience.

Learn more:

• Manage Microsoft 365 Copilot Chat | Microsoft Learn
• Overview of Microsoft 365 Copilot Chat | Microsoft Learn

[Compliance considerations]

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

[Introduction]

We’re enhancing SharePoint site analytics to include usage data from OneNote files (.one). This update provides a more complete view of site engagement by incorporating OneNote activity into metrics such as Unique viewers and site visits. Popular content reporting will also reflect heavily used OneNote files.

This message is associated with Roadmap ID 537285.

[When this will happen:]

General Availability (Worldwide): Rollout begins mid-January 2026 and is expected to complete by mid-February 2026.

[How this affects your organization:]

• Who is affected: Admins and users who monitor SharePoint site analytics.
• What will happen:
  • Expect an increase in reported site usage metrics, including unique viewers and site visits, as OneNote file activity will now be included.

  

  • The Popular content section in site analytics will display OneNote files if they are among the most accessed in the last 7 days.

  

  • No admin configuration changes are required; this update is enabled by default.

[What you can do to prepare:]

• Inform site admins and analytics stakeholders that site usage metrics may increase due to inclusion of OneNote activity.
• Update any internal documentation or reporting processes that reference SharePoint site analytics.
• No additional action or configuration is required.

Learn more: View usage data for your SharePoint site

[Compliance considerations:]

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

Updated December 12, 2025: We have updated the timeline. Thank you for your patience.

In new Outlook for Windows and web, when single-clicking on an empty time slot on the calendar surface, the quick compose pop-up will no longer appear. Instead, you will be able to create an appointment by typing directly in the time slot on the calendar grid, just as you can in classic Outlook for Windows. There will be no change to double-click behavior; the full compose form will still open as it does today.

This message is associated with Microsoft 365 Roadmap ID 406948.

[When this will happen:]

Targeted Release: We will begin rolling out early October 2025 (previously early April) and expect to complete by end of February 2026 (previously late October 2025).

General Availability (Worldwide): We will begin rolling out early November 2025 (previously early May) and expect to complete by end of March 2026 (previously late November 2025).

[How this will affect your organization:]

This may affect how users create appointments quickly on the calendar surface. We expect this to be a better experience, especially for those familiar with classic Outlook inline appointment creation.

This update is available by default.

[What you need to do to prepare:]

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

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

We’re excited to announce that Microsoft 365 Copilot usage metrics will soon be available in Microsoft Graph API v1.0, enabling organizations to programmatically access the usage data and build customized reporting and analytics for Copilot adoption.

What’s included in this release?

The metrics in Graph API v1.0 align with those in the Copilot for Microsoft 365 Usage Report in the Microsoft 365 admin center, including Tenant-level counts of enabled users and active users, Last activity date per user (Totals for each Microsoft 365 app and an overall grand total) 

Please note: A few recently added metrics in the usage report are not yet available in Graph API v1.0 but will be included in a future update.

A Microsoft 365 Copilot license is required to access the Microsoft 365 Copilot usage metrics through Graph API. 

This message is associated with Microsoft 365 Roadmap ID 396562 and with MC724835 Microsoft 365 admin center Usage report: Microsoft Copilot with Graph-grounded chat (Preview) (published March 2024).

[When this will happen:]

Public Preview: We will begin rolling out early September 2024 and expect to complete by mid-September 2024.

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

[How this will affect your organization:]

• Before this rollout, Microsoft 365 Copilot usage metrics were available only through the Graph API Beta for testing programmatically.
• After this rollout, admins and authorized roles can use Graph API v1.0 for production scenarios to create tailored reports and analytics for Microsoft 365 Copilot. The corresponding Beta endpoints have also been updated, and a new Beta URL is available for preview and testing.
• The earlier Beta version of the Graph API will be retired on March 31, 2026, and will no longer be accessible beyond this date.

[What you need to do to prepare:]

• This rollout will happen automatically by the specified date with no admin action required before the rollout. You may want to notify your admins about this release and update any relevant documentation.
• If your organization currently uses the earlier version of Graph API Beta version for accessing the Copilot usage metrics, update your codebase to point to Graph API v1.0 as soon as possible, preferably before the aforementioned date—to ensure uninterrupted functionality.
• Review documentation at the following link: CopilotReportRoot