Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 11:16 UTC Customize Public modeDiscuss ChangeIntel on Discord

SharePoint Framework domain isolated web parts retirement

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

What the notice says

Microsoft’s text, safely structured

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:

What changed

Between archive captures, newest first
  1. Updated FebruaryMarch 2, 2026: This update serves as a final reminder that SharePoint Framework domain isolated web parts will retire and stop working in 2 months1 month from now (April 2, 2026). After careful consideration and extensive review of …

  2. Updated January 5,February 2, 2026: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 3 2 months from now (April 2, 2026). After careful consideration and extensive review …

  3. Updated October 3, 2025:January 5, 2026: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 6 3 months from now (April 2, 2026). After careful consideration and extensive review …

  4. Updated June 2,October 3, 2025: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 106 months from now (April 2, 2026). After careful consideration and extensive review …

    • Tags User impact, Admin impact, Retirement → Updated message, User impact, Admin impact, Retirement

    Updated June 2, 2025: This update serves as a reminder that SharePoint Framework domain isolated web parts will retire and stop working in 10 months from now (April 2, 2026). After careful consideration and extensive review of usage data and feedback Microsoft …

  5. · first version seen

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 11:16 UTC · 271 of 272 readable · 270 fully read · documentation 469/469 current