Microsoft Roadmap, messagecenter and blogs updates from 03-03-2026

Updated March 2, 2026: Due to emerging changes, we are postponing this feature launch. We will communicate updated launch timelines as soon as they are available. We apologize for any inconvenience.

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.

[How this will affect your organization:]

The following features will be included in this initial rollout:

• Ability to pin or unpin solutions to the left navigation bar
• A new Personalization page where users can:
• Toggle visibility of the solution bar
• Choose to show solution walk-through on next sign in
• Export personalization data stored for the signed-in user
• Delete preferences one by one or all at once

The new Personalization page will be at Microsoft Purview > Settings (in top right corner) > Personalization:

On the new Personalization page, users will be able to hide or remove solution tiles and choose to show solution walk-throughs:

These changes will be available by default.

[What you need to do to prepare:]

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

Updated March 2, 2026: We have updated the timeline. Thank you for your patience.

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.

How this affects your organization

With this update, organizations using Microsoft Purview DLP policies will see those policies enforced in Outlook Mobile. When users attempt to send messages containing sensitive information—such as credit card numbers or national IDs—they will receive policy tips or blocking dialogs, depending on how the policy is configured.

This change enhances your organization’s data protection posture and supports regulatory compliance. If DLP policies are already in place for Outlook desktop or web, no additional configuration is required. The feature is on by default and requires no admin action to enable.

What you can do to prepare

What you can do to prepare

• Review existing DLP policies in Microsoft Purview to ensure they are scoped to include mobile clients.
• No new policies are required if DLP is already in use for Outlook desktop or web.
• No additional licensing is needed beyond what is already in place for Microsoft Purview DLP.

Find more on this topic: Learn about data loss prevention.

Compliance considerations

Updated March 2, 2025: We have updated the timeline. Thank you for your patience. 

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

How this affects your organization:

Once the rollout is complete, users will see the new Account Manager in the title bar of Outlook for Windows. Key capabilities include:

• Displaying the user’s profile picture, automatically synced from their Microsoft account.
• Providing access to the Microsoft account page, consistent with the experience in classic Outlook.
• Allowing users to add and manage accounts, if permitted by your organization’s policies.

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

What you can do to prepare:

No admin action is required. You may wish to inform your helpdesk and users about the new experience to reduce potential confusion.

Compliance considerations:

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

Updated March 2, 2026: We have updated the timeline. Thank you for your patience.

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.

• 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)

How this will affect your organization

Updated March 2, 2026: We have updated the timeline. Thank you for your patience. 

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

How this affects your organization

Once rolled out, users will receive a weekly notification in Microsoft Teams linking them to their unread SharePoint news in Viva Connections. This notification is enabled by default, but users can manage its visibility through their Teams notification settings.

What you can do to prepare

• No admin action is required. The rollout is automatic.
• Admins may wish to inform users about the new notification and how to manage it in Teams settings.

Compliance considerations

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

Updated March 2, 2026: We have updated the timeline. Thank you for your patience. 

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

[How this will affect your organization:]

Who is affected: Teams administrators managing meetings and calls.

What will happen:

• The list of In-progress and Completed meetings remains available for each user in Teams admin center > Manage users > {User} > Meetings and calls tab.

Screenshot 1: List of meetings for a user



• Existing functionalities are retained.
• New capabilities include:
  • Issues auto-identified and summarized: We surface likely root issues with your audio, video, and screen sharing experience (network, device, compute, etc.) and show how many people are affected, highlighted when you are viewing the meeting or the participant telemetry.

  Screenshot 2: Auto-identified issues

  

  • Easier drill-downs: Admins can navigate from the meeting view to a participant view with clearer device and network details and timeline‑based signal charts when real‑time data is available. Additionally, if the administrators are looking for more details, they can Export the participant telemetry for deeper analysis.

  Screenshot 3: Data for a meeting in progress

  

  Screenshot 4: A participant’s meeting details

  

  • Smarter search and filters: Search by meeting ID/code, filter by activity or issue type, and sort by key timestamps.
  • Integrated with M365 Copilot for Admins: Use Copilot in Teams admin center to troubleshoot meetings, analyze trends, find similar issues, or explain telemetry signals.

[What you can do to prepare:]

• No action is required.
• Changes will take effect automatically.
• Once rolled out, administrators can start using the new troubleshooting experience.
• We welcome your feedback.

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

[Compliance considerations:]

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

Updated March 2, 2026: We have updated the timeline. Thank you for your patience. 

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

[How this will affect your organization:]

