SharePoint / SharePoint/sp-dev-docs

Tenant Wide Extensions (SPFx) not loading in new SharePoint experience (preview)

Open
#10,750 5 comments 2 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Apr 1, 2026.

sharepoint-developer-support type:bug-suspected type:uservoice-request
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Describe the bug / error

Hi everyone 👋

I'm experiencing an issue with Tenant Wide Extensions (SPFx) not loading when navigating to:

https://<tenant>.sharepoint.com/_layouts/15/sharepoint.aspx

This only happens when the new SharePoint experience (preview) (available to all customers after the SharePoint at 25 digital event, yesterday) is activated at the tenant level.

Details:

  • The SPFx extension is deployed tenant-wide (via Tenant App Catalog).
  • It works correctly in other sites and any modern site page.
  • It does not load in the new SharePoint experience (preview) accessed via /sharepoint.aspx.
  • No obvious errors appear in the console related to the extension loading lifecycle.

Questions:

  1. Are Tenant Wide Extensions currently supported in the new SharePoint experience (preview)?
  2. Is there a known limitation for extensions on /sharepoint.aspx?
  3. Has anyone found a workaround or official guidance from Microsoft regarding this?

Any insights would be greatly appreciated 🙏
Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.