Microsoft is officially retiring the SharePoint Add-In extensibility model, marking a significant shift in how organizations extend SharePoint Online. While this change does not impact the SharePoint Framework (SPFx), it has major implications for businesses relying on SharePoint Add-Ins for customization and integration.
Key dates to keep in mind:
- November 1, 2024 – SharePoint Add-Ins will no longer function in newly created tenants.
- April 2, 2026 – SharePoint Add-Ins will stop working in existing tenants.
Additionally, acquiring, updating, and adding SharePoint Add-Ins from the marketplace will be retired. However, the use of a tenant app catalog for third-party SharePoint Add-Ins will remain supported until April 2, 2026.
If you are using custom-developed SharePoint Add-Ins, migration to SPFx-based solutions should begin as soon as possible. For those relying on marketplace-acquired or third-party SharePoint Add-Ins, updated versions that do not depend on the SharePoint Add-In model will be required.
Recommended Next Steps from Microsoft
1. Evaluate Usage
The first step is to get a complete understanding of what SharePoint Add-Ins are in use in your environment. Begin by running the Microsoft 365 Assessment Tool to scan your tenant.
This will provide a Power BI SharePoint Add-In Report that:
- Identifies all SharePoint Add-Ins in the tenant and per site.
- Provides information on the SharePoint Add-In source and who it was installed by.
- Lays out the validity and permission scope details on provider hosted Add-Ins.
By running the Microsoft 365 Assessment Tool and evaluating the SharePoint Add-In Report you will have a good understanding of what is in use and where. This is an important first step when planning migrating business relevant SharePoint Add-Ins to supported development models.
2. Migrate Using Modern Development Models
With an understanding of what SharePoint Add-Ins are in-play, you can begin migration to alternative solutions.
- SharePoint Framework web parts can be used to replace SharePoint hosted Add-Ins.
- SaaS application platforms like Microsoft Azure paired with Microsoft Entra ID for auth can be used as alternative development models for provider hosted Add-Ins.
For more information on migration check out Microsoft’s Modernization guidance for existing SharePoint Add-In model implementations in Microsoft 365 and watch these videos.
3. Disable SharePoint Add-Ins
Microsoft also recommends that you disable Add-In usage for your tenant. The Set-SPOTenant SharePoint Management Shell PowerShell command can be used by Admins to disable SharePoint Add-Ins.
Once disabled in the tenant SharePoint Add-Ins the following happens:
- SharePoint Add-Ins can no longer be added to sites by users
- SharePoint Add-Ins can no longer be added to tenants or site collection app catalogs by admins
- Existing SharePoint Add-Ins will remain available for use
Get Expert Help Migrating SharePoint Add-Ins
Need help identifying and remediating the SharePoint Add-Ins in your environment? We can help. Please reach out directly to Compass365 to arrange for a complimentary consultation.
Compass365, a Microsoft Solutions Partner, delivers SharePoint, Microsoft Teams and Power Platform solutions that help IT and Business leaders improve the way their organizations operate and their employees work.
