09/30/2026
The most dangerous phrase in IT this year: “But it still works.”
InfoPath hit its retirement date on July 14, 2026. Here is the trap: for many organizations, the forms didn't visibly break. People submit them, approvals still route, nothing is on fire. So it drops off the priority list.
That is exactly the problem. “Still working” and “supported” are not the same thing.
What we actually see once a platform goes unsupported: it is not a dramatic failure on day one. It is a slow accumulation of risk. No security patches. No fixes when a browser or tenant update changes behavior. And the moment you need to change a form for a new policy or a tax rule, you discover you cannot, because publishing is already blocked.
The pattern is almost always the same. Nothing, nothing, nothing, then an urgent business change forces an emergency migration on the worst possible timeline, usually with the fewest people available.
A calmer way to think about it, even if you cannot migrate everything now:
- Sort forms by risk, not by age. The ones touching personal data, finance, or compliance come first.
- Separate “business critical” from “nice to have.” Not every form deserves a rebuild. Some just need retiring.
- Tighten access to the ones you cannot move yet, and monitor them.
- Treat a required change to a frozen form as the trigger to migrate that process, not to hunt for a workaround.
Running unsupported software is a decision, even when you decide by not deciding. The goal is to make it a conscious, risk-ranked choice instead of a surprise.
If you are still on InfoPath: roughly what share of your forms would you call genuinely business critical? For most teams it is far smaller than the total, and that is the reassuring part.
We wrote up the full risk-ranking and migration approach here if it is useful:
https://hubs.li/Q04vZz590
