2026 CW 10 Microsoft 365 Message Center changes

What will happen:

If you have not opted in to passkey profiles by your automatic enablement period, your tenant will be migrated to passkey profiles.

Your existing Passkey (FIDO2) configurations will be migrated into a Default passkey profile

New passkeyType property will be auto-populated

If enforce attestation is enabled, then device-bound allowed

If enforce attestation is disabled, then device-bound and synced allowed

Any existing key restrictions will remain intact

Any existing user targets will be assigned to the Default passkey profile

[Registration Campaign behavior (Microsoft-managed campaigns only)]

For tenants where synced passkeys are enabled, if your registration campaign is set to Microsoft-managed:

The targeted authentication method will be updated from Microsoft Authenticator to passkeys.

The default user targeting will be updated from voice call or text message users to all multifactor authentication (MFA) capable users.

The settings Limited number of snoozes and Days allowed to snooze will no longer be configurable. These will be set to allow unlimited snoozes with a one-day reminder cadence.

What will happen:

If you have not opted in to passkey profiles by your automatic enablement period, your tenant will be migrated to passkey profiles.

Your existing Passkey (FIDO2) configurations will be migrated into a Default passkey profile

New passkeyType property will be auto-populated

If enforce attestation is enabled, then device-bound allowed

If enforce attestation is disabled, then device-bound and synced allowed

Any existing key restrictions will remain intact

Any existing user targets will be assigned to the Default passkey profile

[Registration Campaign behavior (Microsoft-managed campaigns only)]

For tenants where synced passkeys are enabled, if your registration campaign is set to Microsoft-managed:

The targeted authentication method will be updated from Microsoft Authenticator to passkeys.

The default user targeting will be updated from voice call or text message users to all multifactor authentication (MFA) capable users.

The settings Limited number of snoozes and Days allowed to snooze will no longer be configurable. These will be set to allow unlimited snoozes with a one-day reminder cadence.

All Microsoft 365 tenants (commercial, government, sovereign).

All external users who access OneDrive or SharePoint files, folders, or sites.

What will happen

The EnableAzureB2BIntegration setting will no longer control external sharing behavior beginning May 2026.

SPO OTP authentication will retire beginning July 2026.

The option to disable Entra B2B integration will be removed.

Impact on external users

External users who already have an Entra B2B guest account in your directory:

No change in behavior.

External users without a B2B guest account:

Specific people links shared after changes rolled out to your tenant:

A guest account will be automatically created via the Entra B2B Invitation Manager.

Authentication will use Entra B2B (email OTP available if enabled).

Specific people links shared before changes rolled out to your tenant:

SPO OTP authentication continues until July 2026.

After July 2026, these users will receive access denied until a matching B2B guest account exists.

Restoring access after retirement

Admins can manually create a guest account for the external user at any time.

Alternatively, an internal user with permissions needs to share or re-share at least one file, folder, or site, which will automatically create the guest account and restore access to all previously shared content.

All Microsoft 365 tenants (commercial, government, sovereign).

All external users who access OneDrive or SharePoint files, folders, or sites.

What will happen

The EnableAzureADB2BIntegration setting will no longer control external sharing behavior beginning May 2026.

SPO OTP authentication will retire beginning July 2026.

The option to disable Entra B2B integration will be removed.

Impact on external users

External users who already have an Entra B2B guest account in your directory:

No change in behavior.

External users without a B2B guest account:

Specific people links shared after changes rolled out to your tenant:

A guest account will be automatically created via the Entra B2B Invitation Manager.

Authentication will use Entra B2B (email OTP available if enabled).

Specific people links shared before changes rolled out to your tenant:

SPO OTP authentication continues until July 2026.

After July 2026, these users will receive access denied until a matching B2B guest account exists.

Restoring access after retirement

Admins can manually create a guest account for the external user at any time.

Alternatively, an internal user with permissions needs to share or re-share at least one file, folder, or site, which will automatically create the guest account and restore access to all previously shared content.

More details will become available closer to the release date.

Microsoft Purview is launching a new Personalization page that will help users personalize their individual experience on Purview.

This message is associated with Microsoft 365 Roadmap ID 483884.

[When this will happen:]

Public Preview (Worldwide): 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.

Microsoft Purview is launching a new Personalization page that will help users personalize their individual experience on Purview.

This message is associated with Microsoft 365 Roadmap ID 483884.

[When this will happen:]

Public Preview (Worldwide): 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.

Introduction

