Preview: Pay-as-you-go meters

[This article is pre-release documentation and is subject to change.]

If you're using a pay-as-you-go plan, usage of apps and any Dataverse or Microsoft Power Platform request usage that goes above the included amounts are billed against your Azure subscription using Azure meters. The Power Apps per-app meter measures the usage by app. The Microsoft Dataverse capacity add-on meter measures Dataverse usage across database, files, and logs. The Power Platform requests capacity add-on meter measures the number of API calls. As soon as you link your environment to an Azure subscription, all three meters are automatically enabled.

How do meters work?

Meter What is counted? What is billed?
Power Apps per-app The total number of unique monthly active users of each app and portal in a pay-as-you-go environment.
An active user is someone who opens an app/portal at least once in the given month.
Repeat access of an app/portal by a user is not counted. Users with Power Apps per-user licenses are not counted. Users with a Dynamics 365 license that provides access to per user license will not be counted.
$10 per active user/app/month
Dataverse For database storage, any usage above 1 GB per pay-as-you-go environment.
For file storage, any usage above 1 GB per pay-as-you-go environment.
If auditing is enabled, any resulting log storage usage will be counted.
For usage above 1 GB for database: $48 per GB/month
For usage above 1 GB for file: $2.40 per GB/month
For any log usage: $12 per GB/month
Power Platform requests (coming soon) Each user in a pay-as-you-go enabled environment will get a daily entitlement of Power Platform requests based on their license. With the Power Apps per-app meter, you get an entitlement of 6,000 API calls per user/app/day. This will be sufficient for most customers. For those with high-scale scenarios, any Power Platform requests above that entitlement will be counted. 0.00004$ per request/day above the daily entitled limits

For detailed pricing information, see Power Apps pricing.

Note

As of public preview (November 1, 2021), if you link an environment to an Azure subscription, the Power Platform requests meter will not be reported or billed. Users and flows in the environment can consume more than their entitled usage without being throttled or paying for overages. Reporting and billing will be turned on in the weeks following the public preview announcement.

Power Apps per-app meter

The Power Apps per-app meter enables users to use any type of app without needing to have a Power Apps license. The Power Apps per-app meter provides access to both canvas and model-driven apps, and portals for authenticated users.

The Power Apps per-app meter measures the number of unique users who opened the app or a portal at least once in an environment over the course of a month. You're only charged for the unique users who actually opened the app, regardless of how many users have access to it. Users can access the same app any number of times over the course of a month and will only be counted as one unique monthly active user of that app. However, if users run multiple apps, they'll be counted as active users for each app they run that month.

For example, an environment has three apps: App A, App B, and App C. This environment is now enabled for pay-as-you-go pricing:

Note

The prices shown in this example are illustrative only. Your organization's pricing may vary based on your contract with Microsoft.

Environment with three apps

Example of three apps enabled for pay-as-you-go

If a user has a Power Apps per-user license, the user is not counted in the meter. If a user has a Microsoft 365 license, which provides access to Power Apps and is using an app with standard connectors, the user is also not counted in the meter. See below for more on how users are counted in the Power Apps per-app meter.

App with standard connectors App with premium connectors
Unlicensed user Charged via Azure subscription. Charged via Azure subscription.
Unlicensed user but Power Apps per-app license is available in an environment Charged via Azure subscription. App passes are not consumed. Charged via Azure subscription. App passes are not consumed.
User with Power Apps for Microsoft 365 plan Not counted in the meter. Charged via Azure subscription.
User with Power Apps per-user plan Not counted in the meter. Not counted in the meter.

Note

If an environment already has app passes assigned and is enabled for pay-as-you-go, app passes are ignored and not consumed. You can reallocate those app passes to a different environment.

Dataverse capacity meter

Dataverse pay-as-you-go meters let you pay for your usage of all three categories of Dataverse storage (database, log, and file) using an Azure subscription.

When an environment becomes enabled for pay-as-you-go and is linked to an Azure subscription, it stops consuming storage from the tenant-wide Dataverse storage pool. Instead, its consumption is billed to Azure. In pay-as-you-go environments, the first 1 GB of Dataverse database storage and 1 GB of file storage capacity are not billed to Azure. However, any log storage capacity will immediately be billed. Note that log storage capacity is only used if you decide to turn on auditing for an environment.

The measurement of usage for each category of Dataverse storage will happen three times per day (90 measurements per month) at 08:00 UTC, 16:00 UTC, and 00:00 UTC. The usage snapshot in each 8-hour period is then multiplied by 1/90th to get the fractional usage of storage during the measurement period. This fractional usage will be multiplied by the monthly per GB rate and shown in Azure Cost Management. The total amount will be summed and billed based on the customer's Azure billing cycle.

Note

The prices shown in this example are illustrative only. Your organization's pricing may vary based on your contract with Microsoft.

Measured usage above per environment entitlements

Power Platform request meter (coming soon)

Note

As of public preview (November 1, 2021), if you link an environment to an Azure subscription, the Power Platform requests meter will not be reported or billed. Users and flows in the environment can consume more than their entitled usage without being throttled or paying for overages. Reporting and billing will be turned on in the weeks following the public preview announcement.

Each Power Platform license includes a large entitlement of Power Platform requests, designed to be sufficient for most customers and scenarios. For customers with extremely high-scale scenarios, the Power Platform requests meter enables them to scale without getting throttled and only pay for the Power Platform requests used above those entitlements.

For more information on Power Platform requests and the entitlements that are included in each license, go to Requests limits and allocations.

Power Platform request entitlements are structured as daily entitlements (requests/day). In pay-as-you-go environments, users and flows that go above their daily entitlement will be billed to the linked Azure subscription. With the Power Apps per-app meter, you get an entitlement of 6,000 API calls per user/app/day. Note that flows still need to be licensed with a base license (either Power Automate per-user, Power Automate per-flow, or Office).

In the example below, User A is licensed with a Power Apps per-user license and Flow A is licensed with a Power Automate per-flow license. The number of Power Platform requests consumed by User A and Flow B are measured daily and any usage above the daily entitlement is multiplied by a $/request rate and shown in Azure Cost Management. The total amount will be summed and billed based on the customer's Azure billing cycle.

Note

The prices shown in this example are illustrative only. Your organization's pricing may vary based on your contract with Microsoft.

Measured usage above entitlements

Next step

Preview: Set up pay-as-you-go