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

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

Introduction

We’re introducing a new integration between Microsoft Teams and Microsoft Defender for Office 365 that enables security admins to manage blocked external domains in Teams using the Tenant Allow/Block List (TABL) in the Microsoft Defender portal. This feature enhances security by allowing organizations to centrally manage domain blocks across Microsoft 365 services.

This capability is available to customers with Microsoft Defender for Office 365 Plan 1 or Plan 2 and Microsoft Teams.

This message is associated with Microsoft 365 Roadmap ID 492985.

When this will happen

Targeted Release: We will begin rolling out late August 2025 and expect to complete by early September 2025.

General Availability (Worldwide): This is now generally available.

How this affects your organization

Security admins, with permission from Teams admins, will be able to:

• Add, delete, and view blocked external domains in Microsoft Teams using the Microsoft Defender portal.
• Prevent incoming communications (chats, channels, meetings, and calls) from blocked domains.
• Automatically delete existing communications from users in blocked domains.
• Track actions taken to block domains in audit logs, supporting compliance monitoring and reporting.

View and manage blocked domains for Teams in the Microsoft Defender portal:

This change does not affect existing federation configurations or domain blocks set in the Teams admin center.

• Entry limit: Up to 4,000 blocked domains can be configured for Teams.
• Client impact: Applies to all Teams clients and the Defender XDR web portal.

What you can do to prepare

To enable this feature – 

• Ensure that external access in the Teams admin center is set to either:
  • Block only specific external domains, or
  • Allow all external domains
• Teams admins must enable the setting “Allow my security team to manage blocked domains” in the Teams admin center. This setting is off by default.

Enable security team access to manage blocked domains in the Teams admin center:

Learn more: Block domains in Microsoft Teams using the Tenant Allow/Block List | Microsoft Defender for Office 365 | Microsoft Defender | Microsoft Learn

Compliance considerations

Updated December 16, 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 December 16, 2025: We have updated the timeline. Thank you for your patience.

[Introduction]

We’re introducing a new productivity feature in Microsoft Teams: Open Channels in a New Window. This enhancement allows users to detach any channel from the main Teams client and view it in a separate window—supporting better multitasking and focus, especially in high-traffic or cross-functional collaboration scenarios.

This change is associated with Microsoft 365 Roadmap ID: 509110

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

• Who is affected: All users of Microsoft Teams desktop client (Windows and macOS).
• What will happen:
  • Users will find a new option to Pop out channel from the channel menu.

  • Screenshot 1: Entry point from left rail

    

    Screenshot 2: entry point from channel header

    

  • The channel will open in a separate window, allowing simultaneous viewing of multiple channels.
  • There are no changes to existing Teams functionality or policies.
  • Feature will be enabled by default for all tenants.

• No admin action is required.
• You may choose to:
  • Inform helpdesk and support staff of the new multitasking capability.
  • Update internal training or documentation if you provide Teams usage guidance.

[Compliance considerations:]

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

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

[Introduction]

We’re introducing a new capability in Copilot Pages that allows Copilot Chat to answer questions based on the contents of the currently open page. This enhancement supports more efficient workflows by enabling users to get contextual answers directly within the side-by-side Chat experience, without needing to switch views or search manually.

General Availability (Worldwide): We will begin rolling out in early October 2025 and expect to complete by early February 2026 (previously early November 2025).

• Who is affected: Users with access to Copilot in Microsoft 365 who use Copilot Pages and Copilot Chat in side-by-side mode.
• What will happen:
  • Users will be able to ask questions in Copilot Chat about the currently open page in Copilot Pages.
  
  • Copilot will respond using the content of the open page to provide contextual answers.
  • The feature will be ON by default for eligible tenants to configure.
  • Existing admin policies are respected; no policy changes are required.

• Communicate this change to helpdesk and support staff.
• Update internal documentation or training materials that reference Copilot Pages or Chat functionality.
• Review user guidance to ensure users understand how to use Copilot effectively in side-by-side mode.

Learn more:  Manage Copilot Pages and Copilot Notebooks in your organization | Microsoft Learn