Outlook Mobile for iOS and Android will soon support Data Loss Prevention (DLP) policy tips and enforcement. This update helps users avoid accidental data leaks by providing inline alerts or pop-ups when sensitive content is detected-based on admin-configured DLP rules. This enhancement brings DLP behavior in Outlook Mobile in line with Outlook for desktop and web, ensuring consistent compliance enforcement across platforms.

This message is associated with Microsoft 365 Roadmap ID 496146.

When this will happen

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

Introduction

Outlook Mobile for iOS and Android will soon support Data Loss Prevention (DLP) policy tips and enforcement. This update helps users avoid accidental data leaks by providing inline alerts or pop-ups when sensitive content is detected-based on admin-configured DLP rules. This enhancement brings DLP behavior in Outlook Mobile in line with Outlook for desktop and web, ensuring consistent compliance enforcement across platforms.

This message is associated with Microsoft 365 Roadmap ID 496146.

When this will happen

General Availability: We will start rolling out April 6, 2026.

We're introducing a new Account Manager experience in Outlook for Windows. This feature helps users better manage their Microsoft accounts by providing quick access to account details, displaying their profile picture, and enabling account switching (if permitted by your organization). This update aligns the experience with classic Outlook and enhances user productivity.

This message is associated with Microsoft 365 Roadmap ID 497546

When this will happen:

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

Targeted Release: Rollout will begin in early February 2026 (previously early December 2025) and is expected to complete by late February 2026 (previously late December 2025).

We're introducing a new Account Manager experience in Outlook for Windows. This feature helps users better manage their Microsoft accounts by providing quick access to account details, displaying their profile picture, and enabling account switching (if permitted by your organization). This update aligns the experience with classic Outlook and enhances user productivity.

This message is associated with Microsoft 365 Roadmap ID 497546

When this will happen:

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

Targeted Release: Rollout will begin in early February 2026 (previously early December 2025) and is expected to complete by late February 2026 (previously late December 2025).

Introduction

Microsoft Teams is introducing noise suppression for PSTN dial-in participants in Audio Conferences. This feature automatically reduces background noise-such as traffic or keyboard sounds-enhancing audio clarity for users joining meetings via phone.

This message is associated with Microsoft 365 Roadmap ID 496150

When this will happen

Targeted Release (Worldwide): Rollout begins in October 2025 and is expected to complete by late October 2025.

General Availability (Worldwide, GCC, GCC High, and DoD): Rollout begins late October 2025 and is expected to complete by late November 2025

Introduction

Microsoft Teams is introducing noise suppression for PSTN dial-in participants in Audio Conferences. This feature automatically reduces background noise-such as traffic or keyboard sounds-enhancing audio clarity for users joining meetings via phone.

This message is associated with Microsoft 365 Roadmap ID 496150

When this will happen

Targeted Release (Worldwide): Rollout begins in October 2025 and is expected to complete by late October 2025.

General Availability (Worldwide, GCC, GCC High, and DoD): Rollout begins late October 2025 and is expected to complete by end of March 2026 (previously late November)

Introduction

We're introducing a new feature in Viva Connections that helps users stay informed with SharePoint news. Starting with this rollout, users will receive a weekly notification in Microsoft Teams reminding them to catch up on SharePoint news articles they haven't read from the previous week. These articles will be accessible under the Unread pill in the News tab within Viva Connections.

This feature is associated with Microsoft 365 Roadmap ID 498323.

When this will happen

General Availability: We will begin rolling out mid-February 2026 and expect to complete by end of February 2026.

Introduction

We're introducing a new feature in Viva Connections that helps users stay informed with SharePoint news. Starting with this rollout, users will receive a weekly notification in Microsoft Teams reminding them to catch up on SharePoint news articles they haven't read from the previous week. These articles will be accessible under the Unread pill in the News tab within Viva Connections.

This feature is associated with Microsoft 365 Roadmap ID 498323.

When this will happen

General Availability: We will begin rolling out mid-March 2026 (previously mid-February) and expect to complete by end of March 2026 (previously end of February).

[Introduction]

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

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

This message is associated with RMID 500378.

[When this will happen:]

Targeted release: Rollout will begin in early December 2025.

General Availability (Worldwide): Rollout will begin by early February 2026 (previously mid-December 2025).

[Introduction]

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

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

This message is associated with RMID 500378.

[When this will happen:]

Targeted release: Rollout will begin in early December 2025.

General Availability (Worldwide): Rollout will begin by early February 2026 (previously mid-December 2025) and is expected to be completed by late March 2026.

