How much does Power Apps development cost in Australia?

What are the two cost lines in a Power Apps project?

Every Power Apps project has a build cost, paid once, and a licence cost, paid every month for every user. Buyers usually see the first in a consultant’s quote and the second months later in a Microsoft invoice. Budget both from the start.

Cost line	What it covers	How it scales
Build	Design, building screens and logic, connectors, testing, deployment, training	With complexity: data model, integrations, approvals, number of apps
Licences	Power Apps for each user, plus Power Automate, Dataverse capacity and Power Pages where used	With users and usage, and with Microsoft’s price changes

Whether you need standalone licences at all is the first question, because some apps run on Microsoft 365 licences you already pay for.

Which Power Apps licence applies to your app?

The connectors and data store your app uses decide the licence, not how complex it looks. Microsoft’s licensing FAQ says customers can run apps that extend Microsoft 365 using standard connectors on their Microsoft 365 licences. It also says a standalone Power Apps or Power Automate licence is required for premium, on premises and custom connectors, and that users of apps running on Dataverse need a standalone licence. The SQL, Azure and Dynamics 365 connectors are classified as premium.

Option	Listed price at the time of writing (ex GST)	When it applies
Microsoft 365 rights	Included in your Microsoft 365 plan	Apps on SharePoint lists or other standard connectors
Power Apps Developer Plan	Free	Building and testing in a non production environment only
Power Apps Premium	AU$29.90 per user a month, paid yearly	Unlimited apps per user, premium connectors, Dataverse
Power Apps Premium (2,000 seat minimum)	AU$18.00 per user a month, paid yearly	Very large organisations
Pay as you go	Billed through Azure by usage	Seasonal or occasional users
Per app plan	Through CSP only for new customers	One app per user licence; no longer sold to new Enterprise Agreement customers since 2 January 2026

A simple app on SharePoint lists for staff who already have Microsoft 365 can therefore cost only the build. The moment it needs Dataverse, a SQL database or a custom connector to your own API, every user needs Premium or an equivalent.

What changes on 1 January 2027?

Power Apps Premium list prices rise by US$2 per user a month from 1 January 2027, the first list price increase in more than five years according to Microsoft. Its announcement of 9 September 2026 sets out the change:

Plan	US list price before 1 January 2027	From 1 January 2027
Power Apps Premium	US$20	US$22
Power Apps Premium (2,000 seat minimum)	US$12	US$14

Existing subscriptions keep their price to the end of their term. The new price applies to new purchases, renewals and coterminations with a term beginning on or after 1 January 2027, and other plans are not part of this change. Microsoft had not published updated AUD prices when we checked. For budgeting, this page assumes the AUD price rises in proportion, by 10%, to about AU$32.90. That is our assumption, not a Microsoft figure. If you are close to a renewal, ask your licensing partner whether renewing before 1 January locks in the current price for your term.

What do Power Platform developers cost in Australia?

Power Platform consultants charge in the same band as other senior developers, and agency rates are higher than contractor rates. We found no published Australian rate card specific to Power Platform. As anchors, Re:Sourced’s July 2026 guide puts senior software contractors in Sydney at $800 to $1,100 a day ex GST, with specialists to $1,300, and Conduct puts small and medium Australian agencies at $123 to $330 an hour. This page converts effort at an assumed blended agency rate of $1,100 to $1,500 a day. Our developer rates guide has the wider picture.

What you are paying for is less the screens than the data model, the connectors and the governance: environments, data loss prevention policies and a deployment process from test to production.

What do typical Power Apps builds cost?

Three bands cover most work. They are indicative market ranges, not quotes, and exclude licences.

Build	Typical scope	Indicative range (AUD, ex GST)
Simple canvas app	SharePoint lists, standard connectors, a few screens, one approval flow	$5,000 to $20,000
Model driven app on Dataverse	Relational data, roles, premium connectors, approvals, reports	$30,000 to $90,000
Multi app solution	Several apps, custom connectors to your APIs, Power Pages for external users, deployment pipelines across environments	$100,000 to $250,000

