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.
What each one actually does
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.
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: 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 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.
How to fix it
Go form by form. Stop at the first yes.
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.