SharePoint add-in retirement
Microsoft's edit ·
Microsoft's commit message in SharePoint/sp-dev-docs · commit 46917aa · +3 −3 lines · also on GitHub
⋯ 23 unchanged lines
2424
2525
SharePoint Add-Ins come in two flavors: SharePoint hosted Add-Ins and provider hosted Add-Ins, both of which are effected by this retirement.
2626
27
−[SharePoint hosted Add-Ins primarily bring UX elements](https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/sharepoint-add-ins#sharepoint-hosted-sharepoint-add-ins) to the site the Add-In was installed into and the app web that was created for the Add-In. A common use case is showing SharePoint Add-In web parts on pages of the host web, using [SharePoint Framework](https://aka.ms/spfx) based web parts is the recommended alternative here. These applications use JavaScript for writing business logic using the logged in user context to authenticate.
27
+[SharePoint hosted Add-Ins primarily bring UX elements](sharepoint-add-ins.md#sharepoint-hosted-sharepoint-add-ins) to the site the Add-In was installed into and the app web that was created for the Add-In. A common use case is showing SharePoint Add-In web parts on pages of the host web, using [SharePoint Framework](https://aka.ms/spfx) based web parts is the recommended alternative here. These applications use JavaScript for writing business logic using the logged in user context to authenticate.
2828
29
−[Provider hosted SharePoint Add-Ins](https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/sharepoint-add-ins#provider-hosted-sharepoint-add-ins) run outside of SharePoint and typically have their own UX. They use Azure ACS (Access Control Services) as auth layer to enable calling back into the host web where the SharePoint Add-In was installed. SharePoint provider hosted Add-Ins can be rewritten in various ways as software as a service application hosted externally (e.g. Microsoft Azure) and optionally also offered as Teams application. The auth model for these will be based on Microsoft Entra ID. If there are requirements to integrate in the SharePoint UX then [SharePoint Framework](https://aka.ms/spfx) can be used as calling into external application APIs can be done from SharePoint Framework solutions.
29
+[Provider hosted SharePoint Add-Ins](sharepoint-add-ins.md#provider-hosted-sharepoint-add-ins) run outside of SharePoint and typically have their own UX. They use Azure ACS (Access Control Services) as auth layer to enable calling back into the host web where the SharePoint Add-In was installed. SharePoint provider hosted Add-Ins can be rewritten in various ways as software as a service application hosted externally (e.g. Microsoft Azure) and optionally also offered as Teams application. The auth model for these will be based on Microsoft Entra ID. If there are requirements to integrate in the SharePoint UX then [SharePoint Framework](https://aka.ms/spfx) can be used as calling into external application APIs can be done from SharePoint Framework solutions.
3030
3131
### SharePoint Server support for SharePoint Add-Ins
3232
⋯ 17 unchanged lines
5050
5151
### Migrate business relevant SharePoint Add-Ins by using newer SharePoint development models
5252
53
−SharePoint hosted Add-Ins can be replaced by [SharePoint Framework](https://aka.ms/spfx) web parts, for the provider hosted Add-Ins any software as a service application platform (e.g. Microsoft Azure) in combination with [Microsoft Entra ID](https://learn.microsoft.com/en-us/azure/active-directory/develop/) for auth can be used as alternative development model.
53
+SharePoint hosted Add-Ins can be replaced by [SharePoint Framework](https://aka.ms/spfx) web parts, for the provider hosted Add-Ins any software as a service application platform (e.g. Microsoft Azure) in combination with [Microsoft Entra ID](https://learn.microsoft.com/azure/active-directory/develop/) for auth can be used as alternative development model.
5454
5555
To learn more about how to migrate SharePoint Add-Ins to alternative solutions check out these [articles](https://aka.ms/retirement/addins/guidance) and accompanying [videos](https://aka.ms/sp/add-in/modernize/videos).
5656
⋯ 15 unchanged lines
Microsoft's Markdown source from SharePoint/sp-dev-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 01:29 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.