Published: 9 June 2026. Source: Microsoft 365 Message Center MC616550 and Microsoft Tech Community blog.
On 14 July 2026, InfoPath Forms Services stops rendering forms in SharePoint Online. That is five weeks from today. Any SharePoint site still serving InfoPath browser forms will break on that date, with no extension option and no automatic migration path provided by Microsoft.
What is retiring and what is not
The retirement covers InfoPath Forms Services in SharePoint Online: the server-side component that renders InfoPath .xsn files in a web browser without requiring the InfoPath 2013 client installed locally. The same date marks the end of support for InfoPath 2013, the last desktop version Microsoft shipped.
What is not immediately affected: SharePoint document libraries that store .xsn files as plain documents. Those files are not deleted on retirement day. They simply cannot be opened as functioning forms once the rendering service ends.
An earlier restriction is already in effect: as of 18 May 2026, SharePoint Online blocks publishing new or updated InfoPath forms for all tenants. Administrators who attempted to republish a form after that date will have encountered an error. The July 14 date removes rendering for every form published before the May cutoff.
Retirement timeline
| Date | What changes |
|---|---|
| 18 May 2026 | Publishing new or updated InfoPath forms to SharePoint Online is blocked for all tenants. |
| 14 July 2026 | InfoPath Forms Services stops rendering existing forms. Browser-rendered forms return errors. InfoPath 2013 client reaches end of support; no further security patches are issued. |
| After 14 July 2026 | .xsn files remain stored in SharePoint libraries but are non-functional as forms. No file data is deleted, but no form can be rendered or submitted. |
What admins need to do before 14 July
Five weeks is enough time for straightforward forms. Complex forms with cascading lookups, REST or SOAP data connections, or multi-stage approval flows can take significantly longer to rebuild. Starting the inventory now is the critical first step.
-
Find all InfoPath forms in the tenant. Search document libraries for files with the
.xsnextension, or look for form libraries created specifically for InfoPath. ShareMaster's Report Master exports library metadata including content types across all sites, which helps surface form libraries quickly across a large tenant without manual browsing. - Classify each form by complexity. Simple forms (basic fields, no external data connections) typically migrate to Microsoft Forms in a few hours. Complex forms with lookup lists, REST data connections, calculated fields, or digital signature requirements need Power Apps and may take days to rebuild properly.
- Build replacement forms in Power Apps or Microsoft Forms. Prioritise any form tied to an active business process: expense approval, IT request intake, new supplier registration. Microsoft provides Power Apps for SharePoint tutorials covering the most common migration patterns.
- Update linked workflows. Once a replacement form is live, update the trigger in any Power Automate flows or SharePoint Designer workflows that currently fire on InfoPath form submission to point at the new list or Power Apps output.
- Communicate to end users before the cutover. Anyone who has bookmarked a form URL or embedded a form link in a Teams channel tab will hit a broken page on July 14 unless the replacement is published and re-linked first.
Frequently Asked Questions
What happens to existing InfoPath forms after July 14, 2026?
InfoPath Forms Services will no longer render forms in SharePoint Online - users opening a browser-rendered form will see an error. The underlying .xsn files remain in the library but cannot be opened as functioning forms.
Can I still use the InfoPath 2013 desktop client after July 2026?
InfoPath 2013 reaches end of support on 14 July 2026. Microsoft will not issue security patches after that point. Forms connecting to SharePoint Online will lose the server-side rendering needed to function in a browser, making the client effectively unusable for SharePoint-integrated forms.
What should I migrate InfoPath forms to in Microsoft 365?
Microsoft recommends Power Apps for complex forms with conditional logic, data connections, or approval workflows. Microsoft Forms suits simpler data collection. For workflows triggered on InfoPath form submission, Power Automate provides the same SharePoint connector support.