We're introducing significant enhancements to the Meeting Troubleshooting experience in Teams admin center. These updates make it easier and faster for administrators to identify issues during meetings and calls, understand root causes, and take action with confidence.

This message is associated with Microsoft 365 Roadmap ID 526784.

[When this will happen:]

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

[Introduction]

We're introducing significant enhancements to the Meeting Troubleshooting experience in Teams admin center. These updates make it easier and faster for administrators to identify issues during meetings and calls, understand root causes, and take action with confidence.

This message is associated with Microsoft 365 Roadmap ID 526784.

[When this will happen:]

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

[Introduction]

We're excited to announce the rollout of a new built-in role-based access control (RBAC) role in the Microsoft Teams admin center called Teams External Collaboration Administrator. This role provides targeted administrative capabilities for managing external collaboration settings (Federation) in Teams, enabling organizations to delegate responsibilities securely without granting full Teams admin permissions.

[When this will happen:]

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

[Introduction]

We're excited to announce the rollout of a new built-in role-based access control (RBAC) role in the Microsoft Teams admin center called Teams External Collaboration Administrator. This role provides targeted administrative capabilities for managing external collaboration settings (Federation) in Teams, enabling organizations to delegate responsibilities securely without granting full Teams admin permissions.

[When this will happen:]

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

Starting in March 2026, Microsoft Entra ID will introduce passkey profiles and synced passkeys to General Availability (GA). This update allows administrators to opt in to a new passkey profiles experience that supports group-based passkey configurations and introduces a new passkeyType property.

The passkeyType property enables admins to configure:

Device-bound passkeys

Synced passkeys

Both

If a tenant does not opt in to passkey profiles during the initial rollout window, the new schema will be automatically enabled at the date range specified below. When this occurs:

Existing Passkey (FIDO2) authentication method configurations will be moved into a Default passkey profile.

The passkeyType value will be set based on the tenant's current attestation settings.

For tenants that have synced passkeys enabled, Microsoft-managed registration campaigns will update to target passkeys.

[When this will happen]

General Availability (Worldwide): Rollout begins in early March 2026 and is expected to complete by late March 2026.

Automatic enablement for tenants that have not yet opted in (Worldwide): Rollout begins in early April 2026 and is expected to complete by late May 2026.

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

Automatic enablement for tenants that have not yet opted in (GCC, GCC High, and DoD): Rollout begins in early June 2026 and is expected to complete by late June 2026.

[Introduction]

Starting in March 2026, Microsoft Entra ID will introduce passkey profiles and synced passkeys to General Availability (GA). This update allows administrators to opt in to a new passkey profiles experience that supports group-based passkey configurations and introduces a new passkeyType property.

Important: Only tenants that already have Passkeys (FIDO2) enabled are affected by this update.

The passkeyType property enables admins to configure:

Device-bound passkeys

Synced passkeys

Both

If your tenant already has Passkeys (FIDO2) enabled and you do not opt in to passkey profiles during the initial rollout window, your tenant will be automatically migrated to the passkey profiles schema at the date range specified below. When this occurs:

Existing Passkey (FIDO2) authentication method configurations will be moved into a Default passkey profile.

The passkeyType value will be set based on the tenant's current attestation settings.

For tenants that have synced passkeys enabled, Microsoft-managed registration campaigns will update to target passkeys.

No new authentication methods are enabled as part of this migration.

[When this will happen]

General Availability (Worldwide): Rollout begins in early March 2026 and is expected to complete by late March 2026.

Automatic migration for existing Passkeys (FIDO2) enabled tenants (Worldwide): Rollout begins in early April 2026 and is expected to complete by late May 2026.

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

Automatic migration for existing Passkeys (FIDO2) enabled tenants (GCC, GCC High, and DoD): Rollout begins in early June 2026 and is expected to complete by late June 2026.

[Introduction]

Microsoft is introducing a unified plus (+) menu to make it easier for users to add grounding, tools, and sources when prompting in Microsoft 365 Copilot. Grounding refers to the content users connect to Copilot-such as files, sites, or other organizational data-that helps improve response relevance. This update consolidates related actions into a single menu, improving discoverability and streamlining the workflow for adding entities or updating inputs. This simplified menu will be available for Copilot Chat users (without a Microsoft 365 Copilot license) and Microsoft 365 Copilot users (with a Microsoft 365 Copilot license).

Note: The Tools menu will be consolidated under the unified plus (+) menu and no longer exist as a separate menu in the prompt box after this change.

[When this will happen:]