• Who is affected: Admins who manage external collaboration settings in Microsoft Teams.
• What will happen:
  • A new RBAC role, Teams External Collaboration Administrator, will be available.
  • Key capabilities include:
    • Manage external access settings for federated domains.
    • Manage External Access Policies to allow or disallow external domains.
  • Role limitations:
    • No access to the Teams admin center portal; management is only through PowerShell.
    • Assignment to Administrative Units is not supported.
  • Global admins can assign or unassign this new RBAC role from the Microsoft Entra admin center or Microsoft 365 admin center.

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout.
To prepare:

• Notify your Global admins about the availability of this new role.
• Update internal documentation and training materials to reflect the new role and its capabilities.
• Learn more:
  • Use Microsoft Teams administrator roles to manage Teams – Microsoft Learn
  • Microsoft Entra built-in roles – Microsoft Learn

[Compliance considerations:]

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

Updated March 2, 2026: We have updated the content. Thank you for your patience.

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

[How this affects your organization]

Who is affected: Microsoft Entra ID tenants with Passkeys (FIDO2) enabled

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 you can do to prepare]

If you want a configuration different from the migration defaults, review the timeline above and opt in to passkey profiles before your tenant’s automatic enablement window begins. Then configure the Default passkey profile’s passkeyType to your preferred values.

We also recommend:

• Review your registration campaign configuration, especially if its set to Microsoft-managed. If you want synced passkeys enabled in your tenant but do not want registration campaign to target passkeys, you can: 
  • Switch the registration campaign state to Enabled and continue targeting Microsoft Authenticator, or 
  • Set the registration campaign state to Disabled.
• Update runbooks and help content so your help desk and end users understand any changes in passkey availability or behavior. 

Learn more:

• How to Enable Passkey (FIDO2) Profiles in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn
• How to Enable Synced Passkeys (FIDO2) in Microsoft Entra ID (preview) – Microsoft Entra ID | Microsoft Learn
• How to run a registration campaign to set up Microsoft Authenticator – Microsoft Entra ID | Microsoft Learn
• Synced passkeys FAQ – Microsoft Entra ID | Microsoft Learn

[Compliance considerations]

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

Updated March 2, 2026: We have updated the timeline. Thank you for your patience. 

[Introduction]

To help organizations analyze more recent Microsoft 365 Copilot usage trends, we’re adding a new export option in the Copilot dashboard. In addition to the existing user‑week export (see MC1173208), dashboard users with company‑level access will be able to export a subset of de‑identified Copilot usage metrics aggregated by user and day. This option includes 28 days of activity data and supports more granular, short‑term insights into Copilot adoption. Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary 

A minimum of 50 Microsoft 365 Copilot licenses is required. This feature applies to the Viva Insights web app.

This message is associated with the Microsoft 365 Roadmap ID 547749.

• Screenshot 1 – Export data button in Copilot dashboard:



• Screenshot 2 – Copilot dashboard export options:

  

[When this will happen]

• Public preview: Early April 2026 (previously early March) – Late April 2026 (previously late March)
• General availability (Worldwide): Early June 2026 (previously Early April) – Late June 2026 (previously late April)

[How this affects your organization]

Who is affected

This feature is available to Copilot dashboard users with full company-level data access, including:

• Senior leaders (as identified in Entra ID)
• Admin‑assigned company‑level users
• Delegates with company‑level access
• Global analysts and admins
• Group managers with access restricted to their own teams won’t have access to the user-day export.

What will happen

• A new export option will allow eligible users to download de-identified, row-level Copilot usage metrics aggregated by user and day, covering the most recent 28 days.
• Organizations can use this export to assess short-term usage patterns, support tactical adoption efforts, optimize licensing, and evaluate the impact of recent changes.
• Exported data will usually reflect copilot activity up to 3 days before the export date; actual timing may vary
• The export supports analysis across Copilot-enabled apps (for example, Word, Excel, Teams) and includes two additional attributes: Organization and Job function.
• Copilot activity metrics in exports run within 2 days of Copilot license assignments or removals may not reflect those license changes. Exports run after the 2‑day window will accurately reflect the impact of those license changes in copilot activity metrics under normal conditions.
• Data in previously exported files will not be automatically updated or modified after the export is generated.
• Access to the new user‑day export uses the same Viva Feature Access Management (VFAM) controls as the existing user‑week export (Viva Insights → Copilot Metrics Export). No new access controls are introduced. Existing VFAM settings for the Copilot dashboard export will remain in effect and apply to both day and week level export options after the day level export is released. Please read MC1173208 for more details.

[What you can do to prepare]

• Review and update VFAM settings for users with company‑wide access to the Copilot dashboard.
• Inform eligible users about this new export option.
• No additional admin configuration is required if export functionality is already enabled.
• Admins may disable the export feature for the tenant or specific groups at any time through VFAM.

Learn more:

