Microsoft Power Apps pay-as-you-go (PAYG) pricing model
Microsoft have recently made Power Apps available under a pay-as-you-go (PAYG) model, alongside the traditional “per user”/ “per app” options. The rationale behind Power Apps pay-as-you-go appears to be so Redmond can help organisations digitally transform faster while also reducing wasted software spend.
How it works
To take advantage of the PAYG model, you connect the relevant Power Apps environment to an Azure subscription. You then pay for usage via the following three meters:
1. Power Apps per-app PAYG
Here, you pay when a user runs an app – rather than the existing model of allocating licenses beforehand and seeing them consumed based on apps being shared rather than run.
An active user is, to Microsoft, someone who opens an app and/or a portal at least once a month. The cost is $10 per active user per app per month.
2. Dataverse PAYG
There are three areas of spend here:
- Database storage
- File storage
- Log storage (only used if auditing is turned on)
You get 1GB of database storage and 1GB of log storage included with each linked environment. Use over the free amount is charged at:
- Database – $48 per GB per month
- File – $2.40 per GB per month
- Log – $12 per GB per month
3. Power Platform Requests PAYG
This is the new name for API calls and, as standard, you get 6,000 API calls per user per app per day – Microsoft believe this will be enough for most users. If it isn’t, any additional API calls are charged at $0.00004 per request per day.
Note that the requests example includes both Power Apps and Power Automate.
These new meters will be available within Azure Cost Management, meaning costs can be tracked, budgets can be set, and resources can be tagged.
This has the potential to give organisations much greater insight into Power Apps usage that is currently possible with any ITAM tool.
For some organisations, particularly those where Cloud cost management / FinOps is stronger than ITAM, this new PAYG approach may be the preferred approach – giving better insights and more control. Where it makes sense, organisations can use both the per user and PAYG models simultaneously to best serve the needs of the user base.
About Rich Gibbons
A Northerner renowned for his shirts, Rich is a big Hip-Hop head, and loves travel, football in general (specifically MUFC), baseball, Marvel, and reading as many books as possible. Finding ways to combine all of these with ITAM & software licensing is always fun!
Connect with Rich on Twitter or LinkedIn.