General Availability (Worldwide): Rollout begins in late February 2026 and is expected to complete by mid‑March 2026.

[Introduction]

Microsoft is introducing a unified plus (+) menu to make it easier for users to add grounding, tools, and sources when prompting in Microsoft 365 Copilot. Grounding refers to the content users connect to Copilot-such as files, sites, or other organizational data-that helps improve response relevance. This update consolidates related actions into a single menu, improving discoverability and streamlining the workflow for adding entities or updating inputs. This simplified menu will be available for Copilot Chat users (without a Microsoft 365 Copilot license) and Microsoft 365 Copilot users (with a Microsoft 365 Copilot license).

Note: The Tools menu will be consolidated under the unified plus (+) menu and no longer exist as a separate menu in the prompt box after this change.

[When this will happen:]

General Availability (Worldwide): Rollout begins in early March 2026 (previously late February) and is expected to complete by mid-April 2026 (previously mid‑March).

Model Context Protocol (MCP) based agents in Microsoft 365 Copilot Chat will now be able to surface rich, interactive UI widgets directly within chat. This enhancement enables developers to deliver more engaging and structured agent interactions. Users will experience these widgets when interacting with agents that implement them, and admins will continue to manage these agents through the Microsoft 365 Admin Center.

Screenshot 1: Rich in-line widgets in Copilot

When this will happen:

Public Preview: Rollout will begin late February 2026 and is expected to complete by early March 2026.

Introduction

Model Context Protocol (MCP) based agents in Microsoft 365 Copilot Chat will now be able to surface rich, interactive UI widgets directly within chat. This enhancement enables developers to deliver more engaging and structured agent interactions. Users will experience these widgets when interacting with agents that implement them, and admins will continue to manage these agents through the Microsoft 365 Admin Center.

Screenshot 1: Rich in-line widgets in Copilot

When this will happen:

WW rollout will begin late February 2026 and is expected to complete by early March 2026.

Starting in mid‑February 2026, the Microsoft 365 apps for Mac suite installer will include a shim for the Microsoft 365 Copilot app. This change helps organizations more easily deploy the Microsoft 365 Copilot Mac app by enabling users to download the full application directly from the shim.

The Microsoft 365 Copilot Mac app brings AI assistance to macOS, helping users search, analyze, and create from a single, secure desktop experience.

[When this will happen]

General Availability (Worldwide): Rollout will begin in mid‑February 2026 and is expected to complete by mid‑March 2026.

[Introduction]

Starting in mid‑February 2026, the Microsoft 365 apps for Mac suite installer a shim for the Microsoft 365 Copilot app. This change helps organizations more easily deploy the Microsoft 365 Copilot Mac app by enabling users to download the full application directly from the shim.

The Microsoft 365 Copilot Mac app brings AI assistance to macOS, helping users search, analyze, and create from a single, secure desktop experience.

[When this will happen]

General Availability (Worldwide): Rollout will begin in mid‑February 2026 and is expected to complete by mid-May 2026 (previously mid‑March).

We are retiring SharePoint One‑Time Passcode (SPO OTP) authentication in OneDrive and SharePoint starting July 2026. Beginning in May 2026, new external sharing invitations and authentication will start using Microsoft Entra B2B instead of SPO OTP. This transition simplifies external collaboration, aligns authentication with Microsoft identity standards, and enables consistent guest lifecycle management, governance, and Conditional Access coverage across Microsoft 365.

[When this will happen]

May 2026: Invitation and authentication for new external sharing begins transitioning to Microsoft Entra B2B. Users who previously authenticated via SPO OTP will continue to have access to specific people links even without a B2B guest account yet.

July 2026: Retirement of SPO OTP authentication begins. External users without a guest account get access denied on previously shared specific people links. To restore access, a guest account must be created in Entra B2B, or an allowed user must share/re-share at least one file/folder/site.

Retirement is expected to complete by August 31, 2026.

[Introduction]

We are retiring SharePoint One‑Time Passcode (SPO OTP) authentication in OneDrive and SharePoint starting July 2026. Beginning in May 2026, new external sharing invitations and authentication will start using Microsoft Entra B2B instead of SPO OTP. This transition simplifies external collaboration, aligns authentication with Microsoft identity standards, and enables consistent guest lifecycle management, governance, and Conditional Access coverage across Microsoft 365.

[When this will happen]

May 2026: Invitation and authentication for new external sharing begins transitioning to Microsoft Entra B2B. Users who previously authenticated via SPO OTP will continue to have access to specific people links even without a B2B guest account yet.