• Connect to the Microsoft Copilot Dashboard for Microsoft 365 customers | Microsoft Learn
• Microsoft Viva Feature access management | Microsoft Learn

[Compliance considerations]

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

Updated March 2, 2026: We have updated the timeline and content. Thank you for your patience. 

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

[How this affects your organization]

Who is affected: Organizations that deploy Microsoft 365 apps for Mac using the suite installation package.

What will happen:

• The Microsoft 365 apps for Mac suite installer will include the Microsoft 365 Copilot shim app.
• Users will be able to download and install the full Microsoft 365 Copilot app by opening the shim app from the Applications folder.
• Existing installations of Microsoft 365 apps on macOS are not affected.
• Organizations that want to deploy Microsoft 365 Copilot to devices already running Microsoft 365 apps should deploy the shim app separately.

[What you can do to prepare]

If your organization deploys Microsoft 365 apps for Mac using the suite installer package:

• 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 –

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.

• Custom Quote Generation – Generates personalized quotes using product intent captured from customer conversations and contextual data, ensuring that each quote is precisely tailored to the customer’s needs.
• Integration with Pitch & Close capabilities – Provides the generated quote to the Pitch & Close agent, which then uses it to verify and confirm the customer’s purchase intent, creating a seamless handoff between agents.
• Customer-Driven Activation Workflow – Offers flexibility by allowing quotes to be activated upon explicit customer approval, subsequently transitioning into an order that is submitted to back-end order management systems.
• Native D365 Sales Integration – For customers utilizing the D365 Sales Quote and Order workflow, the agent can read and write to the Quote & Order tables in Dataverse. It can also autonomously generate new quotes, streamlining the quoting process within the ecosystem.
• Third-Party and Custom System Support – Integrates with third-party systems (e.g., SAP) or custom quoting solutions for customers not using the native D365 Sales system, ensuring the agent can function in diverse environments.

• Early detection of issues that could block quality or feature updates 
• Improved visibility into device readiness and update health 
• Reduced manual troubleshooting and post-deployment firefighting 
• Stronger security posture through timely and reliable updates 

1. Go to the Microsoft Intune admin center. 
2. Select Devices > Windows updates. 
3. Depending on the insights you need: 
4. Select Feature updates or Quality updates, then a specific update to access update readiness checker. 
5. Select Feature updates or Quality updates > Alerts and remediations. Select Feature updates > Devices managed for feature updates, then a required target release to see device update journey. 
6. Select Overview > Autopatch Management Report. 

• Windows Autopatch prerequisites 
• Windows Autopatch update readiness overview
• Windows Autopatch update readiness brings insights to IT

Updated March 2, 2026: This update serves as a final reminder that SharePoint 2013 workflow will retire and stop working 1 month from now (April 2, 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.

[How this will affect your organization]

If your organization still uses SharePoint 2013 workflows, they will no longer function after April 2nd, 2026. We recommend customers to move to Power Automate or other supported solutions.

[What you need to do to prepare]

You will want to notify your users, workflow developers and site owners. Update your user training and prepare your help desk.

For admins

• Use the Microsoft 365 Assessment tool to scan your tenants for legacy workflow usage.
• Review Guidance: Migrate from classic workflows to Power Automate flows in SharePoint
• Review the Power Automate resources as a solution to legacy workflows.

Note: There will not be an option to extend SharePoint 2013 workflow beyond April 2nd 2026.

Learn more:

• Detailed support article with additional resources. 
  

Updated March 2, 2026: This update serves as a final reminder that Azure ACS in Microsoft 365 will retire and stop working 1 month from now (April 2, 2026).

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

[How this will affect your organization]

If your organization still uses Azure ACS to grant custom developed or third party applications access to SharePoint Online, they will no longer have access after April 2nd, 2026. We recommend customers to update their customizations to use Microsoft Entra ID and ask their solution vendors to do the same.

[What you need to do to prepare]

You will want to notify your Azure ACS users and developers. Update your user training and prepare your help desk.

For admins

• Use the Microsoft 365 Assessment tool to scan your tenants for Azure ACS usage.
• Review the guidance for migrating from Azure ACS to Microsoft Entra ID.
• There will not be an option to extend Azure ACS usage for SharePoint Online beyond April 2nd 2026.

Learn more

• Support update for the retirement of Azure ACS for SharePoint Online in Microsoft 365.

Updated March 2, 2026: This update serves as a final reminder that SharePoint Add-Ins will retire and stop working 1 month from now (April 2, 2026).

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

[How this will affect your organization:]

If your organization still uses SharePoint Add-Ins, they will no longer function after April 2nd, 2026. We recommend customers to port their customizations to SharePoint Framework (SPFx) and ask their solution vendors for updated solutions.

[What you need to do to prepare]

You will want to notify your Add-In users and developers. Update your user training and prepare your help desk.

For admins

• Use the Microsoft 365 Assessment tool to scan your tenants for SharePoint Add-In usage.
• Disable SharePoint Add-Ins on your tenant using SharePoint Online Management Shell
• Review the guidance for migrating from SharePoint Add-Ins to SharePoint Framework.
• There will not be an option to extend SharePoint Add-Ins beyond April 2nd 2026.

New: How to disable SharePoint Add-Ins on your tenant

Admins can disable SharePoint Add-Ins with the Set-SPOTenant SharePoint Management Shell PowerShell command.

Connect-SPOService -Url https://<tenant>-admin.sharepoint.com

Set-SPOTenant -IsSharePointAddInsDisabled $true

After SharePoint Add-Ins are disabled, users will not be able to add SharePoint Add-Ins to their sites, and admins cannot add new SharePoint Add-Ins to the tenant and site collection app catalogs. SharePoint Add-Ins already added to sites will stay available and can still be used by the site’s users.

New: SharePoint Add-Ins will not be available from the public marketplace

After July 1, 2024, users browsing the public marketplace (AppSource) will see SharePoint Add-In, but if they select Get it now, a message will explain that SharePoint Add-Ins are retired and cannot be added. If you still require a specific SharePoint Add-In, contact the Add-In creator to understand the possible options.

Learn more

• Support update for the retirement of SharePoint Add-Ins in Microsoft 365.

Updated March 2, 2026: We have updated the timeline. Thank you for your patience. 

 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:

1. Only a user email notification
2. Only a policy tip
3. A user email notification and a policy tip
4. 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). 

