Bemærk
Adgang til denne side kræver godkendelse. Du kan prøve at logge på eller ændre mapper.
Adgang til denne side kræver godkendelse. Du kan prøve at ændre mapper.
Important
SharePoint Add-ins reached end of life in SharePoint Online on April 2, 2026. Both SharePoint-hosted and provider-hosted Add-ins are retired and no longer work in SharePoint Online, including government clouds. Add-in development, deployment, and usage guidance is retained for historical reference and for applicable SharePoint Server scenarios, not for new SharePoint Online solutions.
SharePoint Server Add-ins deployed through an on-premises app catalog are not retired by this change. Acquiring SharePoint Add-ins from the public marketplace ended on April 2, 2026 for SharePoint Server.
This retirement does not retire SharePoint REST APIs, CSOM, JSOM, or SharePoint Framework (SPFx). For SharePoint Online, use SPFx for user interface extensions and Microsoft Entra ID for authentication to external applications. See the retirement announcement and Add-in migration guidance.
The articles in this section show you how to deploy your SharePoint Add-ins.
| Article | Shows you how to use the add-in model to |
|---|---|
| Deploy development Office 365 sites to Microsoft Azure | This page explains the steps involved in taking an Office 365 API development project and launching it to a working sample hosted entirely in Azure. |
| Publish SharePoint Add-ins | This section explains how to publish your add-ins for use in SharePoint sites. |
| Use the App Catalog to make custom business apps available for your SharePoint environment | This page explains how to create and use the App Catalog to deploy add-ins for use in SharePoint sites. |
| Use Microsoft Azure WebJobs with Office 365 | Use Azure WebJobs to implement timer jobs that can access SharePoint Online. |
| Configure SharePoint provider-hosted add-ins for distribution | This page explains issues that may arise when sharing a SharePoint provider-hosted add-in with other developers, or when obtaining a copy from a source control system such as Team Foundation Server, Git, or Visual Studio Team Services. |
| Configure Office 365 API projects for distribution | This page explains some steps developers should consider taking on their projects that leverage the Office 365 APIs prior to distributing them to other developers, their customers, or to source control systems. |