No compliance considerations identified, all compliance capabilities will be the same as the Microsoft 365 Copilot Pages experience.

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

[Introduction:]

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

This message is associated with Microsoft 365 Roadmap ID 518643.

[When this will happen:]

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

[How this affects your organization:]

Who is affected:

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

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

[What you can do to prepare:]

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

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

[Compliance considerations:]

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

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

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

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

Who is affected:

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

What will happen:

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

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

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

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

Compliance considerations:

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

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

This message is associated with Microsoft 365 Roadmap ID 516568.

[When this will happen:]

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

[How this affects your organization:]

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

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

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

[What you can do to prepare:]

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

[Compliance considerations:]

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

[Introduction:]

We are introducing inline file upload protection for Microsoft Edge for Business to help prevent data leakage when users upload files to consumer generative AI (GenAI) apps in the browser. This complements the existing text upload protections available today for unmanaged GenAI apps and can be layered with Endpoint DLP protections. With this update, admins can detect and enforce inline protections on file uploads in Edge for Business. Policies can target file-specific conditions such as file size, file type, and sensitive information types, enabling organizations to audit or block activities for users on Intune-managed Windows devices.

This message is associated with Microsoft 365 Roadmap ID 518642.

[When this will happen:]

• Public Preview: Begins late November 2025 (previously mid-November); expected to complete by early December 2025.
• General Availability (Worldwide): Begins mid-January 2026 (previously early December 2025) (previously late November); expected to complete by end of January 2026 (previously mid-December 2025).

[How this affects your organization:]

• Who is affected: Admins managing Microsoft Purview DLP policies and Edge for Business on Intune-managed Windows devices.
• What will happen:
  • Admins can extend existing Purview collection and DLP policies to include file upload protection for unmanaged GenAI apps.
  • Inline protections are built directly into Edge for Business.
  • Automated behaviors will block use of unprotected browsers for users included in blocking policies.
  • Policies can be configured based on file size, type, and sensitivity.

[What you can do to prepare:]

• No action is required before rollout.
• Review your current collection and DLP policies.
• Update policies to include file upload conditions if needed.
• Inform your Security and Edge admins about this enhancement.

Learn more:

• Collection policy reference – Collection policies | Microsoft Purview | Microsoft Learn
• Data Loss Prevention for Cloud Apps in Edge for Business | Microsoft Purview | Microsoft Learn
• Data Loss Prevention policy reference | Microsoft Purview | Microsoft Learn
• Help prevent sharing via Microsoft Edge for Business to unmanaged AI apps from managed devices | Microsoft Purview | Microsoft Learn

[Compliance considerations:]

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

[Introduction]

We are updating the multi-select toolbar in Outlook Mobile. This change will allow users to customize the order and placement of toolbar actions when selecting multiple emails. Users can now Move to Other, Report Junk, Ignore, Pin, and Snooze multiple messages at once.

[When this will happen:]

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-January 2026 (previously mid-December 2025) and is expected to complete by mid-February 2026 (previously late January).

[How this affects your organization:]

• Who is affected: Users of Outlook Mobile.
• What will happen:
  • Users will be able to customize the multi-select toolbar.
  • No admin action is required.

  Screenshot 1: Shows the updated toolbar when selecting multiple messages. Tap the overflow menu (…) to find more actions.

  

  Screenshot 2: Tap Reorder to customize the order. Note that several actions shown are disabled because they can only be applied when only one message is selected.

  

  Screenshot 3: Users can customize the multi-select toolbar by dragging and dropping. 

  

[What you can do to prepare:]

• No admin action is required.

[Compliance considerations:]

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

Updated December 16, 2025: To ensure the best customer experience we have decided not to proceed with the rollout of this change at this time. The grace period is no longer ending. We apologize for any inconvenience this may have caused and thank you for your patience.

[Introduction]

The Loop app grace period is ending. This grace period was granted to organizations that participated in the Loop app Public Preview between March and November 2023, allowing all users—regardless of license—to create and manage Loop workspaces. To align with Microsoft 365 licensing requirements, this grace period will end in December 2025. After this change, only users with a qualifying Microsoft 365 plan will retain full workspace capabilities in the Loop app.

