SharePoint Add-In Retirement (April 2, 2026): What You Need To Know

SharePoint Add-ins will stop working on April 2, 2026. Organizations still relying on the SharePoint Add-In model must begin planning migration now to avoid disruptions.

This guide explains what is retiring, who is affected and provides a practical checklist to help you transition to modern SharePoint Framework (SPFx) solutions.

What is retiring and when?

Microsoft has announced the retirement of SharePoint Add-Ins in Microsoft 365.

SharePoint Add-Ins were disabled for new tenants starting November 1, 2024, and will stop working for all tenants on April 2, 2026, this will include marketplace acquisition and update capabilities.

Both SharePoint-hosted Add-Ins and provider-hosted Add-Ins will be affected.

If your organization still relies on any SharePoint Add-ins, the window to maintain consistent functionality is closing, every week you wait reduces testing time and increases the chance of a last-minute outage.

Microsoft has confirmed that there will not be an option to extend SharePoint Add-Ins beyond the April 2nd, 2026 retirement date.

Who is impacted?

Many organizations are unaware they are still running legacy SharePoint Add-ins.

You may be affected if:

• You use classic SharePoint web parts delivered via the Add-In model
• You deployed marketplace apps prior to 2024
• You use provider-hosted apps
• You have custom-developed SharePoint Add-Ins

Where to start: Run an Add-In Audit

Start with a focused audit. Identify which of your SharePoint sites still host Add-In based solutions, and which are business critical.

To understand if/where your organization is using SharePoint Add-Ins, Microsoft recommends running the Microsoft 365 Assessment tool, which evaluates:

• SharePoint Add-In usage across your tenant
• Azure ACS dependency
• Installation source (marketplace vs app catalog)
• Who installed the Add-In

Using this report and further site information, you can:

• Identify all SharePoint Add-Ins in your tenant
• Determine which sites are affected
• Assess business criticality
• Prioritize in your migration planning

Combining assessment data with business impact analysis allows for a controlled and low-risk transition.

Migration Strategy

If you are using custom-developed SharePoint Add-Ins, Microsoft recommends migrating to SharePoint Framework (SPFx) based solutions or other alternatives.

If you have acquired a SharePoint Add-In from Microsoft’s public marketplace or a 3rd party, you should contact the vendor to determine whether:

• A modern SPFx version is available
• The solution is being actively supported
• A migration path is documented

When evaluating alternatives, prioritize:

• Compatibility with your Microsoft 365 security model
• Modern authentication
• Long-term vendor roadmap alignment
• Performance and user experience

Migration Checklist

1. Run the Microsoft 365 Assessment Tool
2. Classify Add-Ins by business criticality
3. Identify replacement approach (SPFx, vendor update)
4. Engage vendors (if marketplace Add-Ins are in use)
5. Build and test replacements in a modern SharePoint site collection
6. Conduct user acceptance testing
7. Communicate changes to stakeholders
8. Decommission legacy Add-Ins before April 2, 2026

Disabling Add-In usage for your tenant

If you want to prevent additional Add-Ins from being installed during your migration process, Microsoft offers the option for SharePoint administrators to disable new Add-in usage via PowerShell.

This prevents new SharePoint Add-Ins from being added to the tenant or site collection app catalogs. It does not disable existing Add-Ins already in use.

Helpful links

• Mirosoft SharePoint Retirement Announcement
• Microsoft SharePoint Add-in Retirement FAQs

Using the TeamOrgChart SharePoint Add-In?

If your tenant is currently using the TeamOrgChart SharePoint Add-In on one or more SharePoint pages, those org charts will stop rendering once Microsoft retires the SharePoint Add-In framework on April 2, 2026.

To ensure uninterrupted functionality, you should migrate to the TeamOrgChart SPFx web part, built on the modern SharePoint Framework (SPFx). This is a one-time upgrade that preserves your org chart experience while aligning with Microsoft’s long-term SharePoint roadmap.

Learn more about upgrading to the TeamOrgChart SPFx solution and how to complete this transition before the retirement deadline.