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

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

 We’re introducing a new sign-in experience that enhances flexibility and accessibility for a limited number of users on Microsoft Teams for the web. This change introduces new sign-in options—Continue with Apple and Continue with Google—on the sign-in page (teams.microsoft.com or teams.com) for users routed through login.microsoftonline.com/common.

NOTE: These options are intended for consumer Microsoft accounts and may be visible to both consumer and enterprise users, depending on your authentication configuration.

[When this will happen:]

We will begin rolling out this private preview (Worldwide) in mid-November 2025 (previously mid-September) to a small number of Teams for the web users and expect to complete by mid-December 2025 (previously mid-October). We expect to expand this feature to other Microsoft apps later in 2025.

[How this will affect your organization:]

After this rollout:

• Users can sign in or sign up for a Microsoft account using Apple or Google credentials.
• Some users will be prompted to confirm whether they are using a personal or work/school account.
• Existing sign-in methods remain unchanged, including entering an email/username or using Sign-in options to access organizational accounts.
• Organizations using custom URLs (such as login.microsoftonline.com/contoso.com) will not be affected.
• In the case of Teams on the web, the custom URLs will be https://teams.microsoft.com?tenantId=<YOUR_DOMAIN_NAME> or https://teams.microsoft.com?tenantId=<YOUR_TENANT_ID>

Screenshots of the new experience:

1. Users can select Continue with Apple or Continue with Google to sign in or sign up for a consumer Microsoft account using an Apple or Google credential. This image shows the Google option:

2. A subset of users who click these options will see a screen that confirms whether they are using a personal or work/school account. In this image, the user has selected the work/school option:

3. Users can still enter their email/username at the top of the sign-in screen, and sign into a specific organization with Sign-in options:

[What you need to do to prepare:]

No action is required. This feature is only being added to login.microsoftonline.com/common. Users accessing login.microsoftonline.com with a custom URL will not see this feature.

You can show a custom URL for your organization by passing a domain hint to apply company branding at the initial sign-in screen. Custom URLs for Teams on the web will be https://teams.microsoft.com?tenantId=<YOUR_DOMAIN_NAME> or https://teams.microsoft.com?tenantId=<YOUR_TENANT_ID>.

Learn more

• Add company branding to your organization’s sign-in page – Microsoft Entra | Microsoft Learn
• Adding branded URLs to authentication with Microsoft Entra External ID Custom URL Domains | Microsoft Entra Identity Platform

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

 What and Why

We’re introducing a new capability that allows users with a Microsoft 365 Copilot license to scope and control Copilot Chat responses by selecting specific content sources. This enhancement is designed to improve the relevance and accuracy of Copilot responses by limiting them to user-selected sources, aligning with customer feedback for more transparent and customizable AI interactions.

This message is associated with Microsoft 365 Roadmap ID 496596

Rollout Schedule

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

Impact on Your Organization

• Who is affected:
  • Users with a Microsoft 365 Copilot license.
• What will happen:
  • Users will see a new option to select content sources when using Copilot Chat.
  • Copilot responses will be scoped only to the selected sources, improving control and precision.
  • This feature will follow a standard rollout and is enabled by default.
  • There is no impact to admin settings or policies.
  • No changes to existing Copilot behavior unless users actively select sources.

Action Required/Recommendations

• No admin action is required.
• This feature does not impact admin controls or require configuration.
• We recommend:
  • Informing helpdesk staff of this new user-facing capability.
  • Updating internal documentation if you provide guidance on Copilot usage.

Compliance Considerations

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

Updated September 25, 2025: After further review, we will not be rolling this out to GCC, GCCHihg, DoD, USSec, USNat during the timeline outlined below. We will communicate via Message center when we are ready to proceed. Thank you for your patience.

Updated September 11, 2025: This release is intended solely for commercial cloud environments. Separate release timelines will be communicated for special clouds and on-premises segments in dedicated posts.

We’re introducing the new Microsoft Teams calendar experience, designed to unify and enhance productivity across Microsoft 365. This calendar integrates familiar features with innovations like Microsoft Copilot and Microsoft Places, enabling seamless collaboration from anywhere. It works consistently across Teams, the new Outlook for Windows, Outlook on the web, and Places. As part of this update, the legacy calendar experience will be deprecated, and the toggle to switch between old and new calendars will be removed.

When this will happen

• Public Preview: Early November 2025 – Mid-November 2025
• Targeted Release: Early November 2025 – Mid-November 2025
• General Availability (Worldwide): Early November 2025 – Mid-November 20255
• General Availability (Gallatin, GCC, GCC High, DoD, USSec):  After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.
• General Availability (USNat):  After further review we have decided not to proceed with this change at this time. We apologize for any inconvenience.

