On July 14, 2026, Microsoft retired InfoPath 2013 and InfoPath Forms Services in SharePoint Online. If you're reading this, you likely still have InfoPath forms running critical processes, and you're not alone. Thousands of organizations crossed that deadline with forms still in production.
Here's a clear-eyed look at what changed, what's at risk, and what your options actually are.
The two dates that matter
- May 18, 2026: Microsoft blocked publishing new or updated InfoPath forms to SharePoint Online. Your existing forms kept working, but changes were frozen.
- July 14, 2026: InfoPath 2013 client reached end of extended support, and InfoPath Forms Services in SharePoint Online was retired. Microsoft has stated there is no extension option.
What this means in practice
If your forms live in SharePoint Online, InfoPath Forms Services has been retired. Forms that your teams have relied on for years will stop being usable in the browser.
If you run the InfoPath 2013 client (including with on-premises SharePoint), your forms still open, but the software no longer receives security updates. Every InfoPath form filled out on an unsupported client is now part of your attack surface, at exactly the moment AI-assisted tools are making vulnerability discovery dramatically faster for defenders and attackers alike.
And in every case: no more updates means broken forms stay broken. The first time a business rule needs to change, you're out of road.
Your three real options
-
Option 1
Rebuild in Power Apps
Microsoft's recommended path. For simple forms (a handful of fields, basic routing), this is often the right answer. But if you've tried rebuilding a complex InfoPath form in Power Apps, you know the honest math: multi-view forms, repeating tables, code-behind logic, and intricate data connections don't migrate. They get redesigned from scratch, form by form, at consulting rates. Organizations with hundreds of forms routinely see seven-figure estimates.
-
Option 2
Run your InfoPath forms on a platform built for them
This is the path most people don't know exists. Qdabra Forms takes your existing form templates (XSN files) and runs them in any modern browser, with logic, views, and data connections intact. No rebuild. Forms render mobile-responsive, connect to SharePoint, and stay editable with FormsDesigner. Your ten years of form-building investment keeps working. (This is what we do, so weigh our perspective accordingly, then test it with your own forms, which is exactly what we suggest below.)
-
Option 3
Do nothing
Tempting, and honestly viable for a short while on-premises. But unsupported clients accumulate risk, frozen forms accumulate workarounds, and the migration you eventually do will be under pressure instead of on your schedule.
A practical next step
The fastest way to know your options is to see your own forms running somewhere else. Send us one or two of your most complex form templates and we'll show them to you live in Qdabra Forms, as-is, no commitment. If Power Apps is genuinely the better fit for your situation, we'll tell you that too.

