SharePoint add-in retirement

[added: Important SharePoint Add-ins reached end of life in SharePoint Online on April 2, 2026. Both SharePoint-hosted and provider-hosted Add-ins are retired and no longer work in SharePoint Online, including government clouds. Add-in development, deployment, and usage guidance is retained for historical reference and for applicable SharePoint Server scenarios, not for new SharePoint Online solutions. SharePoint Server Add-ins deployed through an on-premises app catalog are not retired by this change. Acquiring SharePoint Add-ins from the public marketplace ended on April 2, 2026 for SharePoint Server. This retirement does not retire SharePoint REST APIs, CSOM, JSOM, or SharePoint Framework (SPFx). For SharePoint Online, use SPFx for user interface extensions and Microsoft Entra ID for authentication to external applications. See the retirement announcement and Add-in migration guidance.]

Before: No saved wording on this side.

After: Important SharePoint Add-ins reached end of life in SharePoint Online on April 2, 2026. Both SharePoint-hosted and provider-hosted Add-ins are retired and no longer work in SharePoint Online, including government clouds. Add-in development, deployment, and usage guidance is retained for historical reference and for applicable SharePoint Server scenarios, not for new SharePoint Online solutions. SharePoint Server Add-ins deployed through an on-premises app catalog are not retired by this change. Acquiring SharePoint Add-ins from the public marketplace ended on April 2, 2026 for SharePoint Server. This retirement does not retire SharePoint REST APIs, CSOM, JSOM, or SharePoint Framework (SPFx). For SharePoint Online, use SPFx for user interface extensions and Microsoft Entra ID for authentication to external applications. See the retirement announcement and Add-in migration guidance.

SharePoint Add-Ins [removed: will stop] [added: stopped] working for new [added: SharePoint Online] tenants [removed: as of] [added: on] November [removed: 1st, 2024; they will stop working] [added: 1, 2024 and] for all [added: SharePoint Online] tenants [removed: as of] [added: on] April [removed: 2nd,] [added: 2,] 2026. This applies to all environments[added: ,] including [removed: Government Clouds] [added: government clouds] and the U.S. Department of Defense.

Before: 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.

After: 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.

[added: 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.]

Before: No saved wording on this side.

After: 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.

[removed: SharePoint Add-Ins come in two flavors:] [added: Both] SharePoint hosted Add-Ins and provider hosted [removed: Add-Ins, both of which] [added: Add-Ins] are [removed: impacted.] [added: retired in SharePoint Online.]

Before: SharePoint Add-Ins come in two flavors: SharePoint hosted Add-Ins and provider hosted Add-Ins, both of which are impacted.

After: Both SharePoint hosted Add-Ins and provider hosted Add-Ins are retired in SharePoint Online.

[added: 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.]

Before: No saved wording on this side.

After: 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.

[removed: Project Online is an extension on top of] SharePoint [removed: Online and SharePoint] Add-Ins could also have been used to extend Project Online. [removed: The retirement of SharePoint] [added: Those] Add-Ins [removed: applies to Project Online as well, any SharePoint Add-In used in Project Online will follow] [added: followed] the same retirement [removed: path] [added: timeline] as SharePoint Add-Ins [removed: used] in SharePoint [removed: Online.] [added: Online and retired on April 2, 2026.]

Before: 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.

After: 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.

[added: Before retirement, admins could block new Add-In installations with the Set-SPOTenant SharePoint Management Shell PowerShell command. The following command is retained for historical context; it does not extend or restore Add-In functionality after April 2, 2026.]

Before: No saved wording on this side.

After: Before retirement, admins could block new Add-In installations with the Set-SPOTenant SharePoint Management Shell PowerShell command. The following command is retained for historical context; it does not extend or restore Add-In functionality after April 2, 2026.

[added: 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.]

Before: No saved wording on this side.

After: 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.

[added: The retirement was also communicated through the Microsoft 365 admin center Message Center.]

Before: No saved wording on this side.

After: The retirement was also communicated through the Microsoft 365 admin center Message Center.

[removed: 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.]

Before: 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.

After: No saved wording on this side.

[removed: Important The SharePoint add-in model deprecation in SharePoint Online does not impact SharePoint Framework (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.]

Before: Important The SharePoint add-in model deprecation in SharePoint Online does not impact SharePoint Framework (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.

After: No saved wording on this side.

[removed: 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.]

Before: 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.

After: No saved wording on this side.

[removed: 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.]

Before: 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.

After: No saved wording on this side.

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

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

After: No saved wording on this side.

[removed: 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.]

Before: 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.

After: No saved wording on this side.

[removed: 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.]

Before: 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.

After: No saved wording on this side.