[When this will happen:]

This change is no longer planned.

[How this affects your organization:]

• Who is affected:
  • Organizations that participated in the Loop app Public Preview between March and November 2023.
  • Within those organizations, only users without a qualifying Microsoft 365 plan are affected by this change.
• What will happen:
  • Starting in mid-December 2025:
  • Users with a qualifying Microsoft 365 plan will continue to:
    • Create new Loop workspaces.
    • Add or remove members from Loop workspaces.
  • Users without a qualifying Microsoft 365 plan will:
    • No longer be able to create new Loop workspaces.
    • No longer be able to add or remove members from existing workspaces.
    • Continue to access and use previously created Loop components, pages, and workspaces.

[What you can do to prepare:]

• No action is required at this time. However, you may wish to:
• Review your organization’s Microsoft 365 licensing to ensure users who need to create or manage Loop workspaces have the appropriate plan.
• Communicate this change to your helpdesk or support staff.
• Update internal documentation if you provide guidance on Loop app usage.

Learn more: Loop access via Microsoft 365 subscriptions

[Compliance considerations:]

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

Updated December 16, 2025: We have made a minor correction. Thank you for your patience.

[Introduction]

Microsoft Purview is introducing Classifier Simulation Mode, the first phase of the broader Classifier Health Monitoring Platform. This new capability allows admins to test and validate custom classifiers on production data before publishing. Simulation Mode enables admins to optimize classifier logic before deployment, helping in reducing false positives, scanning latency, and noisy matches. Admins will access simulation controls and classifier health insights directly in the Microsoft Purview compliance portal, making it easier to monitor and improve classifier performance in one centralized location.

This message is associated with Roadmap ID 523201.

[When this will happen:]

• Targeted Release (Worldwide): Rollout begins early November 2025, completes by early December 2025.
• General Availability (Worldwide): Rollout begins late February 2026, completes by late March 2026.

[How this affects your organization:]

• Who is affected: Admins managing Microsoft Purview Information Protection and custom sensitive information types (SITs).
• What will happen:
  • By default, the feature will be available to all tenants.
  • Admins will see a new option to simulate a custom classifier before publishing.
  • Simulation is optional — admins can choose to simulate or publish directly.
  • Classifiers published without simulation will still be monitored for performance and flagged if unhealthy.
  • Classifier health insights will be available in the Microsoft Purview compliance portal, helping admins identify and remediate inefficient classifiers.
  • Inefficient classifiers may be automatically disabled to maintain system performance.

[What you can do to prepare:]

• Admins can begin using Simulation Mode once available; no onboarding or training is required.
• Once the feature is available:
  • Review classifier health insights in the compliance portal.
  • Monitor any SITs flagged as unhealthy and adjust logic as needed.
  • Consider simulating classifiers before publishing to reduce risk of false positives or performance issues.

[Compliance considerations:]

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

[Introduction]

To streamline workspace scheduling, users can now book a workspace directly from the location field when creating a calendar event. This enhancement simplifies the booking experience and aligns with user feedback requesting more intuitive workspace reservation options.

Screenshot: Open the location field to book a workspace through search or by selecting Browse workspaces

[When this will happen:]

• General Availability (Worldwide, GCC, GCC High, DoD): Rollout will begin in mid-January 2026 (previously mid-December 2025) and is expected to complete by mid-February 2026 (previously mid-January).

[How this affects your organization:]

• Who is affected: All users in tenants where workspace booking is enabled by IT admins and users have turned on workspace booking in their settings.
• What will happen:
• Users will see a new option to search or Browse Workspaces directly from the location field when creating an event.
• On iOS, the existing long-press calendar compose button method for booking workspaces will be retired.
• This feature is ON by default but only applies if workspace booking is enabled by both the admin and the user.
• Admins must have already configured workspace bookings for this feature to be available in their organization.

[What you can do to prepare:]

