{"id":18977,"date":"2022-03-08T17:30:00","date_gmt":"2022-03-09T01:30:00","guid":{"rendered":"https:\/\/newed.any0.dpdns.org\/en-us\/power-platform\/blog\/power-apps\/announcing-the-general-availability-of-pay-as-you-go-for-power-apps\/"},"modified":"2025-06-11T07:50:41","modified_gmt":"2025-06-11T14:50:41","slug":"announcing-the-general-availability-of-pay-as-you-go-for-power-apps","status":"publish","type":"post","link":"https:\/\/newed.any0.dpdns.org\/en-us\/power-platform\/blog\/power-apps\/announcing-the-general-availability-of-pay-as-you-go-for-power-apps\/","title":{"rendered":"Announcing the general availability of pay-as-you-go for Power Apps"},"content":{"rendered":"

We are pleased to announce the general availability of a new and more flexible way to pay for Power Apps<\/a> and related Power Platform services. Customers now can use an Azure subscription to cover their Power Apps usage and Dataverse capacity costs based on actual usage.<\/p>\n

Register to join us for a Power Apps pay-as-you-go webinar on March 22, 2022<\/strong><\/a><\/p>\n

Historically, low-code platforms have required customers to figure out their licensing needs in advance \u2013 often involving time-consuming procurement processes negotiated between developers, makers and IT professionals. While there are many benefits to the scale and predictability of user-based<\/strong> licensing, several scenarios today require the agility of a usage-based<\/strong> model. With deep roots in both Microsoft 365 as well as Azure, Power Platform is uniquely equipped to offer customers both options.<\/p>\n

With the new pay-as-you-go plan, customers only pay for what they use, giving them more flexibility to get started with low code with low risk and then scale their investments over time based on the usage patterns of their solutions.<\/p>\n

\"Chart<\/p>\n

Great for developers building Power Apps that leverage Azure services<\/h4>\n

The pay-as-you-go option for Power Apps is a great solution for developers who are already using Azure subscriptions to pay for the cloud services they need for their applications. Let\u2019s say you are planning to build a Power Apps mobile app<\/a> that leverages Dataverse as well as a set of Azure-hosted APIs. Today you would need to purchase Power Apps licenses from Microsoft or a partner, and allocate those licenses before deploying your app , and also pay for the Azure services you are using with your Azure subscription. Now, with Power Apps pay-as-you-go you can simply use the same Azure subscription you are using to pay for your Azure services to pay for Power Apps as well.<\/p>\n

Test the waters<\/h4>\n

When building a new app it is often tough to predict how many users will want to use it, making it hard to forecast your licensing needs in advance. Now you can start with the pay-as-you-go option to gauge usage patterns then determine whether purchasing a pre-paid Power Apps subscription plan<\/a> makes sense.<\/p>\n

Only pay when users use your apps<\/h4>\n

Let\u2019s say you have created an app (or set of apps) that you need to share with a large set of users in your organization, but which you expect will only be used by a varying subset of those users on an occasional basis. In this instance it may be more economical to leverage Power Apps pay-as-you-go instead of purchasing pre-paid Power Apps subscription plans for every user you share the app with.<\/p>\n

Share costs across your organization<\/h4>\n

Many organizations want to allocate software license costs to the department or team that used the licenses. \u00a0Power Apps pay-as-you-go makes this possible by letting teams pay for Power Apps using Azure subscriptions linked to their own departmental budgets, and by providing the option to use Azure Cost Management and Azure tags to visualize and divide up costs<\/a>.<\/p>\n

\u00a0<\/p>\n

How it works<\/h2>\n

\"Graphic<\/p>\n

To take advantage of Power Apps pay-as-you-go simply link the environment containing your apps to an Azure subscription. Usage of Power Apps and Dataverse in that environment will then be billed to your subscription using a new set of Azure meters:<\/p>\n