As Dynamics 365 storage capacity is expensive and need to meticulously manage the same is of prime importance, Microsoft is providing a way to allocate the storage capacity amongst the Dataverse environments.
So, here’s a way to allocate capacity between Database, File and Log types for each Dataverse environment and get take corrective actions when the capacity is reached.
Manage Capacity
Given you have correct rights in the Power Platform Admin Center, you’ll be able to see the Capacity under Resources –
- On the left hand menu in Power Platform Admin Center, look for Resources as shown below –

- When you see the list of all the environments, select any one to see the option to go to the Storage Allocation page as shown below.

- Once you are in this page, you’ll see the total consumption of Database, Log and File types across all environments – and you’ll see the button to manage this capacity amongst the environments.

- Now, when I click the Manage Capacity button, I’ll see a list of the environments and whether they are already within capacity or not. I can then select the environment which want to allocate/review the allocated capacity for –

- When I select the environment here, I’ll see that by default nothing has been allocated under this new model – but I can then enter thresholds for each type within the available space and not less than what is already consumed.
By default, the values are blank.
- Now, since I have some numbers and made sure to draw from the available capacity if the thresholds are exceeded, I’ll click save for the consumption meters to show up indicating that the allocation is now saved.

This way, you can keep the environment consumption in check and make other environments take up the unallocated space and take corrective actions.
Best is to keep less used sandbox environments consume lesser space.
Hope this was useful!
Here are some Power Automate posts you want to check out –
- Select the item based on a key value using Filter Array in Power Automate
- Select values from an array using Select action in a Power Automate Flow
- Blocking Attachment Extensions in Dynamics 365 CRM
- Upgrade Dataverse for Teams Environment to Dataverse Environment
- Showing Sandbox or Non Production Apps in Power App mobile app
- Create a Power Apps Per User Plan Trial | Dataverse environment
- Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
- Co-presence in Power Automate | Multiple users working on a Flow
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Call a Flow from Canvas Power App and get back response | Power Platform
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
- Asynchronous HTTP Response from a Flow | Power Automate
- Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
- Converting JSON to XML and XML to JSON in a Flow | Power Automate
Thank you!