Blog · · 2 min read
InfoPath and SharePoint 2013 workflows stopped. What to do now
If your company had a request form in SharePoint that “always worked,” it may have stopped this year. Often nobody notices right away: the request just sits there, and someone starts handling it by email until that becomes the process.
What happened in 2026
- April 2: SharePoint 2013 workflows (the ones built in SharePoint Designer) stopped running in every Microsoft 365 tenant. There was no extension option.
- May 18: publishing new InfoPath forms, or updates to existing ones, to SharePoint Online was blocked.
- July 14: Microsoft removed InfoPath Forms Services from SharePoint Online. The forms no longer open.
Microsoft’s own recommendation is to move to Power Apps, Power Automate or Microsoft Forms.
How to find what broke
- Run the Microsoft 365 Assessment tool on your tenant. It lists SharePoint 2013 workflows and InfoPath forms, with the site and list for each.
- Talk to the people who use them. Ask each site owner what changed since April. That is where the processes that quietly moved to email show up.
- Rank by impact. Legal deadlines, audits and money on hold first; then volume.
How to rebuild without repeating the problem
Each form becomes a SharePoint list with a Power Apps form and a Power Automate flow. Three things make the difference:
- Write down the hidden rules. InfoPath forms often carry validation and conditional fields nobody documented. List them before you build.
- Keep a history. The new flow should record who approved, when and with which comment. The old one rarely did this well, and auditors notice.
- Run in parallel briefly. One or two weeks with both paths, a short training for users, then retire the old one.
In most cases this runs on the Microsoft 365 the company already pays for, with no extra licenses. Simple forms usually take one to two weeks each.