Field guide · Small business · Microsoft InfoPath

InfoPath replacement for SharePoint Online: rebuild your forms

InfoPath stopped working in SharePoint Online after July 14, 2026, and Microsoft says “there is no migration tool provided,” so every form gets rebuilt. For most small-business forms, the replacement is the SharePoint list’s own form or a Power Apps form on the same list, plus a Power Automate flow for the approval.

Published · Get the PDF

What did Microsoft change, and when?

DateWhat happenedSource
May 18, 2026“Publishing new InfoPath forms or publishing updates to existing forms will be blocked.”Microsoft notice MC616550
July 14, 2026“After July 14, 2026, users will no longer be able to use InfoPath forms in SharePoint Online.”MC616550
July 14, 2026The InfoPath 2013 desktop app reached the end of extended support.MC616550
After July 14, 2026Extended support for InfoPath Forms Services ended on SharePoint Server 2016, 2019 and Subscription Edition.Microsoft SharePoint Blog

If an old form still opens for your team, you still can’t publish a fix to it.

Which replacement fits your form?

OptionGood forWatch for
The list’s own form (Edit form, in any SharePoint list)Show or hide fields based on an answer, group fields into sectionsFormulas can’t use Currency, Calculated, Managed Metadata or multi-select columns
A Power Apps form on the list (Integrate > Power Apps > Customize forms)Read-only fields, field rules, a layout closer to the old InfoPath formUsers given access to only some list items can’t open it
Microsoft Forms plus a Power Automate flowA short request form that sends answers into a listThe Forms connector isn’t available in Power Apps, so a flow does the copying
A Power Automate approval flowReplacing InfoPath’s “submit and email the manager” rulesApprovals that may wait more than 30 days need a different setup
Bring in an outside team (Custom software)Forms with line items, several approval steps, or dozens of forms to moveNeeds time with the people who use the form

How do you rebuild an InfoPath form yourself?

1. Write down what the old form did. List every field, every rule (hide this, require that, fill in a default), who it emailed and where it saved. If the form won’t open, use the list’s columns and a few past submissions. Our guide to mapping how a job really runs shows how to get this from the people who do it.

2. Find every InfoPath form you have. Microsoft points admins to the Microsoft 365 Assessment tool, run with --mode InfoPath. Its Power BI report shows, by site, which lists, libraries and content types use InfoPath, and how recently and how much each is used. The tool needs an Entra app registration, so ask whoever manages your Microsoft 365.

3. Fix the list before the form. Give each field a column of the right type, and use Number, not Currency, for an amount that drives a rule. Put InfoPath repeating tables (one row per item ordered) in a second list, linked back with a lookup column.

4. Try the list’s own form first.

  1. Open any item in the list.
  2. At the top of the form, select Edit form > Edit columns.
  3. Check or uncheck columns to show or hide them, and drag to reorder.
  4. To show a column only for some answers, select the ... beside it, then Edit conditional formula.
  5. Enter a formula such as =if([$Category] == 'Equipment', 'true', 'false'), then select Save.
  6. To group fields into sections, expand Edit form, select Configure layout, choose Body under Apply formatting to, and paste a sections layout from Microsoft’s “Configure the list form” page.

Formulas refer to each column by its internal name, written as [$InternalName].

5. Move to Power Apps if the list form can’t do it.

  1. In the list, select Integrate > Power Apps > Customize forms.
  2. In the tree view, expand the containers, select the form (SharePointForm1) and use Edit fields to choose and order fields.
  3. To make a field read-only, select its card and set Display mode to View. Built-in cards are locked at first: open the Advanced pane and select the button there to manage the card’s properties.
  4. Select File, then Save, then Publish to SharePoint, and confirm.

6. Rebuild the approval as a flow.

  1. In Power Automate, select My flows, then New flow > Automated cloud flow.
  2. Choose the trigger When an item is created - SharePoint, then pick your site and list.
  3. Add Start and wait for an approval, choose an Approval type, and put the manager in Assigned to.
  4. Add a Condition: Responses Approver response is equal to Approve.
  5. On each branch, add Send an email (V2) to tell the requester, and Update item to write the decision to the list.

Type Approve exactly. Microsoft’s connector notes say the responses “Approve” and “Reject” “are case-sensitive.”

What breaks, and how do you check it worked?

  • Some people can’t open the form. The Power Apps form needs at least Read or Restricted View access to the whole list.
  • Approval times look wrong. Approvals timestamps are always shown in UTC.
  • The wrong name appears on approvals. The flow’s creator is always shown in the approval details, so build it under the account you want approvers to see.
  • Layouts won’t save. List form layouts are stored on the list content type, and content types from a content type hub are read-only by default.
  • Lookup rules don’t match. In form conditions, a lookup value reads as 1;#Toronto (ID and text together), so a plain text comparison fails.

To check it worked:

  1. Create, view, edit, save and cancel one test item, as Microsoft advises.
  2. Submit a request as a regular staff member, not the site owner.
  3. Approve one test request and reject another, then confirm both decisions landed in the list.
  4. Compare three past submissions with what the new form shows for the same items.

If the form fed a spreadsheet the whole team edits, see our guide to turning an Excel workbook into a web app.

FAQ

Can I extend InfoPath in SharePoint Online? No. Microsoft said in 2023: “There will not be an option to extend InfoPath Forms Services in SharePoint Online beyond July 14, 2026.”

Is there a tool that converts InfoPath forms to Power Apps? No. Microsoft’s notice says “there is no migration tool provided,” so each form is rebuilt by hand.

Do I need extra licenses for Power Apps forms and flows? Not if they only use standard connectors, such as SharePoint, Approvals and Microsoft Forms. Premium, on-premises and custom connectors need a standalone Power Apps or Power Automate plan.

What happened to the data people already submitted? Open the list and check that past items are there. Export a copy before you change any columns.

We run SharePoint Server, not SharePoint Online. Are we affected? Yes. Microsoft’s extended support for InfoPath Forms Services on SharePoint Server 2016, 2019 and Subscription Edition ended after July 14, 2026.

Sources

Have one problem in mind?

Walk us through it on a free 30-minute call. Within two business days you get a one-page note on what we’d fix first, yours to keep.

Walk us through one problemFree 30-minute call.