We would like to request an improvement to the Dataverse capacity warning email experience in Power Platform admin center.

In our scenario, administrators received Dataverse capacity warning emails for the Default environment after File capacity usage appeared to increase unexpectedly. After review, Microsoft Product Group confirmed that this behavior was related to a recent change in how Dataverse capacity is reported. Some existing system data that was previously shown under other storage categories is now being reported under File capacity.

Because of this reporting change, File storage usage may appear to increase in Power Platform admin center. However, this does not necessarily mean that new data was suddenly added to the environment or that a separate background process is unexpectedly consuming more storage. The same existing data is now being presented under a different storage category.

This warning email experience can create confusion and concern for administrators because it may appear as though there is a new storage issue, new business risk, or urgent action required, even when the change is mainly related to how storage is categorized and reported.

We would like Microsoft to improve the Dataverse capacity warning email experience so that administrators can better understand why the warning was triggered. Possible improvements could include:

1. Adding clearer explanation in the warning email when the increase is caused by a reporting or categorization change.

2. Providing more details in Power Platform admin center about which storage category changed and why.

3. Providing an option to suppress, acknowledge, or reduce repeated warning emails when the behavior is already understood.

4. Providing clearer documentation or in-product messaging for cases where existing system data is reclassified under File capacity.

5. Allowing administrators to delegate capacity warning notifications to specific recipients or admin groups.

This improvement would help administrators avoid unnecessary concern, reduce support cases, and better understand whether a capacity warning requires immediate action or is related to a reporting/categorization update.