Microsoft is officially phasing out the SharePoint add-ins in SharePoint Online, which matters a lot if your organization uses add-Ins for custom features or integrations. The end date for add-ins is April 2, 2026; after that, the add-in model will stop working for all SharePoint Online users.
If you’re concerned about SharePoint resources you built using add-ins, there’s no need to fret. Microsoft has now published a clear end-of-life plan for add-Ins. With the help of SharePoint consulting services, you can understand the timeline, what is affected, and what to do next. So, you can migrate to supported options in time.
What are, or were, SharePoint add-ins?
SharePoint add-ins, once known as SharePoint apps, extend SharePoint sites with custom functionality. Consider them like your browser extensions, but ones that work on SharePoint sites only. Add-ins literally add features or business functions without running custom code on the SharePoint server.
Here are some popular SharePoint add-ins that’ll help you understand what they do:
People Finder
A staff directory add-in that makes it easier to find and contact coworkers than SharePoint’s default people search. You can search by name or use filters like department or title.
K2 Five for SharePoint
A workflow automation add-in that lets you build business processes inside SharePoint using a drag-and-drop / point-and-click designer.
Space Navigator for Office 365
A dashboard add-in that reduces SharePoint clutter by centralizing your sites and projects in one place. It organizes everything, so important work stays easy to find and quick to access.
When are Add-Ins retiring? Important dates
Microsoft has already started retiring SharePoint add-ins. Complete end of life will happen in phases, and most of the phases have already passed.
| Date | Effect |
| November 27, 2023 | SharePoint add-in model was not recommended for new solutions |
| July 24, 2024 | Add-ins were discontinued on SharePoint Store |
| November 1, 2024 | Add-ins stop working for new tenants |
| April 2, 2026 | Add-ins will stop working for all tenants |
Currently, only old tenants can privately deploy add-ins via an App Catalog. But after April 2, 2026, the add-In model will not function in any SharePoint Online tenant.
However, there is a caveat. If your organization runs SharePoint on-prem, your current SharePoint Add-ins will keep working even after April 2026. The April 2026 cutoff applies to SharePoint Online tenants only.
Why is Microsoft retiring SharePoint Add-Ins?
Add-ins were introduced in 2012, and they quickly became user favorites. But it looks like they have done their job, and it’s time to give them a well-deserved farewell.
Firstly, many Add-in patterns depend on older auth approaches, while Microsoft 365 is standardizing modern identity and security controls. Retiring the model makes sense because it reduces long-term security risk and legacy dependencies.
Operational simplicity comes second. Supporting multiple, older extensibility stacks increases platform complexity. Moving to fewer, modern models helps Microsoft keep SharePoint Online more consistent and easier to secure and maintain at scale.
Migrating from SharePoint Add-Ins
Microsoft is pretty clear where SharePoint add-ins users move to: SharePoint Framework (SPFx). It is Microsoft’s modern platform designed for cloud-based solutions.
SPFx was built specifically for SharePoint Online and works naturally with the Modern SharePoint experience, so solutions feel more integrated and consistent for users. Because SPFx has become the preferred approach for most new SharePoint customizations, Microsoft has been putting its time, updates, and long-term investment into SPFx.
Best practices to migrate from SharePoint Add-Ins
These are some of the best practices for migrating from SharePoint Add-Ins. It is not all about replacement, as the discipline with which you choose what to keep, what to rebuild, and what must finally be left behind is equally important.
1. Check what you’re actually using
Inventory every SharePoint Add-In in your tenant so you know what could be affected. You can use the Microsoft 365 Assessment Tool for this. It generates a Power BI SharePoint Add-In report that helps you:
- See all Add-Ins across the tenant (and which sites they’re on)
- Identify where each Add-In came from and who installed it
- For provider-hosted Add-Ins, review key details like validity and permission scope
This gives you a clear map of what exists and where, which is essential before planning migration.
2. Replace add-ins with modern alternatives
Once you know what Add-Ins are in use, start moving them to newer, supported approaches:
- SharePoint-hosted Add-Ins: These are SPFx extensions with modern SharePoint customizations
- Provider-hosted Add-Ins: Such modern cloud apps, like those on Microsoft Azure, can be accessed using Microsoft Entra ID for authentication
You can consult Microsoft’s modernization guidance and videos to plan and execute these migrations safely.
3. Disable existing add-ins
Use SharePoint Online PowerShell to turn off add-ins in your tenant. It’s about stopping new installs, not breaking what’s already there. Disabling new ones maintains the migration scope manageable.
Conclusion
The retirement of SharePoint Add-Ins is a chance to improve the way your intranet actually works. Migration done well removes the dependencies that make SharePoint environments fragile. Handled with intention, this transition can leave your SharePoint simpler to run, easier to scale, and far more resilient.
If you want experienced guidance for the migration process, Xavor can help. Our SharePoint consulting services identify and resolve the SharePoint Add-Ins in your environment. Contact us at [email protected] to start planning your migration journey before April 2026 and build an intranet that’s ready for what comes next.
FAQs
SharePoint Add-ins extend SharePoint with custom features like dashboards, forms, document automation, integrations, and role-based workflows without changing the core SharePoint platform.
Yes, but Microsoft’s direction has shifted toward SharePoint Framework (SPFx) for most modern customizations. Add-ins will still work until April 2, 2026, after that they will no longer be supported for any new or old tenant.
Microsoft is retiring SharePoint Add-ins because the model is deprecated, outdated, and heavily dependent on Azure Access Control Services (ACS), which is also being retired. Microsoft also wants to steer customers toward modern alternatives like SharePoint Framework (SPFx) and Microsoft Entra ID.