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.
The SharePoint Add-in portions of this article are legacy guidance. The retirement below doesn't retire the other APIs or platforms discussed here.
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.
If you're using InfoPath as the basis for creating forms in your add-ins, now is the time to start thinking about migrating your forms to other solutions. Although InfoPath is currently supported, InfoPath 2013 is the last release of the desktop InfoPath client, and InfoPath Forms Services in SharePoint 2013 is the last release of InfoPath Forms Services.
The client and the on-premises version of InfoPath Forms Services in SharePoint 2013 will be fully supported until 2023. The forms service will be supported in Office 365 until at least the next major release of Office.
To replace your InfoPath forms, you can choose one of the following alternatives:
Use Microsoft Power Automate and Microsoft PowerApps.
Move complex behaviors to the new add-in model and client-side developments.
We recommend the first two solutions because information workers that don't know how to write and deploy code-based alternatives can implement them. The following table describes the scenarios for which each alternative is best suited.
Alternatives to InfoPath in SharePoint 2013
| Alternative | Scenario |
|---|---|
| Microsoft Power Automate and Microsoft PowerApps | This is the recommended approach for extending lists by SharePoint power users. |
| New add-in model and client-side developments | You can convert complex forms driven by extensive code into provider-hosted add-ins or client-side web parts. This option requires developer resources. |