• No admin action is required.
• If workspace booking is not yet enabled in your organization, consider reviewing the feature and enabling it to take advantage of this streamlined experience.
• Communicate the upcoming change to helpdesk staff, especially regarding the retirement of the iOS long-press method.
• Update internal documentation if it references the previous booking method.

Learn more: Configure rooms and workspaces for Room Finder in Outlook

[Compliance considerations:]

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

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

[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 when Interpreter agent is enabled – 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

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

[Introduction]

Turn scanned PDF files into editable, searchable text using built-in Optical Character Recognition (OCR) in the OneDrive mobile app. This feature helps users reuse information, speed up document workflows, and make content easier to find.

[When this will happen:]

General Availability for Worldwide, GCC, and GCCH: Rollout begins early January 2026 (previously mid-December 2025) and is expected to complete by early February 2026 (previously late January).

[How this affects your organization:]

Who is affected: All users of OneDrive mobile apps on iOS and Android.

What will happen:

• Users can recognize text in scanned PDF files directly within the OneDrive mobile app.
• The feature is enabled by default.
• To use the feature:
1. Open the OneDrive mobile app.
2. Open the scanned PDF you want to make searchable.
3. Long-press the page and select Recognize Text (on iOS) or Recognize text (on Android).
4. After OCR completes, users will see the message: Text is now selectable.

[What you can do to prepare:]

• No action is required from admins.
• Some users may see this feature before others as rollout progresses.
• Communicate this change to helpdesk staff to assist users with the new functionality.
• Update internal documentation if you provide guidance on OneDrive mobile features.

Learn more: We will update this post with new documentation when it becomes available. 

[Compliance considerations:]

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

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

[Introduction]

Microsoft 365 Copilot declarative agents are upgrading to the GPT-5.1 model, which uses an “auto” architecture. The orchestrator will automatically select the best model for each scenario, either the fast “chat” model or the advanced reasoning model, based on the user prompt.

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

Who is affected: All tenants using Microsoft 365 Copilot declarative agents.

What will happen:

• Declarative agents will upgrade to GPT-5.1.
• The advanced reasoning model will be available for complex queries.
• No admin configuration changes are required.
• Feature will be enabled by default for all applicable tenants.

No action is required.

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

Updated December 16, 2025: We have updated the PowerShell example. Thank you for your patience. 

Exchange Online ActiveSync Device Support Update

We’re making a change to improve security and reliability in Exchange Online. Starting March 1, 2026, devices using Exchange ActiveSync (EAS) versions lower than 16.1 will no longer be able to connect to Exchange Online. EAS 16.1 was introduced in June 2016 and provides enhanced compatibility and security.

When this will happen:

This change begins taking effect on March 1, 2026.

How this affects your organization:

Who is affected: Organizations using mobile devices with native email apps to access Exchange Online mailboxes via EAS protocol. Apple devices added support for EAS 16.1 in iOS 10 and are unlikely to be affected. The Gmail app and Samsung Mail will have updated versions available before the deadline. For other apps you should contact your device or application vendor if they are using EAS versions lower than 16.1. 

What will happen:

• Devices running EAS versions lower than 16.1 will no longer connect to Exchange Online.
• Devices using Outlook Mobile are not impacted because they do not use EAS.
• This change applies only to Exchange Online, not Exchange Server.

What you can do to prepare:

• Verify that all mobile devices and applications are updated to EAS version 16.1 or higher before March 1, 2026.
• Admins can generate a report of devices using older EAS versions with the following PowerShell command:

Get-MobileDevice -ResultSize Unlimited | Where-Object {($_.ClientType -eq 'EAS' -or $_.ClientType -match 'ActiveSync') -and $_.ClientVersion -and ([version]$_.ClientVersion -lt [version]'16.1')} | Sort-Object UserDisplayName | Select-Object UserDisplayName, Identity, DeviceId, DeviceModel | Format-List

• Communicate this change to your helpdesk and end users and ask them to update if possible.
• Update internal documentation as needed.
• For assistance, contact your device or application vendor.
• Learn more: Exchange ActiveSync in Exchange Online

Compliance considerations:

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