The simple band is where Power Apps shines: replacing a spreadsheet or paper form for a team that already lives in Microsoft 365. Our guide to replacing Excel or Access with a web app covers that decision from the other side.

What hidden costs should you budget for?

Four costs often appear after go live: Power Automate licences, Dataverse capacity, environments and support.

• Power Automate. Flows inside a Premium app’s context are covered, but standalone automation may need Power Automate Premium, listed at AU$22.40 per user a month, or Power Automate Process at AU$224.50 per bot a month, both paid yearly.
• Dataverse capacity. Microsoft’s pricing page lists 250 MB of database capacity with each Premium licence. Extra database, file and log capacity is bought per GB at the tenant level and is shared across environments.
• Environments and governance. Development, test and production environments, data loss prevention policies and a deployment pipeline are what keep a Power Platform estate from sprawling. They take consultant days to set up.
• Support. Someone has to own the apps when the person who built them moves on. Budget a support arrangement, roughly 15 to 20% of the build each year as for other software.

What is the five year total against a custom web app?

At 20 users Power Apps is cheaper over five years; at 200 users the licences make it roughly twice the cost of a custom web app. This hypothetical model driven app has the same scope either way. Power Apps build $60,000; custom web app build $110,000 because the platform’s ready made pieces must be built. Support at 15% of build a year on both; hosting for the custom app at an assumed $500 a month. Licences at AU$29.90 for year one and the assumed AU$32.90 for years two to five. All users already have Microsoft 365, so single sign on through Entra ID is available to both, as explained in our Entra ID single sign on guide. It is illustrative arithmetic, not a quote.

Option	Build	Five years of licences	Five years of support and hosting	Five year total (AUD, ex GST)
Power Apps, 20 users	$60,000	(20 × $29.90 × 12) + (4 × 20 × $32.90 × 12) = $38,760	5 × $9,000 = $45,000	$143,760
Power Apps, 200 users	$60,000	(200 × $29.90 × 12) + (4 × 200 × $32.90 × 12) = $387,600	$45,000	$492,600
Custom web app, any user count	$110,000	None	5 × ($16,500 + $6,000) = $112,500	$222,500

The break even in this example sits at about 60 users: at 60, the Power Apps total is $221,280 against $222,500 for the custom app. Below it, Power Apps wins on cost and speed. Above it, the per user fee dominates, and a custom app also avoids being tied to Microsoft’s future price changes. If the app could run on standard connectors and Microsoft 365 rights, the licence column disappears and Power Apps wins at any size. Our low code vs custom guide covers the non cost factors, such as performance limits and who can maintain the app.

How can you keep Power Apps costs down?

Design the data and connectors to stay within the cheapest licence that does the job.

1. Start on SharePoint lists and standard connectors if the data volume and security model allow it.
2. Move to Dataverse only when you need relational data, row level security or scale, and accept the Premium cost knowingly.
3. Count users realistically: occasional users may suit pay as you go.
4. Set up environments and data loss prevention policies at the start, not after the tenth app.
5. Document every app and flow, with an owner, so support doesn’t depend on one person.
6. Review licence assignments every quarter. Staff who left or no longer use an app are a common source of waste, and auto claim policies assign licences automatically when someone opens an app.

If you already have apps built by a staff member who has since left, start with an inventory of apps, flows, connectors and owners before adding anything new. It is often the cheapest piece of work with the biggest effect on the licence bill.

How AWLabs approaches Power Apps decisions

The first question in a 15 minute Development Consult is whether Power Apps, an automation tool or a custom app fits your users and data. If a build is warranted, a paid Discovery Audit maps users, data, connectors and licences, and the fee is credited in full against the build. You then get a fixed price Schedule of Work with three options, The Minimum, The Recommended and The Complete, with licence assumptions written down. Senior engineers lead every build. See our workflow automation service and internal tools guide.