Once this update is deployed, users accessing the Calendar app in Microsoft Teams will see the new calendar experience by default. The toggle to switch between the old and new calendar will be removed, and only the new Microsoft 365 calendar will be available. This change may impact users accustomed to the legacy calendar interface.

No admin action is required. We recommend informing your users about the upcoming change and updating any internal documentation or training materials that reference the legacy calendar experience.

For more information about the new calendar experience, visit the Microsoft Teams documentation.

Compliance considerations

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

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

Introduction

Organizers and co-organizers of Viva Engage events can now export event content from the past 28 days in a .csv file. This includes questions and discussions, along with metadata such as status, source, timestamps, upvotes, and reactions—enabling easier filtering, analysis, and sharing. The export option appears by default on the event page.

Screenshot – Export option on the event page:

The feature will be available across Android, iOS, Mac, Desktop, and Web platforms. 

This message is associated with Microsoft 365 Roadmap ID 493948.

When this will happen

General Availability (Worldwide): We will begin rolling out on September 29, 2025 (previously September 22) and expect to complete by October 4, 2025 (previously September 27).

How this affects your organization

Organizers and co-organizers will be able to download event posts in a .csv format directly from the event page. This file includes:

• Content
• Status
• Source
• Timestamps
• Upvotes
• Reactions

This feature is enabled by default. Network admins can disable it at the tenant level. If disabled, organizers will no longer see the export option.

What you can do to prepare

Admins can manage access to this feature by navigating to: Admin settings > Tenant settings > Content management.

No additional configuration is required unless you wish to disable the feature.

Compliance considerations

A copy of personal data (messages posted by participants in the event) is stored on event-organizer/co-organizer’s device.

Updated September 25, 2025: After further review, we will announce a revised GA date after we have had an opportunity to collect feedback from the public preview. Thank you for your patience.

Introduction

We’re introducing a new feature: M365 Copilot Chat adoption metrics in the Microsoft Copilot dashboard. This feature provides organizations with enhanced visibility into how users who are not licensed for Microsoft 365 Copilot are engaging with Copilot Chat. These insights include usage trends, retention and intensity metrics, app-level breakdowns, and filtering by organizational attributes—helping organizations better understand adoption patterns and tailor support strategies.

This feature will be available to tenants with at least 50 assigned Viva Insights licenses or 50 assigned Microsoft 365 Copilot licenses (includes Viva Insights service plan).

This message is associated with Microsoft 365 Roadmap ID 499899.

When this will happen

Public Preview: We will begin rolling out at the end of October 2025 and expect to complete by end of November 2025.

General availability (Worldwide): We will announce a revised GA date after we have had an opportunity to collect feedback from the public preview. Thank you for your patience.

How this affects your organization

Users with access to the Microsoft Copilot dashboard will see new analytics cards and visualizations focused on Microsoft 365 Copilot Chat adoption for unlicensed users. These insights will appear in the dashboard’s adoption tab and include:

• Usage trends over time: Track active users and adoption growth.
• Adoption by group: Compare usage across departments or roles.
• Usage intensity and retention: Understand recurring usage and engagement levels.
• App-level breakdowns: Identify which apps and entry points drive adoption.
• Filtering and drilldown: Segment data by organizational attributes to tailor change management strategies.

This feature will be on by default for existing dashboard users. No additional administrator action is required to enable it.

What you can do to prepare

Review the impact of this feature on your organization’s reporting and privacy practices. You may also want to update internal training and documentation to reflect the new insights available.

Starting in September 2025:

• A new administrator control will be available for Global administrators, Viva Insights administrators, and AI administrators to turn off this feature at the tenant level. To disable this feature, use Viva Feature Access Management (VFAM) in Microsoft admin center or PowerShell.
• These same roles will also be able to exclude specific users or groups from being included in aggregated insights using the updated exclusion list feature.

Administrators should read the communication regarding the detailed scope and availability of this exclusion feature here (Roadmap ID: 500161).

Administrators should review any existing exclusions, assess their impact, and take appropriate action to exclude or include additional users or groups as needed.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Viva Insights | Microsoft Viva | Microsoft Learn
• Control access to features in Microsoft 365 | Microsoft Viva | Microsoft Learn
• Copilot for all: Introducing Microsoft 365 Copilot Chat | Microsoft Blog
• Manage settings for the Microsoft Copilot Dashboard and Viva Insights web app | Viva Insights | Microsoft Viva | Microsoft Learn
• Microsoft 365 Copilot overview | Microsoft 365 Copilot | Microsoft 365 | Microsoft Learn

