InfoPath is now end of life
Microsoft InfoPath Forms Services was retired on July 14, 2026. InfoPath forms in SharePoint Online no longer open or submit. If your organisation has active InfoPath forms, they need to be rebuilt now.
What Microsoft InfoPath was — and what it did
Microsoft InfoPath was a form designer for SharePoint. It let non-developers build custom forms on top of SharePoint lists: multi-column layouts, conditional logic, calculated fields, people pickers, attachment controls, and full column type support. You designed in a desktop application and published to SharePoint. No developer, no separate licence, no extra product.
For over a decade, InfoPath was the standard way to build a professional-looking form that actually wrote to a SharePoint list. Compliance forms, risk registers, HR intake forms, incident reports — if your SharePoint had custom forms, they were almost certainly InfoPath forms.
What Microsoft recommends instead — and why it falls short
Microsoft's official position is that Power Apps and Microsoft Forms replace InfoPath. In practice, both fall short of what InfoPath did for SharePoint list forms.
Power Apps — the "official" replacement
Power Apps can customise SharePoint list forms. But it requires a Power Apps per-user or per-app plan (an additional licence on top of Microsoft 365), a Canvas app that a developer or skilled IT resource builds and maintains, and Content Types are not supported out of the box — a known limitation still listed as "under review" on Microsoft's ideas board in 2026.
For organisations that used InfoPath as a no-code tool for non-technical staff, Power Apps is a step backward in complexity and cost. You have traded a product that required no licence and no developer for one that requires both.
Microsoft Forms — the wrong tool
Microsoft Forms is a survey tool. It collects responses into Microsoft Forms storage — not your SharePoint list. Getting data into SharePoint requires a Power Automate flow that runs on every submission. You have added a dependency on two tools and a flow that breaks silently when field names change.
Microsoft Forms also does not replace the NewForm and EditForm in a SharePoint list. It is not a list form replacement. It is a survey. These are different things.
The actual InfoPath replacement for SharePoint list forms
Forms365 Workspace is purpose-built to replace InfoPath for SharePoint list forms. It is a no-code drag-and-drop designer that deploys inside your Microsoft 365 tenant as an SPFx solution. You connect it to a SharePoint list, drag your fields onto the canvas, set your conditional logic, and publish.
It supports everything InfoPath supported — people pickers, linked lists, calculated fields, managed metadata, Content Types — and adds things InfoPath never had: mobile-responsive rendering, AI-assisted form generation, version history with restore points, and automation rules that run on save without a Power Automate flow.
| Capability | Forms365 Workspace | Power Apps | Microsoft Forms |
|---|---|---|---|
| Replaces SharePoint list NewForm / EditForm | Yes | Yes | No |
| No-code drag-and-drop designer | Yes | No | Yes |
| SharePoint Content Types supported | Yes | No | No |
| No additional licence required | Yes | No | Yes |
| Saves directly to SharePoint list items | Yes | Yes | No |
| Conditional logic without code | Yes | No | No |
| Mobile-responsive rendering | Yes | Yes | Yes |
| Version history and restore points | Yes | No | No |
How to migrate from InfoPath — step by step
There is no automated migration from InfoPath. Forms need to be rebuilt. The good news: most simple InfoPath forms can be rebuilt in Forms365 Workspace in under an hour, and the rebuilt form is better than the original.
- 1
Audit your InfoPath forms
List every InfoPath form in your environment. Note which SharePoint list each form is connected to, how many fields it has, what conditional logic it uses, and how frequently it is used. Prioritise high-usage forms first.
- 2
Connect Forms365 Workspace to the same SharePoint list
Install Forms365 Workspace as an SPFx solution in your tenant. Connect it to the same list your InfoPath form was built on. All the list columns are automatically available in the designer.
- 3
Recreate your layout
Drag your fields onto the canvas. Use multi-column tables and section dividers to match your InfoPath layout. InfoPath forms with tabs can use collapsible sections in Forms365 Workspace.
- 4
Recreate your conditional logic
Set show/hide rules, required/optional rules, and calculated field logic using the visual rule builder. InfoPath conditions map directly to Forms365 Workspace conditions — field equals value, show/hide field, mark required.
- 5
Set up automation rules
If your InfoPath form triggered a workflow, recreate the trigger in Forms365 Workspace's automation rules or connect it to an existing Power Automate flow. Forms365 Workspace saves to SharePoint list items, which natively trigger any Power Automate flow on that list.
- 6
Publish and test
Publish the new form and test it with real SharePoint data before retiring the InfoPath form. Forms365 Workspace has a preview mode that shows desktop, tablet, and mobile rendering before you go live.
What to do if you're still running InfoPath
If your organisation still has active InfoPath forms in SharePoint Online after July 14, 2026, those forms are now broken. Users who try to open, edit, or submit an InfoPath form will see an error. The data in your SharePoint list is safe — list items are separate from the form — but the form itself is no longer functional.
The steps are:
- Identify which forms have stopped working by checking your SharePoint lists for inactive form customisations.
- Start a trial of Forms365 Workspace and rebuild your highest-priority form first.
- Test the rebuilt form with a small group before rolling out to all users.
- Work through remaining forms in order of business impact.
Start rebuilding your InfoPath forms today.
14-day free trial. Full access. No credit card required.
Common questions about replacing InfoPath
What replaced InfoPath in Microsoft 365?
Microsoft retired InfoPath on July 14, 2026. The officially recommended replacements are Power Apps (for complex forms) and Microsoft Forms (for surveys). Neither is a like-for-like replacement for SharePoint list forms. Forms365 Workspace is a purpose-built replacement: a no-code designer that deploys inside your tenant and writes directly to SharePoint list columns.
How do I migrate from InfoPath to SharePoint without Power Apps?
There is no automated migration from InfoPath — forms must be rebuilt. Connect your form builder to the same SharePoint list your InfoPath form used, recreate your fields and conditional logic rules, then publish. Most simple InfoPath forms can be rebuilt in Forms365 Workspace in under an hour.
Does any InfoPath replacement support SharePoint Content Types?
Forms365 Workspace supports SharePoint Content Types natively. Power Apps does not support Content Types out of the box for list forms — this is still listed as under review on Microsoft's ideas board as of 2026.
What happened to InfoPath Forms Services in SharePoint Online?
Microsoft retired InfoPath Forms Services on July 14, 2026. InfoPath forms in SharePoint Online no longer open, render, or submit. Organisations with active InfoPath forms need to rebuild them using a supported tool.