# Five real replacements for InfoPath forms, and how to pick one

> InfoPath went dark on July 14, 2026. There is no single replacement, and two options the top-ranking articles still recommend are already switched off. Here are the five that work, what each costs, and the four questions that pick between them.

[Home](https://tenantcraft.ca/)  [Insights](https://tenantcraft.ca/insights)  Power Platform

Plan Aug 16, 2026  5 min read

Geri Crroj

Microsoft 365 consultant, Niagara, Ontario

## What hurts

InfoPath Forms Services was removed from Microsoft 365 on **July 14, 2026**. Your forms don’t render and nobody can submit.

Microsoft never shipped a replacement. It split InfoPath’s job across four of its own tools, and a third-party market fills the fifth gap.

Then there’s the trap. Search “InfoPath alternatives” and the top results still recommend **Access web apps**, deleted in 2018, and **Nintex Forms for Office 365**, which stopped opening on **April 2, 2026** when Microsoft retired the SharePoint Add-In model. Custom .NET forms need a farm you no longer have. Check an article’s date before you follow it.

The 5-minute version

1.  **Start at native Lists forms.** Free, and they do conditional branching now. Most surviving InfoPath forms fit here.
2.  **Microsoft Forms is for people outside your tenant.** That is its only job.
3.  **Power Pages is the only one that takes their files.** Microsoft blocks external uploads in Forms at the service level.
4.  **Power Apps is for complex logic**, not a default.
5.  **Third-party products earn their licence on repeating tables.** Nothing native replaces them cleanly.

## What each one actually does

![Comparison table. Native Lists forms: internal only, no external uploads, no repeating tables, no extra cost. Microsoft Forms: works externally, no external uploads, no repeating tables, no extra cost. Power Apps: internal only, attachments and repeating tables possible with work, no extra cost until a premium connector. Power Pages: external including uploads, repeating tables with work, licensed per user or site. Third-party: external and attachments with work, repeating tables supported, from 899 dollars a year.](https://tenantcraft.ca/images/infopath-options-matrix.png)

The four constraints that rule an option out

Everything else is preference. These four decide it.

## 1\. Native Lists forms

The default, and the one people skip because they remember it being useless.

Conditional branching arrived in early 2025. Show or hide questions based on earlier answers, which is what most InfoPath rules did. Add a logo, group fields into sections, mark fields read-only. Header, footer and body take the same JSON formatting you already use on list views.

**Two limits:** internal only, since the form inherits site permissions, and no repeating table.

**Cost:** nothing.

![The branching panel in a native SharePoint list form. A Request type choice field routes each answer to a different follow-up question: Hardware goes to the Hardware item question, Software goes to Software name, and Building access goes to Area requested. The Customise pane on the right shows the fields included on the form.](https://tenantcraft.ca/images/lists-form-branching.png)

Microsoft Lists · Branching panel

One choice field routing three ways, in a live tenant. No Power Apps licence, no premium connector, nothing to maintain outside the list.

## 2\. Microsoft Forms, into a list

One reason to reach for this: the person filling it in doesn’t work for you.

Set **Collect responses** to _Anyone can respond_, then have a Power Automate flow write each submission into a SharePoint list. The list is your record; the form is just the funnel.

**Ceilings:** 200 questions, 4,000 characters per question and answer. Commercial tenants take up to 5,000,000 responses, but summary charts, individual responses and printing stop working past 50,000. GCC High and DoD cap at 50,000 outright.

**The blocker:** Microsoft blocks external respondents from uploading files. It’s a service-level rule, not an admin toggle.

## 3\. Power Apps, customizing the list form

The closest thing Microsoft ships to InfoPath, and the subject of the [rebuild post](https://tenantcraft.ca/insights/infopath-replacement-power-apps): inventory script, triage rubric, InfoPath rules translated to Power Fx.

Use it when native branching can’t express the logic, or the layout genuinely matters. Repeating sections have no direct equivalent; the pattern is a child list plus a gallery.

**Structural limit:** one custom form per list. Different layouts for different departments means conditional visibility inside that one form.

**Cost:** seeded in Microsoft 365 for SharePoint data. Touch a premium connector and every user needs a per-app licence, around $5 USD per user per app per month, or Premium at $14 to $20.

## 4\. Power Pages

For external people who submit documents, or who sign in and check status later. Grant applications, vendor onboarding, permit intake. The [Power Pages comparison](https://tenantcraft.ca/insights/power-pages-vs-sharepoint-sites) covers where it stops making sense.

**Cost:** licensed per authenticated user or per site, and it’s a project, not an afternoon. Right for a few genuinely external forms, wrong for an internal leave request.

## 5\. Third-party products

Worth it when repeating tables or sheer form count cost more in rebuild hours than a licence does.

Plumsail Forms runs about **$899 USD a year**, no per-user cap. Crow Canyon’s NITRO Studio targets InfoPath replacement directly. Nintex Automation Cloud starts near **$15,000 USD a year**, which only makes sense if you’re standardizing on Nintex.

Do the arithmetic. Forty forms with repeating sections at 8 to 12 hours each in Power Apps makes $899 the cheap option.

Ask what framework it's built on

Any SharePoint forms product still on the Add-In model died on April 2, 2026. Confirm the product is SPFx-based, and ask the vendor what happens at the next platform retirement. Nintex Forms for Office 365 customers learned that a product roadmap and a platform roadmap are two different documents.

## How to fix it

Go form by form. Stop at the first yes.

![Decision flow. Question one, someone outside your organization attaches a file, routes to Power Pages. Question two, outside your organization without attachments, routes to Microsoft Forms into a list. Question three, repeating tables and more than a handful, routes to pricing a third-party product. Question four, logic beyond show-and-hide or layout matters, routes to a Power Apps list form. Everything else falls through to a native Lists form with branching.](https://tenantcraft.ca/images/infopath-routing-rule.png)

Routing rule

Most forms fall all the way through, which is the free option.

Run your inventory down that and the forms cluster at the bottom. The ones that survived to 2026 are mostly simple, because nobody had a reason to touch them, and simple is exactly what native Lists forms now handle for nothing.

## Bottom line

Start at native Lists forms and justify every step up from there.

The expensive mistake isn’t picking the wrong tool. It’s rebuilding forty forms in Power Apps when thirty of them worked as list forms with branching, free, with nothing extra to maintain.

Working out which forms go where? The decision tree walks it form by form.

InfoPath Forms Decision Tree

PDF · 7 pages

[Email me the PDF](https://tenantcraft.ca/resources/guides/infopath-forms-decision-tree)

TWENTY MINUTES, NO PITCH

## Tell me what is stuck. I will tell you what it takes.

Same consultant from the first email to the last cutover. If I am not the right fit, I will refer you to someone who is.

[Book a 20-min call](https://tenantcraft.ca/contact) [See published rates](https://tenantcraft.ca/pricing)

---

_Canonical HTML: https://tenantcraft.ca/insights/infopath-alternatives-sharepoint-forms · Agent guide: https://tenantcraft.ca/llms.txt · Site map: https://tenantcraft.ca/sitemap-index.xml_