Public mode

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

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

SharePoint add-in retirement

This page's changes and edits · All guidance changes

Microsoft's edit ·

SPFx 1.24 GA docs updates - with Copilot Components GA (#11075)

Microsoft's commit message in SharePoint/sp-dev-docs · commit f59497d · +10 −13 lines · also on GitHub

Source wording view
11 ---
22 title: SharePoint Add-In retirement in Microsoft 365
33 description: Describes the details around the retirement of SharePoint Add-In in Microsoft 365.
4 −ms.date: 07/30/2023
4 +ms.date: 10/25/2026
55 ms.localizationpriority: high
66 ms.service: sharepoint
77 ---
88
99 # SharePoint Add-In retirement in Microsoft 365
1010
11 −Microsoft strives to deliver value to our customers through modern, optimized, secure solutions. As part of this evolution of Microsoft 365 solutions, we are retiring the SharePoint Add-In extensibility model and believe Microsoft 365 customers will be better served by modern SharePoint extensibility models.
12 −
13 −> [!IMPORTANT]
14 −> The SharePoint add-in model deprecation in SharePoint Online does not impact [SharePoint Framework (SPFx)](https://aka.ms/spfx), which is the primary replacement technology for SharePoint add-ins. SPFx is the most widely used extensibility model in Microsoft 365 and continues to be supported.
11 +[!INCLUDE [sp-add-in-deprecation](../../includes/snippets/sp-add-in-deprecation.md)]
1512
16 −SharePoint Add-Ins will stop working for new tenants as of November 1st, 2024; they will stop working for all tenants as of April 2nd, 2026. This applies to all environments including Government Clouds and the U.S. Department of Defense.
13 +SharePoint Add-Ins stopped working for new SharePoint Online tenants on November 1, 2024 and for all SharePoint Online tenants on April 2, 2026. This applies to all environments, including government clouds and the U.S. Department of Defense.
1714
18 −In parallel with the SharePoint Add-In retirement, the ability to add, update, remove, and acquire SharePoint Add-Ins from the public marketplace will also be discontinued. As of March 1st, 2024 Microsoft will not accept new SharePoint Add-Ins for listing in the public marketplace; as of July 1st, 2024, SharePoint Add-Ins cannot be acquired from the public marketplace. Using a tenant app catalog is supported and enables 3rd parties to offer their SharePoint Add-Ins until April 2nd, 2026.
15 +Microsoft stopped accepting new SharePoint Add-Ins for listing in the public marketplace on March 1, 2024. SharePoint Online users could no longer acquire them from the public marketplace starting July 1, 2024. Distribution through a tenant app catalog was available only until April 2, 2026; an app catalog does not provide a way to continue using SharePoint Add-Ins in SharePoint Online after retirement. App catalogs continue to support SPFx solutions.
1916
2017 If you are using custom developed SharePoint Add-Ins, we recommend migrating them to SharePoint Framework based solutions. If you’ve acquired SharePoint Add-Ins from the public marketplace or from a 3rd party, contact the provider for an updated version that does not depend on the SharePoint Add-In extensibility model.
2118
⋯ 3 unchanged lines
2522
2623 ### SharePoint Add-Ins
2724
28 −SharePoint Add-Ins come in two flavors: SharePoint hosted Add-Ins and provider hosted Add-Ins, both of which are impacted.
25 +Both SharePoint hosted Add-Ins and provider hosted Add-Ins are retired in SharePoint Online.
2926
3027 [SharePoint hosted Add-Ins primarily bring UX elements](sharepoint-add-ins.md#sharepoint-hosted-sharepoint-add-ins) to the site the Add-In was installed into and the app web that was created for the Add-In. A common use case is showing SharePoint Add-In web parts on pages of the host web, using [SharePoint Framework](https://aka.ms/spfx) based web parts is the recommended alternative here. These applications use JavaScript for writing business logic using the logged in user context to authenticate.
3128
⋯ 1 unchanged line
3330
3431 ### SharePoint Server support for SharePoint Add-Ins
3532
36 −Users of SharePoint Server running on-premises can, if configured by the farm admins, install SharePoint Add-Ins from the public marketplace or from the app catalog. The option to acquire and use SharePoint Add-Ins via the app catalog will not be impacted by this retirement, acquiring SharePoint Add-Ins from the public marketplace will stop working from April 2nd, 2026.
33 +This retirement does not retire SharePoint Add-Ins on SharePoint Server when deployed through an on-premises app catalog. Acquiring SharePoint Add-Ins from the public marketplace for SharePoint Server ended on April 2, 2026. The SharePoint Online retirement must not be interpreted as retirement of the SharePoint Server Add-in model.
3734
3835 ### Project Online support for SharePoint Add-Ins
3936
40 −Project Online is an extension on top of SharePoint Online and SharePoint Add-Ins could also have been used to extend Project Online. The retirement of SharePoint Add-Ins applies to Project Online as well, any SharePoint Add-In used in Project Online will follow the same retirement path as SharePoint Add-Ins used in SharePoint Online.
37 +SharePoint Add-Ins could also have been used to extend Project Online. Those Add-Ins followed the same retirement timeline as SharePoint Add-Ins in SharePoint Online and retired on April 2, 2026.
4138
4239 ## Call to Action Guidance
4340
⋯ 15 unchanged lines
5956
6057 ### Disable Add-In usage for your tenant
6158
62 −Admins can disable SharePoint Add-Ins with the [Set-SPOTenant SharePoint Management Shell PowerShell command](/powershell/module/sharepoint-online/set-spotenant).
59 +Before retirement, admins could block new Add-In installations with the [Set-SPOTenant SharePoint Management Shell PowerShell command](/powershell/module/sharepoint-online/set-spotenant). The following command is retained for historical context; it does not extend or restore Add-In functionality after April 2, 2026.
6360
6461 ```PowerShell
6562 Connect-SPOService -Url https://<tenant>-admin.sharepoint.com
6663 Set-SPOTenant -IsSharePointAddInsDisabled $true
6764 ```
6865
69 −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.
66 +Before retirement, this setting blocked new Add-In installations but allowed previously installed Add-Ins to keep running. That exception ended with retirement: existing SharePoint Online Add-Ins no longer work.
7067
7168 ## How do I get help?
7269
⋯ 10 unchanged lines
8380 - Friendly link to the Azure ACS retirement article: https://aka.ms/retirement/acs/support
8481 - Friendly link to Migration Guidance: https://aka.ms/retirement/addins/guidance
8582
86 −A Message Center post in the Microsoft 365 admin center is being sent to all tenants, and the post will be updated periodically with timelines.
83 +The retirement was also communicated through the Microsoft 365 admin center Message Center.

Microsoft's Markdown source from SharePoint/sp-dev-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 29 Oct 00:56 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

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 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current