Skip to main content

The retirement of SharePoint Add-Ins within the Microsoft 365 environment

Microsoft has announced news regarding the retirement of SharePoint Add-Ins. Here are the key highlights.

Key Notes:
Retirement of SharePoint Add-Ins: As part of the development of Microsoft 365 solutions, Microsoft is ending the extensibility approach for SharePoint Add-Ins. As of November 1, 2024, SharePoint Add-Ins will no longer function for new tenants. By April 2, 2026, they will be completely retired for current tenants.

Retirement of Public Marketplace: The public marketplace will no longer be used to add, modify, or purchase SharePoint Add-Ins. Microsoft will stop advertising new SharePoint Add-Ins on March 1st, 2024, and after July 1st, 2024, users won't be able to purchase SharePoint Add-Ins from the open market.

Microsoft advises: switching from custom-developed SharePoint Add-Ins to solutions based on the SharePoint Framework. If users obtained their SharePoint Add-Ins from the open market, they should ask third parties about updated versions.

Affected SharePoint Add-In Types: This retirement affects both provider-hosted and SharePoint-hosted add-ins. Whereas provider hosted Add-Ins operate independently of SharePoint and offer their own user experience, SharePoint hosted Add-Ins mostly add UX aspects to the website.

Support for Project Online and SharePoint Server: Users of SharePoint Server are still able to install Add-Ins from the app catalog, however they will no longer be able to do so starting on April 2, 2026. The Project Online service is similarly affected by the retirement of SharePoint Add-Ins.

Call to Action - Microsoft 365 Assessment Tool: It is recommended that organizations check for SharePoint Add-In usage among their tenants by using the Microsoft 365 Assessment tool. The application generates a Power BI SharePoint Add-with Report that aids with Add-In identification, source planning, and migration planning with minimal impact on users.

Guidance for Migration: SharePoint Framework web parts can take the place of SharePoint hosted Add-Ins. Additionally, provider hosted Add-Ins could use alternative development models such as software as a service apps (like Microsoft Azure) that use Microsoft Entra ID for authentication.

Support & Assistance: Users can contact Microsoft Solution Providers for assistance with migrating from SharePoint Add-Ins, submit support tickets for the SharePoint Assessment tool, and obtain further information by clicking on the links provided within the content.

Communication with Message Center: All tenants receive updates on timeliness on a regular basis through a Message Center post in the Microsoft 365 admin center.

With the goal of increasing the value of Microsoft 365 applications, Microsoft is discontinuing the SharePoint Add-In extension paradigm. On November 1st, 2024, SharePoint Add-Ins will stop functioning for new tenants. By April 2nd, 2026, they will be completely discontinued. The public marketplace for purchasing SharePoint Add-Ins is also being retired. To detect and organize migrations, organizations are urged to use the Microsoft 365 Assessment tool. SharePoint Framework-based solutions are suggested as an alternative. Support tickets and Microsoft Solution Providers offer migration-related assistance. There will be regular updates on the retiring process via a message center post.
I have collected this points from Microsoft's blog, For more info read this from microsoft learn.


Popular posts from this blog

SPFx Interview Questions With Answers

In this article, we are going to discuss interview questions related to the SPFx (SharePoint Framework Development ). It will help you to prepare for the interview and in getting clarity on the core concepts of SPFx development. What is SPFx? SPFx, short for SharePoint Framework,  SPFx  allows us for client-side SharePoint development, we can easily connect with SharePoint data and it also supports for open source tools. What is the major difference between SPFx web part and the SharePoint app? Both the development model supports client-side development but the major difference between these two is that the SharePoint app(add-in) runs on the iframe. What you can build with SPFx? Using SPFx framework we can customize the SharePoint pages. We can build things mentioned below using the SharePoint Framework(SPFx). Web parts, Extensions, Adaptive Card, Library Component How many types of extensions we can create using SPFx? SPFx has three extension types: Application Customizers: Using the

How to register an app in SharePoint

In this article, we are going to learn how to register an app/add-in in SharePoint online. If you have created a Sharepoint provider-hosted add-in or other SharePoint solution and to access the SharePoint site or list using the app/add-in you need to register the add-in on SharePoint and to grant permission. Register app in SharePoint 1. Login into SharePoint and Navigate to register an app page. Use the URL mentioned below:          [Sitecollection URL]/_layouts/15/appregnew.aspx 2.  Once you navigate to the Register app page, a form will open. You need to fill all the fields on the form. Client Id and Client Secret  generated when we click on the generate button available next to the fields.  Title : Name of the add-in which you want to give. App Domain : Where your domain is hosted, for the local environment you can place             "". Do not include HTTP or HTTPS in App Domain. Redirect URL :  Insert the redirect URL, for t

SharePoint Framework SPFx Node Version Compatibility

How to check the compatibility between the SPFx version and the Node.js version The SharePoint Framework (SPFx) is a client-side development platform used to develop web parts and extensions for SharePoint. The SharePoint Framework (SPFx) is compatible with the Node.js versions. Existing SPFx solutions may have different SPFx versions as compared to the current solutions. To make the SPFx solution run, Node.js is required, and in this blog, I am sharing steps to check the compatible node module for SPFx.  Find the SPFx version from the solution:  Open the project solution and navigate to the "package.json" file. In package.json file you will find  "@microsoft/sp-core-library" key and value of this particular key is the version of the SPFx.       Ex:    "@microsoft/sp-core-library": "1.14.0" Another way to find the SPFx version is by command, open the command prompt and run the command mentioned below: npm ls -g --depth=0 @microsoft/generator-s