July 2026: Retirement of SPO OTP authentication begins. External users without a guest account get access denied on previously shared specific people links. To restore access, a guest account must be created in Entra B2B, or an allowed user must share/re-share at least one file/folder/site.

Retirement is expected to complete by August 31, 2026.

Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond. With the continued investment in Power Automate as the universal solution to workflow, Microsoft is retiring SharePoint 2013 workflows.

[When this will happen:]

Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants.

Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants.

Since the release of SharePoint workflows, Microsoft has evolved workflow orchestration to not only encompass SharePoint, but all the productivity services you use with Microsoft 365 and beyond. With the continued investment in Power Automate as the universal solution to workflow, Microsoft is retiring SharePoint 2013 workflows.

[When this will happen:]

Starting April 2nd, 2024, SharePoint 2013 workflows will be turned off for any newly created tenants.

Starting April 2nd, 2026, Microsoft will remove the ability to run, or create and execute SharePoint 2013 workflows for existing tenants.

Since the first use of Azure Access Control Services (ACS) by SharePoint in 2013, Microsoft has evolved the authorization and authentication options for SharePoint Online via Microsoft Entra ID (a.k.a. Azure AD). Using Microsoft Entra ID as auth platform for your SharePoint Online customizations will provide your applications the most secure, compliant and future proof model. With our continued investment in Microsoft Entra ID, Microsoft is retiring the use of Azure ACS as auth platform for SharePoint Online.

[Key Points:]

Major: Retirement

Timeline:

Starting November 1st, 2024, new tenants will not be able use Azure ACS.

Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants.

Action: Review and assess impact

Since the first use of Azure Access Control Services (ACS) by SharePoint in 2013, Microsoft has evolved the authorization and authentication options for SharePoint Online via Microsoft Entra ID (a.k.a. Azure AD). Using Microsoft Entra ID as auth platform for your SharePoint Online customizations will provide your applications the most secure, compliant and future proof model. With our continued investment in Microsoft Entra ID, Microsoft is retiring the use of Azure ACS as auth platform for SharePoint Online.

[Key Points:]

Major: Retirement

Timeline:

Starting November 1st, 2024, new tenants will not be able use Azure ACS.

Starting April 2, 2026, Microsoft will remove the ability use SharePoint ACS for existing tenants.

Action: Review and assess impact

Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint extensibility using SharePoint Framework (SPFx) enabling you to write applications that can be used in Microsoft SharePoint, Viva Connections and Microsoft Teams. With our continued investment in SharePoint Framework, Microsoft is retiring SharePoint Add-Ins.

[Key Points:]

Major: Retirement

Timeline:

Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible.

Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog).

Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants.

Action: Review and assess impact

Since the release of SharePoint Add-Ins in 2013, Microsoft has evolved SharePoint extensibility using SharePoint Framework (SPFx) enabling you to write applications that can be used in Microsoft SharePoint, Viva Connections and Microsoft Teams. With our continued investment in SharePoint Framework, Microsoft is retiring SharePoint Add-Ins.

[Key Points:]

Major: Retirement

Timeline:

Starting July 1st, 2024, SharePoint Add-Ins cannot be installed from the public marketplace, also referred to as store by existing tenants. Installation from a private app catalog stays possible.

Starting November 1st, 2024, new tenants will not be able use SharePoint Add-Ins, regardless of their origin (public marketplace, private tenant catalog).

Starting April 2nd, 2026, Microsoft will remove the ability use SharePoint Add-Ins for existing tenants.

Action: Review and assess impact

Coming soon to Microsoft Purview | Data Loss Prevention: When an admin wants to enable user email notifications, policy tips also need to be enabled and vice versa. After this rollout, notifications and policy tips will be decoupled, and admins can configure the following rules to enable:

Only a user email notification

Only a policy tip

A user email notification and a policy tip

No policy tips or user email notifications

After this rollout, policy tips and user email notifications will align with the behavior currently available with Microsoft Exchange.

This message is associated with Microsoft 365 Roadmap ID 394279.

[When this will happen:]

Public Preview: We will begin rolling out February 20, 2026 (previously late January 2026) and expect to complete by late February 2026 (previously late July).

General Availability Worldwide: We will begin rolling out March 2026 (previously late March) and expect to complete in March 2026 (previously late April).

Coming soon to Microsoft Purview | Data Loss Prevention: When an admin wants to enable user email notifications, policy tips also need to be enabled and vice versa. After this rollout, notifications and policy tips will be decoupled, and admins can configure the following rules to enable:

