Suggested by Patrick Munsey – New
Current Behaviour:
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 aren't billed to Azure. However, any log storage capacity is immediately be billed. Log storage capacity is only used if you decide to turn on auditing for an environment.
Recommendation:
One of the main factors for wanting our production environment set to PAYG is to take advantage of the cost savings proposition of the power pages PAYG model for monthly authorized logins. This benefit is negated by the additional data storage costs incurred in the PAYG environment. We are being charged for the full capacity of our produciton environment, less 1GB, despite having over 15GB in available capacity just sitting there not being used in our tenant-wide capacity pool.
I think that being able to consume capacity from the tenant-wide pool prior to PAYG charges being applied would better align with the PAYG value proposition and would benefit businesses wanting to leverage the benefits of the new power pages licensing options.