InfoPath 2013 client and InfoPath Forms Services in SharePoint Online will reach end of support in July 2026
Industry trends and feedback from our customers and partners make it clear that today’s businesses demand an intelligent, integrated forms experience that spans devices which InfoPath does not provide. As announced earlier, InfoPath Client 2013 will reach the end of its extended support period on July 14, 2026 (link), and to keep an aligned experience across Microsoft products, InfoPath Forms Service will be retired from SharePoint Online. We’re sending this message to bring it to your early attention to minimize the potential impact on your organization.
Key Points:
- Major: Retirement
- Timeline: Starting from July 14, 2026, Microsoft will remove InfoPath Forms Services for existing tenants.
- Action: Review and assess impact
How this will affect your organization:
After July 14, 2026, users will no longer be able to use InfoPath forms in SharePoint Online.
What you need to do to prepare:
To understand how InfoPath is used in your organization, you can run the Microsoft 365 Assessment tool to scan the tenant for InfoPath usage. Using the Power BI InfoPath Report generated by the scanner tool, you can:
- Identify all InfoPath Forms usage in the tenant, per site collection and site.
- Evaluate the recency and volume of usage of InfoPath Forms.
- Understand lists, libraries and content types that use InfoPath.
We recommend communicating to the impacted site owners/teams inside your organization now, so they are aware of the coming change.
Please plan appropriately as there will not be an option to extend InfoPath Form Services beyond the InfoPath retirement date of July 14, 2026.
For scenarios where InfoPath or InfoPath Forms services are currently being used, we recommend migrating to Power Apps, Power Automate or Forms. Please ensure that you allow adequate time for migration of any use of InfoPath/InfoPath Forms Services in your organization ahead of this date, as there is no migration tool provided. Additional instructions on how to migrate can be found in this blog.
Message ID: MC616550
No comments yet