Pay-as-you-go is a new way to pay for Power Apps and Power Automate using an Azure subscription, which allows you to get started building and sharing apps without any license commitment or upfront purchasing.
Pay-as-you-go allows you to share apps and Power Automate flows with any user in your organization and then only pay if and when they're used. The pay-as-you-go plan also includes Microsoft Dataverse storage capacity and provides the flexibility to pay for additional storage as you need it.
This plan reduces the overhead of license procurement and lets you manage and split costs across business units by leveraging the cost management reporting capabilities of Azure subscriptions. Pricing information for this plan is available here.
Check out how T-Mobile is innovating with Power Apps and pay-as-you-go: T-Mobile adopts Microsoft Power Platform for fast and powerful low-code development.
Common use cases
Widely distributed apps: Use the pay-as-you-go plan for apps that need to be shared with a large user base with infrequent and/or unpredictable use.
Establish usage patterns: Understand adoption patterns for new apps to determine whether prepaid licenses make financial sense for your business.
Flexible purchasing: Use an Azure subscription for Power Apps and Power Automate to reduce license procurement overhead and consolidate with other service purchases. This is especially helpful if you already have an Azure subscription that you use for other Microsoft services.
How does it work?
In Power Apps, Power Automate, or the Power Platform admin center, you can link environments to an Azure subscription using a billing policy.
Once an environment is linked to an Azure subscription, the usage of apps and any Dataverse or Microsoft Power Platform request usage that goes above the included amounts are billed against the Azure subscription using Azure meters.
You can unlink your environment from the Azure subscription at any time and usage will no longer be billed.
What is a billing policy?
A billing policy creates a link between one or more environments and an Azure subscription. It contains:
- Details of the Azure subscription
- A list of environments that are linked to the Azure subscription
Billing policies can be created in either the Power Platform admin center or within Power Apps and Power Automate. When a billing policy is created, a corresponding Azure resource (called a Power Platform account resource) is created in the Azure subscription associated with that billing policy. Any usage charges for Power Apps, Power Automate, Dataverse, and Microsoft Power Platform requests will appear under the Power Platform account resource on the Azure subscription's bill.
When an environment is linked to Azure via a billing policy, it becomes a pay-as-you-go environment. An environment can only be linked to one billing policy at a time. You can change the policy an environment is linked to, or remove it from a billing policy, at any time. When you remove an environment from a billing policy, it goes back to functioning as a regular environment. Usage of Microsoft Power Platform products in that environment will no longer be billed to Azure.
Billing policies provide flexible options for organizations that are looking to allocate Microsoft Power Platform meter costs across teams and departments. In the example below, the customer has decided to set up Power Platform meter usage for the Marketing team's two environments to be billed to that team's Azure subscription. However, for the Finance team, the customer has decided to set up individual billing policies for the environments of two different sub-teams (Accounting and Auditing), each of which will be connected to a separate Power Platform account resource. This allows the costs for each sub-team to be easily broken out, even though they're both billed to the same Azure subscription. Customers can also leverage Azure resource groups and Azure tags to organize their Power Platform account resources and track and allocate spending.
Submit and view feedback for