Compliance considerations

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

Introduction

Meetings should be more productive—not more work. The Facilitator agent is now generally available for Microsoft 365 Copilot-licensed users. This AI-powered agent helps keep meetings focused, organized, and action-oriented by surfacing agendas, tracking progress, and capturing key highlights in real time. It supports collaboration through a conversational interface and integrates with tools like Planner, Word, Loop, and Teams Rooms.

This rollout includes general availability for core meeting skills and public preview for task management and document creation capabilities.

This message applies to Teams for Windows desktop, Mac desktop, the web, iOS, Android, and Microsoft Teams Rooms (MTR) devices and is associated with Roadmap IDs 478611, 499891, and 500701.

• Preview: Began in March 2025 
• General availability: We will begin rolling out late September and expect to complete by early October.

Who is affected: Microsoft 365 users with Copilot licenses. Facilitator is included with a Microsoft 365 Copilot subscription license and subject to available capacity.

What will happen:

• Facilitator agent will be available for scheduled meetings and ad-hoc discussions
• The Facilitator option is available by default in the Teams meeting experience for licensed users, meaning it appears in the meeting interface if the app is allowed in your tenant. However, it is not added to meetings automatically—meeting organizers or participants must choose to enable it before or during each meeting.
• Facilitator is shipped as an app and is allowed by default, respecting existing app permission policies
• If the Facilitator app is allowed in your tenant, it will appear in the meeting UX automatically
• Users can enable Facilitator before or during meetings

Screenshot 1: Copilot License User can turn on Facilitator in meeting


Screenshot 2: Users can see messages from Facilitator and new agenda tracker on the meeting window



• Facilitator does not require recording and can be used with or without transcription
• Visual timeline markers to track topics and time, with reminders at midway and wrap-up
• Collaborative, real-time notes editable by all participants via the Notes tab
• AI-powered Q&A from meeting and web content
• Task tracking integrated with Planner
• Instant document drafting in Word or Loop
• Enhanced Teams Rooms experience with chat, notes, and timers
• Mobile capture of ad-hoc discussions and action items
• Licensed users can interact with the agent by mentioning it in the chat, for example “@Facilitator add these topics to the agenda…”
  What you can do to prepare:
• No admin action is required
• Notify Copilot-licensed users about Facilitator availability
• Update internal documentation as needed
• Review meeting options to configure Facilitator without transcription:
  • Set Allow Copilot to Only during the meeting in Meeting Options
• Public documentation will be available at launch

Updated September 25, 2025: We are updating from a 3-year data retention policy to an indefinite data retention period, as long as your tenant maintains a valid Microsoft Viva Pulse subscription.

[Introduction:]

We’re updating the data retention policy for Microsoft Viva Pulse to improve consistency and transparency in how customer content is stored. This change aligns with our commitment to data governance and ensures that Pulse data remains available for reporting and analysis as long as the subscription is active.

[When this will happen:]

• General Availability: Begins early October 2025
• Expected Completion: Mid-October 2025

[How this affects your organization:]

Who is affected: All Microsoft 365 tenants using Viva Pulse

What will happen:

• Viva Pulse templates (research-backed and custom) are stored in Azure Cosmos DB based on tenant location (West US or EU).
• These templates will be retained indefinitely while the tenant maintains an active Pulse subscription or until the tenant deletes the data.
• Prior to September 1, 2025, Pulse instances were stored in Microsoft Forms. Forms data will continue to be retained indefinitely if the Pulse request met the minimum response threshold for report generation. If the Pulse request closed without meeting the threshold, Forms data was deleted immediately.

[What you can do to prepare:]

• No action is required from your organization at this time.
• This change does not alter user workflows or admin experiences.
• Learn more: Data residency for Viva Pulse | Viva Pulse | Microsoft Viva | Microsoft Learn

[Compliance considerations:]

To support compliance with the GB18030 standard—a mandatory Chinese government character encoding standard that ensures software can correctly display and process all Chinese characters—OneDrive is undergoing updates that temporarily affect the folder sync selection experience for users with the zh-CN language setting. During this time, the Choose folders sync dialog may be unavailable or fail to render correctly.

General Availability:

The folder selection dialog will be unavailable starting September 29, 2025, and is expected to be restored in late October 2025.

[How this affects your organization:]

Who is affected: Users who have selected zh-CN as their operating system language.

What will happen:

• The Choose folders sync dialog in OneDrive will be temporarily unavailable or may not render correctly.
• This may impact workflows that rely on selective sync, particularly in environments with limited storage or bandwidth.
• No other OneDrive functionality is affected.