Only a user email notification

Only a policy tip

A user email notification and a policy tip

No policy tips or user email notifications

After this rollout, policy tips and user email notifications will align with the behavior currently available with Microsoft Exchange.

This message is associated with Microsoft 365 Roadmap ID 394279.

[When this will happen:]

Public Preview: We will begin rolling out mid-April 2026 (previously February 20) and expect to complete by late April 2026 (previously late February).

General Availability Worldwide: We will begin rolling out mid-May 2026 (previously March) and expect to complete in late May 2026 (previously March).

After careful consideration and extensive review of usage data and feedback Microsoft has decided to retire the domain isolated web parts feature in the SharePoint Framework (SPFx).

[When will this happen:]

Starting April 2, 2025, domain isolated web parts will be turned off for any newly created tenants.

Starting April 2, 2026, Microsoft will remove the ability to use domain isolated web parts for existing tenants.

After careful consideration and extensive review of usage data and feedback Microsoft has decided to retire the domain isolated web parts feature in the SharePoint Framework (SPFx).

[When will this happen:]

Starting April 2, 2025, domain isolated web parts will be turned off for any newly created tenants.

Starting April 2, 2026, Microsoft will remove the ability to use domain isolated web parts for existing tenants.

Coming soon: Users will be able to automatically see their automapped calendars when toggling from classic Microsoft Outlook to new Outlook for Windows. This message applies to classic Outlook for Windows desktop and new Outlook for Windows desktop.

This message is associated with Microsoft 365 Roadmap ID 415168.

[When this will happen:]

Targeted Release: We will begin rolling out in early February 2026 (previously early January) and expect to complete by late February 2026 (previously late January).

General Availability: We will begin rolling out in early March 2026 (previously early February) and expect to complete by late March 2026 (previously late February).

Coming soon: Users will be able to automatically see their automapped calendars when toggling from classic Microsoft Outlook to new Outlook for Windows. This message applies to classic Outlook for Windows desktop and new Outlook for Windows desktop.

This message is associated with Microsoft 365 Roadmap ID 415168.

[When this will happen:]

Targeted Release: We will begin rolling out in mid-March 2026 (previously early February) and expect to complete by end of March 2026 (previously late February).

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

Manage retention and deletion workflows for user-owned Loop workspaces such as Copilot Pages and the Loop personal workspace when users leave the organization.

This message is associated with Microsoft 365 Roadmap ID 421612

[When this will happen:]

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

Ensure the Microsoft 365 Copilot shim app is not excluded during deployment.

Confirm that Microsoft AutoUpdate (MAU) is enabled on macOS devices.

Confirm that devices meet the minimum requirement of macOS 14.0 (Sonoma) or later.

Ensure network connectivity is available so the shim app can download the full app.

This guidance is applicable for all users, not specifically those who want to deploy the shim app separately.

Review: Deployment guide for Office for Mac | Microsoft 365 | Microsoft Learn.

[Compliance considerations]

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

https://learn.microsoft.com/microsoft-365-apps/mac/deployment-guide-for-office-for-mac

Ensure the Microsoft 365 Copilot shim app is not excluded during deployment.

Ensure that your organization does not use managed Microsoft AutoUpdate (MAU) configurations.

Confirm that Microsoft AutoUpdate (MAU) is enabled on macOS devices.

Confirm that devices meet the minimum requirement of macOS 14.0 (Sonoma) or later.

Ensure network connectivity is available so the shim app can download the full app.

This guidance is applicable for all users, not specifically those who want to deploy the shim app separately.

Review: Deployment guide for Office for Mac | Microsoft 365 | Microsoft Learn.

How can you exclude the shim app from suite installer package during deployment

Method 1 - While downloading the suite installer package

1. Click on customize on the installation type page.

2. Uncheck Microsoft 365 Copilot to remove the shim app

Method 2 - While using Configuration Profile or Mobile Device Management (MDM)

Apply the following preferences -

Category Details

Domain com.microsoft.m365copilot

Key InstallCopilot

Data Type Boolean

Possible values true (default)

false

Availability 16.106

Comments This preference must be implemented through a Configuration Profile/MDM to be effective. It doesn't work when using the defaults command.

More context - Set suite-wide preferences for Office for Mac - Microsoft 365 Apps | Microsoft Learn

[Compliance considerations]

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

https://learn.microsoft.com/microsoft-365-apps/mac/deployment-guide-for-office-for-mac

https://learn.microsoft.com/microsoft-365-apps/mac/preferences-office

https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=421612