
A Power App has three costs: licences for the people who use it, the build, and the upkeep afterwards. If the app only uses standard connectors such as SharePoint, Outlook and Teams, most Microsoft 365 business plans already cover the licence. If it uses Dataverse or a premium connector, each user needs Power Apps Premium, which Microsoft lists at $20 per user per month.
The licence question usually decides the rest, so it comes first.
Do I have to pay for Power Apps licences?
Often not. Microsoft splits apps into two classes. An app that only uses standard connectors is a Standard app, and people can run it under the Power Apps rights included in most Microsoft 365 business plans. An app that uses Dataverse, a premium connector or a custom connector is a Premium app, and everyone who runs it needs a Power Apps licence.
The rule is on Microsoft's page about app license designation (checked November 2026).
| What the app uses | Licence class | Extra licence cost |
|---|---|---|
| SharePoint lists, Outlook, Teams, Approvals, Excel | Standard | Usually none on Microsoft 365 business plans |
| Dataverse | Premium | Power Apps Premium per user |
| A premium connector, such as SQL Server or an HTTP call to another system | Premium | Power Apps Premium per user |
| A custom connector to your own system | Premium | Power Apps Premium per user |
What does Power Apps Premium cost?
Microsoft's Power Apps pricing page (checked 20 November 2026) lists these prices:
| Plan | Price | Notes |
|---|---|---|
| Power Apps Premium | $20 per user per month, paid yearly | Unlimited apps for that user, Dataverse included |
| Power Apps Premium, 2,000 seat minimum | $12 per user per month, paid yearly | Through Microsoft sales |
| Dataverse database capacity add-on | $40 per GB per month, paid yearly | Only if you outgrow the included storage |
| Developer Plan | Free | For building and testing, not for running apps in production |
Microsoft notes that actual prices vary by country and currency, so check the checkout price for yours. As a worked example, 20 people on Premium is 20 × $20 = $400 a month, or $4,800 a year. Put that figure next to the build price before choosing Dataverse.
What drives the price of building one?
The number of screens matters less than people expect. These things move the price:
- Roles. An app where everyone sees everything is quicker than one where staff, managers and contractors each see different records.
- Approvals and reminders. Each sign-off step, deadline and escalation is a flow that has to handle the person who never answers.
- Offline use. Working without signal needs a different data design and more testing.
- Connections to other systems. Reading from an ERP, a payroll system or a property system depends on whether it has a connector or an API, and on how well documented it is.
- Moving existing data. Cleaning years of spreadsheet rows before import is real work, and it is often the part nobody budgeted for.
- Reports. A PDF report emailed after each job is a flow of its own. A management dashboard may be a Power BI job.
For a sense of scale: a single approval workflow, one request type with reminders and escalation, is a fixed price from $1,800 and goes live in two to three weeks. Larger apps are quoted after a short call, once the roles, steps and connections are known.
What does it cost to keep running?
Less than custom software, but not zero. Plan for:
- Licences, if the app is Premium, every month for every user.
- Small changes, such as a new field, a new approver or a new site. A well-built app keeps these in lists and settings, so an admin can make many of them without a developer.
- Microsoft changes. Connectors and features change over time. An app built on standard, supported controls is far less exposed than one held together with workarounds.
- An owner. Someone in your business who knows who to call when a flow stops. Make sure the app and its flows are owned by a company account, not a personal one.
How do I keep the cost down?
Start on SharePoint lists if the data is simple, because that keeps the app Standard. Build one process for one team first and extend it once people use it. Agree a fixed scope in writing before work starts. If you are weighing SharePoint against Dataverse, Dataverse vs SharePoint Lists sets out when the move is worth paying for.
Frequently asked questions
Is Power Apps free with Microsoft 365? Partly. Most Microsoft 365 business plans let people run Standard apps, which use connectors such as SharePoint, Outlook and Teams. Apps that use Dataverse or premium connectors need a Power Apps licence for each user.
Do I pay per app or per user? Microsoft's current pricing page lists Power Apps Premium per user, which covers unlimited apps for that person. Older per app plans may still appear on existing agreements, so check what your tenant already has.
Do people who only view the app need a licence? Yes. Anyone who opens a Premium app needs a licence, even if they only look at records. People who never open the app, such as a customer receiving an emailed report, do not.
Is a Power App cheaper than custom software? For internal tools, usually. You skip hosting, sign-in and security work because Microsoft 365 already provides them. For an app the public will use, custom software or a different platform is often the better fit.
How much does a Power Apps developer charge? It varies with experience and region. A fixed price for a defined scope is easier to budget than an open hourly arrangement, and it puts the risk of overruns on the developer.
Getting a price for your app
Write down the one process you want to fix, who uses it and where the data lives today. Book a 30-minute call and you will leave with a rough figure and whether your app is Standard or Premium. For approval workflows, the approval workflow service has the fixed price and what it includes.
Last updated
- Power Apps
- Licensing
- Small Business