• Advise affected users to temporarily switch their operating system language to one of the following:
  • zh-HK – Traditional Chinese (Hong Kong)
  • zh-TW – Traditional Chinese (Taiwan)
  • Or any other language setting except zh-CN
• After changing the language, restart OneDrive to restore access to the folder selection dialog.
• Once the updates are complete, users can revert to zh-CN without issue.
• Communicate this workaround to helpdesk and support teams.
• Update internal documentation if you reference selective sync workflows.

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

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:]

[Introduction:]

To support enhanced monitoring and governance, Microsoft Fabric is introducing a new tenant setting that allows admins to control whether user identifiers are included in OneLake diagnostic logs. This change aligns with customer feedback around privacy and compliance, giving organizations more flexibility in managing diagnostic data.

[When this will happen:]

• OneLake diagnostics will become generally available in mid-October 2025.
• The new tenant admin setting will be available starting October 28, 2025.

[How this affects your organization:]

Who is affected:

• Admins managing Microsoft Fabric and OneLake environments.
• Workspace Admins and Tenant Admins.

What will happen:

• Workspace Admins will be able to enable OneLake diagnostics to monitor data interactions:



• By default, diagnostic events will include End User Identifiable Information (EUII), such as User Principal Name (UPN) and IP address.
• A new tenant admin setting will be available to opt out of logging EUII.
• The setting will be enabled by default—EUII will be logged unless the toggle is disabled.

Example scenarios supported by OneLake diagnostics:

• Security investigation: Track which users accessed sensitive datasets, when, and from where. Helps identify unauthorized access attempts or unusual patterns.
• Performance troubleshooting: Diagnose latency or failure issues by correlating diagnostic events with user actions or system interactions.
• Usage analytics and optimization: Understand which datasets are most frequently accessed, by whom, and how often. Supports data governance and resource optimization.
• Integration monitoring: Monitor external systems interacting with OneLake (via APIs or connectors), ensuring integrations are functioning as expected and diagnosing issues when they arise.

[What you can do to prepare:]

• Review your organization’s privacy and compliance policies.
• Starting mid-October:
  • Workspace Admins can enable OneLake diagnostics (EUII will be redacted at this stage).
• By October 28:
  • Tenant Admins should review the new admin toggle in the Fabric Admin Portal.
  • If you wish to prevent EUII from being logged:
    • Disable the toggle in the Fabric Admin Portal.
• Communicate this change to your helpdesk and update internal documentation as needed.

We’re introducing Custom Age and Tenure Derivations in Microsoft Viva Glint to give admins greater control over how employee data is structured and reported. This enhancement allows organizations to tailor demographic groupings directly within the platform, improving reporting accuracy and reducing reliance on support teams.

This message is associated with Microsoft 365 Roadmap ID 500868.

When this will happen:

Global rollout will begin in mid-October 2025 and is expected to complete by mid-November 2025.

How this affects your organization:

Who is affected: Admins managing Viva Glint configurations and data uploads.

What will happen:

• Admins can define custom ranges (e.g., “30–34 years” or “1–2 years of tenure”).
• These ranges can be mapped to source fields like Hire Date or Birth Year.
• Derivations can be enabled or disabled as needed.
• Derived attributes will be automatically generated by Glint.
• Historical values will remain available even if a derivation is turned off.
• Disabled derived attributes will function as standard attributes.
• Configuration changes apply to both full and incremental uploads.

What you can do to prepare:

• Review current data files to ensure required source fields (e.g., Hire Date, Birth Year) are consistently included in future uploads.
• Avoid naming conflicts: Do not manually include attributes named “Tenure” or “Age Grouping” in your data files.
• Understand the impact of turning off a derivation:
  • The configuration will be removed.
  • Historical values will remain accessible.
• Plan for unified configuration: Changes will apply across all upload types.

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.

To help users avoid duplicate questions and find answers faster, Viva Engage in Teams for iOS will now surface related questions when a user starts typing a new one. This enhancement supports knowledge reuse and improves engagement efficiency. This feature is available to tenants with the Viva Engage Knowledge Service Plan, included in the Microsoft Viva Suite and Viva Employee Communications and Communities.

Screenshot: The Viva Engage app in Teams showing the Create a post window with an active question prompt and a suggestion to View related questions.

[When this will happen:]

Global rollout: Begins in late September 2025 and is expected to complete by early October 2025.

• Who is affected: Tenants with the Viva Engage Knowledge Service Plan using Teams for iOS.
• What will happen:
  • Users asking a question in Viva Engage via Teams for iOS will see related questions suggested in real time.
  • This feature is already available for other Viva Engage clients (e.g., web and desktop).
  • No admin configuration is required; the feature is enabled by default for eligible tenants.

