Microsoft has officially retired SharePoint Add-ins in Microsoft 365, with the final cut-off now reached as of April 2, 2026. Organisations still relying on this model face an immediate need to migrate to modern alternatives to avoid disruption.
This milestone marks the end of a long journey, and the beginning of a more modern SharePoint development landscape. We explain more about the update and next steps in this article.
What Are SharePoint Add-ins?
SharePoint Add-ins (formerly Apps for SharePoint) were introduced to extend SharePoint functionality without deploying server-side code. They enabled custom apps, integrations, and web parts to run either within SharePoint or externally. However, the model is now considered legacy and has been replaced by more modern, cloud-aligned approaches.
End of Life: Key Dates You Need to Know
Microsoft has phased out SharePoint Add-ins in several stages over the past two years. Between March and July 2024, new Add-ins were no longer accepted or made available through the public marketplace. From November 1, 2024, Add-ins were disabled for all new tenants, preventing any new deployments.
This phased approach has now reached its final stage, with SharePoint Add-ins fully retired as of April 2, 2026, meaning they no longer function in any SharePoint Online tenant. There is no extension or grace period; any remaining Add-ins will simply stop working.
What Does This Mean in Practice?
Following the retirement date, SharePoint Add-ins no longer function in SharePoint Online. Add-in web parts will fail to load, custom UI elements and integrations will stop working, and any dependent business processes may break. This applies to all Add-in types, including SharePoint-hosted, provider-hosted, and third-party solutions, and is closely tied to the retirement of legacy authentication models like Azure ACS.
Why Microsoft Is Retiring Add-ins
The Add-in model has been replaced by technologies that are better suited to modern, cloud-first environments. Microsoft is now focused on solutions that offer stronger Microsoft 365 integration, improved security through Microsoft Entra ID, and a better user experience. As a result, the SharePoint Framework (SPFx) has become the primary extensibility model.
Risks of Doing Nothing
Organisations that have not migrated face immediate risks. With Add-ins now retired, any remaining solutions will no longer work, potentially causing critical failures and business disruption. This can also introduce security concerns and increase technical debt, often leading to costly, reactive fixes.
How to Prepare for Migration
A structured approach is essential. Start by identifying all Add-ins in your environment, then assess their purpose and business impact. Map each one to a modern alternative such as SPFx, Power Platform, or Azure, and carry out migration in phases, prioritising critical solutions and testing thoroughly before rolling out.
Need help with your SharePoint migration?
The retirement of SharePoint Add-ins is now a reality, and organisations that act now can turn this change into a strategic advantage.
Whether you’re just starting out or already planning your migration, explore our SharePoint Migration Services or speak to our SharePoint migration specialists for expert guidance and support.
