Alternatives to Power Apps for intranet tools
Last updated:
Power Apps is a capable platform and it is included with Microsoft 365 for standard connectors. It is also, for a lot of intranet requirements, the wrong shape — and the reasons are specific rather than a matter of taste.
An app embedded on a SharePoint page renders inside its own container: it does not inherit the site theme, it has its own loading behaviour, and it visibly reads as an application dropped into a page rather than part of it. Premium connectors are licensed per user per month, which turns a small tool into a recurring cost as adoption grows. And apps concentrate in the hands of the few people who build them, which makes those people a queue.
The five realistic alternatives, in the order worth trying them: JSON list formatting, native web parts, a no-code component platform, Power Automate without an app, and bespoke SPFx.
The five, compared
| Option | Cost | Looks native? | Who maintains it |
|---|---|---|---|
| JSON list formatting | €0 | Yes | Any site owner |
| Built-in web parts | €0 | Yes | Any page author |
| No-code component platform | Flat per tenant | Yes | The person who described it |
| Power Automate, no app | €0 with standard connectors | No UI at all — that is the point | The flow owner |
| Bespoke SPFx | €3,000–8,000 per component | Yes | Whoever wrote it, while they are still there |
| Power Apps (for reference) | €0 standard; ~€19/user/month premium | No — embedded container | The maker |
The looks native column matters more than people expect. Intranet adoption is largely about whether a tool feels like part of the intranet, and an embedded app that loads separately with its own spinner tells every user, every time, that it is a bolted-on thing.
When each one is right
- JSON formatting — the requirement is a list that needs to look better and behave slightly smarter. Free, instant, no approval. Start here, always.
- Native web parts — news, documents, links, highlighted content, embedded video. If Microsoft ships it, use theirs.
- A no-code component platform — you need trackers, dashboards, directories and link panels that read your lists, look native and can be changed by the person who wanted them. A flat cost per tenant instead of a per-app licence.
- Power Automate alone — the requirement is a process, not a screen: approvals, notifications, scheduled updates. People often build an app when what they needed was a flow on top of a formatted list.
- Bespoke SPFx — genuinely unusual logic, a real external integration, or a regulated process. This is where the money is well spent.
And to be fair to Power Apps: it is the right answer when you need a real application — offline capability, a mobile app, complex multi-screen data entry, or a Dataverse-backed model. Trying to force those into any of the alternatives above is the mirror image of the mistake this page is about.
The licensing trap worth understanding
The most expensive Power Apps surprises come from connectors, not from the platform. The distinction:
| Standard connectors | Premium connectors | |
|---|---|---|
| Examples | SharePoint, Outlook, Teams, OneDrive | SQL Server, Dataverse, custom connectors, HTTP |
| Included with Microsoft 365 | Yes | No |
| Extra cost | €0 | ~€19 per user per month |
| Charged for | — | Every user who opens the app, not just the builder |
The trap is that a proof of concept is built on standard connectors, then one requirement pulls in a premium one, and the cost silently becomes a per-head monthly bill across everyone who touches the tool. Check the connector list before you build, not after the pilot succeeds. The full side-by-side is in Sharelio vs Power Apps.
Frequently asked questions
Is Power Apps free with Microsoft 365?
For standard connectors, yes — including SharePoint, which covers a lot. Premium connectors such as SQL Server, Dataverse, HTTP and custom connectors need a separate licence, charged per user per month for everyone who uses the app. That distinction is where budgets get away from people.
Why do embedded Power Apps look out of place on a SharePoint page?
Because they render inside their own container rather than as part of the page. They do not inherit the site theme, they size independently and they load separately. It is a technically sound design and a visible one — and on an intranet, whether a tool feels native has a measurable effect on whether people use it.
Can we replace an existing Power App with something simpler?
Often, yes, and the test is simple: if the app is essentially a list with a nicer front end, a formatted view or a native-looking component will do the same job with less to maintain. If it has multi-screen data entry, offline use or non-SharePoint data behind it, keep the app — that is what it is for.
What about Power Pages or Dataverse?
Different problems. Power Pages is for external-facing sites, which is a separate concern from an internal intranet tool. Dataverse is worth it when your data genuinely outgrows SharePoint lists — relational integrity, large volumes, strict schemas — and it brings its own licensing. For a tracker that lives happily in a list, both are more machinery than the requirement needs.