The thread's landed on the right conclusion, there's no native "storage by Company/Legal Entity" report in PPAC, since storage reporting stops at the environment and table level. Since Finance & Operations tables are typically partitioned by DataAreaId (the company/legal entity field), here's a practical way to approximate it yourself:
Build a custom estimate using DataAreaId:
Identify your largest tables first In PPAC → Environments → your environment → Resources → Capacity, export the table-level breakdown (as 11manish mentioned). Focus on the top 10-20 tables by size, since storage is almost always concentrated in a handful of transactional tables (ledger, sales lines, inventory transactions, etc.).
Query row counts per company for those tables For each large table, run a grouped count by DataAreaId:
SELECT DataAreaId, COUNT(*) AS RecordCount
FROM YourLargeTable
GROUP BY DataAreaId
This won't give exact bytes, but record count proportion per company is a reasonable proxy when combined with average row size.
Estimate size per company Take the table's total reported size (from PPAC capacity export) and allocate proportionally based on the DataAreaId record count distribution from step 2. Not exact (doesn't account for index/BLOB variance), but close enough for capacity planning purposes.
Access method depends on your environment type
- If you have access to Data Lake export/Synapse Link, run this analysis there without touching production directly.
- If not, this needs read access via SQL/Azure Data Explorer if enabled, or via a Power BI report against exported data.
On licensing, to directly answer your second question:
- Database capacity add-on, if your structured/Dataverse table data is the bottleneck (most common for F&O transactional growth)
- File capacity add-on, if attachments/documents/images are the driver
- Check the Resources → Capacity page in PPAC for your current split across these three pools before purchasing, since buying the wrong capacity type won't relieve the actual constraint. Confirm which pool is actually near its limit first.
This is a manual/custom exercise either way, there's no button that gives you Company-level GB today, but the DataAreaId proportional approach is the most practical way to get a defensible estimate for internal reporting or capacity justification.