[How this will affect your organization:]

After rollout, to configure policy tips and user email notifications, you can use PowerShell or Purview | Data Loss Prevention.

In PowerShell

After rollout, use the new parameter called -NotifyUserType with the cmdlets New-DlpComplianceRule and Set-DlpComplianceRule.

Use New-DlpComplianceRule to create a new rule. Use Set-DlpComplianceRule to update an existing rule.

• Default value: NotSet
• To enable a policy tip: PolicyTip
• To enable a user email notification: Email
• To enable a user email notification and a policy tip: Email,PolicyTip

Example 1: New-DlpComplianceRule -Name "PT rule" -Policy "Policy Name" -ContentContainsSensitiveInformation @{Name="India Unique Identification (Aadhaar) Number"} -NotifyUserType PolicyTip -NotifyUser SiteAdmin,LastModifier,Owner

Example 2: Set-DlpComplianceRule -Identity "Rule Name" -NotifyUserType Email

To check that the value is set correctly, check the following and check the parameter value for NotifyUserType:

Get-DlpComplianceRule -Identity "Rule Name" | fl

In Data Loss Prevention (DLP)

Before rollout:

After rollout:

DLP examples

Rule 1: Configured to only trigger a user email notification:

Rule 2: Configured to only trigger a policy tip:

Rule 3: Configured to trigger a user email notification and a policy tip:

[What you need to do to prepare:]

This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to update any relevant documentation as appropriate.

Updated March 2, 2026: This update serves as a final reminder that SharePoint Framework domain isolated web parts will retire and stop working 1 month from now (April 2, 2026).

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.

[How this will affect your organization:]

If your organization still uses domain isolated web parts, after the change has rolled out these will render an error message and stop functioning. We recommend customers to update the impacted web parts as regular web parts and redeploy them.

[What you need to do to prepare:]

To understand whether you have installed domain isolated web parts and granted permissions you can verify if the SharePoint admin center API access page contains permissions listed under the Isolated grouping. If you see permissions listed under Isolated then you can use the instructions described on the domain isolated web part retirement page to discover the solutions, their domain isolated web parts and where those web parts are used. This resource will also contain the needed steps to update the web parts to not use domain isolation.

Note: There will not be an option to extend domain isolated web parts beyond April 2, 2026.

Learn more:

• Domain isolated web part retirement page
• Retirement announcement blog post

Updated March 2, 2026: We have updated the timeline. Thank you for your patience.

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

[How this will affect your organization:]

Before this rollout, users were not able to see their automapped calendars when toggling from classic Outlook to new Outlook.

To access an automapped calendars, users can go to Microsoft Outlook > Calendar icon on left of screen > My Calendars > Automapped calendar.

This feature is on by default.

[What you need to do to prepare:]

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

Learn more

• The section called Use the shared calendar from the shared mailbox in Open and use a shared mailbox in Outlook – Microsoft Support
• Definition of automapping: Remove automapping for a shared mailbox – Outlook | Microsoft Learn

#newoutlookforwindows