Update remote components in SharePoint Add-ins


The SharePoint Add-In model in SharePoint Online has been retired as of November 27th 2023, checkout the full retirement announcement to learn more.

Retirement means that the feature will not get any new investments, but it's still supported. End-of-life means that the feature will be discontinued and is no longer available for use.

Before you begin, be familiar with Update SharePoint Add-ins and the prerequisites and core concepts listed in it.

For the most part, only very general advice can be provided for updating the remote components because of the wide differences in platforms and tenancy systems. The following section provides some guidance.

For a provider-hosted SharePoint Add-in, you update the remote components by using the best update practices of the platform on which the components are hosted. Just as the remote components of a provider-hosted add-in are installed separately from the installation of the SharePoint Add-in itself, they are also updated separately. Some points to consider:

  • The updated remote components should continue to work with all earlier versions of the SharePoint Add-in.

  • If you implemented a tenancy isolation system for your remote components, keep in mind that different tenants might be using multiple versions of your add-in, and a specific tenant might even have different versions installed on various SharePoint websites.

For a provider-hosted SharePoint Add-in that uses Microsoft Azure SQL Database or SQL Server, there are multiple methods for updating the database. To get started, see Upgrade a Data-tier Application.

Next steps

Return to Major steps in updating an add-in, or go directly to one of the following articles to learn how to update the next major component of your SharePoint Add-in.

See also