• Update internal documentation to reflect this new experience in Teams for iOS.
• Inform your communications and support teams about the change.
• If you manage helpdesk or training materials, consider adding a note about this feature to reduce confusion and duplicate questions.

[Compliance considerations:]

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

[Introduction]

Outlook’s Events from email feature helps users stay organized by automatically adding reservations such as flights, hotels, rental cars, and deliveries to their calendars.  To improve reliability and ensure this feature continues to work smoothly, we strongly encourage all providers to adopt Schema.org markup in their transactional emails. This change aligns with industry standards and improves accuracy, consistency, and long-term support.

• Legacy extraction is fragile, and once templates fail, they cannot be fixed.
• We are receiving increasing reports of incorrect or missing events.
• It is technically impossible to make further improvements to the old stack.
• By January 2026, the old extraction stack will no longer be supported.

Screenshot of Settings > Calendar > Events from email

[When this will happen:]

Legacy extraction will be retired on January 31, 2026. After this date, only emails using Schema.org markup will be supported for automatic event extraction.

[How this affects your organization:]

Who is affected:

• Organizations whose users rely on Outlook’s Events from email feature.
• Partners and providers who send transactional emails (e.g., airlines, hotels, travel agencies, delivery services).

What will happen:

• Emails that rely on legacy extraction will stop generating events after January 2026.
• Emails using Schema.org markup will continue to generate calendar events automatically.
• Partners using Schema.org markup report up to 30% higher engagement and more reliable event extraction.

[What you can do to prepare:]

• Identify providers (e.g., airlines, hotels, travel agencies, and delivery partners) that send confirmation emails to your users.
• Work with those providers to adopt Schema.org markup for supported scenarios.
• If you’d like assistance onboarding a provider to schema.org, please reach out to [email protected] along with your provider details. 
• Communicate this change to helpdesk staff.

[Compliance considerations]

[Introduction:]

To support privacy and organizational control, Microsoft Teams is introducing a new admin setting that allows you to hide Teams call and meeting history from appearing in the native iOS dialer. This change is based on customer feedback and provides greater flexibility for managing user experience on iOS devices.

This message is associated with Microsoft 365 Roadmap ID 503106.

[When this will happen:]

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

[How this will affect your organization:]

Who is affected: Users who join Microsoft Teams meetings or make Teams calls using iPhones or iPads.

What will happen:

• Admins will have a new toggle in the Teams admin center (TAC) to hide Teams call history from the native iOS dialer.
• This feature is enabled by default; no configuration is required unless you wish to disable it.
• Existing device settings and policies remain unchanged.

Screenshot – View of new admin control to hide Teams call history in iOS native dialer:

[What you can do to prepare:]

No action is required at this time.

You may wish to:

• Review the new setting in TAC if you want to disable this feature.
• Update internal documentation if you provide guidance on iOS device setup for Teams.

[Compliance considerations:]

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

[Introduction]

We’re simplifying how organizations grant applications permission to send email on behalf of mailboxes. Today, customers must manually assign permissions to each individual mailbox using PowerShell, which is time-consuming and inefficient. With this new capability, admins can assign the SMTP.SendAsApp role to an app through App Role-Based Access Control (RBAC), enabling group-based or scoped access to mailboxes. This simplifies onboarding for SMTP clients using OAuth and provides a scalable, secure, and modern approach to managing mailbox access.

This message is associated with Microsoft 365 Roadmap ID 498356.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

• Admins managing SMTP AUTH clients using OAuth in Exchange Online.

What will happen:

• Admins can assign the SMTP.SendAsApp role to applications via App RBAC.
• This enables group-based or scoped access to mailboxes.
• Eliminates the need for per-mailbox permission assignments.
• Streamlines onboarding for SMTP clients using OAuth.
• No changes to end-user experience.

[What you can do to prepare:]

• Prepare to create security or distribution groups for mailboxes requiring access.
• Plan for migration from per-mailbox permissions to group-based RBAC assignments.
• Communicate this change to your helpdesk or support teams.
• Update internal documentation if you currently detail mailbox permission onboarding.
• Review onboarding documentation: Authenticate an IMAP, POP or SMTP connection using OAuth | Microsoft Exchange | Microsoft Learn (https://learn.microsoft.com/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth)
• Documentation will be updated November 1^st  

• This preview update includes improvements that were a part of update KB5065429 (released September 9, 2025).
• This update makes quality improvements to the servicing stack, which is the component that installs Windows updates.
• This update contains miscellaneous security improvements to internal Windows OS functionality.

• Windows 10, version 22H2: KB5066198