Document Power BI storage double-reporting caused by consumption field confusion

[Copilot]

Power BI reports show ~2x database storage vs PPAC when measures incorrectly sum both consumption fields or use the wrong one.

Root Cause

The admin_EnvironmentCapacity entity stores two separate metrics from the Power Platform Admin API:

• admin_actualconsumption - matches PPAC values
• admin_ratedconsumption - normalized/rated value using different calculation

Summing both or using ratedconsumption instead of actualconsumption doubles reported storage.

Changes

• User troubleshooting guide (docs/troubleshooting/power-bi-storage-double-reporting.md)

  • Explains field semantics and fix steps
  • Provides correct DAX measure pattern

• Issue response template (docs/ISSUE-RESPONSE-PowerBI-Storage-Double.md)

  • Standardized response for future occurrences

• Maintainer verification guide (docs/VERIFICATION-PowerBI-Storage-Measures.md)

  • Instructions for auditing .pbit templates
  • Common anti-patterns to identify

• Documentation index updates

  • Added references in troubleshooting README and main README

Correct DAX Pattern

Total Database Storage (GB) = 
CALCULATE(
    SUM('admin_EnvironmentCapacity'[admin_actualconsumption]) / 1024,
    'admin_EnvironmentCapacity'[admin_capacitytype] = "Database",
    'admin_EnvironmentCapacity'[admin_environmentdeleted] = false()
)

Notes

Manual verification of .pbit templates needed (binary format). Verification guide provides inspection procedures.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>COE DB size showing incorrect in Powe BI report</issue_title>
<issue_description>Hi Team, I see in admin center the db size is approx 260 gb but in the PowerI report it whows double the space than what it shows in the admin center. Could you please let me know how to fix? It could be a bug ..</issue_description>

<agent_instructions>Investigate why Dataverse storage in PPAC shows ~260 GB while the CoE Power BI report shows roughly double. Provide the supported steps to correct the report (refresh, parameters/filters, model fixes) so storage matches PPAC within expected variance.</agent_instructions>

Comments on the Issue (you are @copilot in this section)

Custom agent used: CoE Custom Agent
Specialized agent for triaging and fixing issues in the CoE Starter Kit. Always consult the official CoE docs and the team’s SharePoint notes first, then mine prior GitHub issues and the CoE Common Responses playbook.

• Fixes COE DB size showing incorrect in Powe BI report #10758

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.