Storage capacity entitlement

Microsoft 365, Power Platform, Dynamics 365

Enter the licenses and add-ons a tenant has purchased to model the storage capacity those licenses entitle it to. Figures are an estimate of entitlement only.

Disclaimer: This estimator provides estimates based on publicly available licensing information.

This estimator is not the official Power Platform admin center capacity report.

Use the Power Platform admin center for official reported capacity.

How this estimate works

Show

Per-tenant capacity is granted once by the most generous qualifying base license.
Per-user capacity increases with each qualified licensed user.
Add-on capacity is added to total tenant entitlements and is not multiplied by user counts.
Sandbox add-ons provide 10 GB of Operations Database capacity per environment. For each Tier 4 and Tier 5 environment, qualified F&O user licenses also contribute 0.125 GB (128 MB) of Operations Database capacity. This entitlement is calculated independently for each eligible environment. For example, a customer with 100 qualified F&O user licenses, 2 Tier 4 environments, and 3 Tier 5 environments would receive: Tier 4 environments: 2 × (10 GB + (100 × 0.125 GB)) = 2 × 22.5 GB = 45 GB Tier 5 environments: 3 × (10 GB + (100 × 0.125 GB)) = 3 × 22.5 GB = 67.5 GB Total Operations Database capacity = 112.5 GB (45 GB + 67.5 GB)
Capacity is tracked across:
- Dataverse Database
- Dataverse File
- Dataverse Log
- Operations Database
- Operations File
- Process Mining
AI Builder credits are tracked separately.

Licensing guides

Entitlements are based on the Dynamics 365 Licensing Guide - August 2026.
Entitlements are based on the Microsoft Power Platform Licensing Guide - August 2026.
Entitlements are based on the Microsoft Copilot Studio Licensing Guide - August 2026.

Retirement notices

Note: Operations Database and Operations File entitlements are available only for reporting through December 2025. Beginning January 2026, these SKUs will no longer be available for purchase. Customers MUST transition to purchase corresponding Dataverse Database and Dataverse File SKUs. More Details
Note: Microsoft is retiring AI Builder credits and transitioning AI workloads to Copilot Credits. New AI Builder capacity add-on sales ended in November 2025 for new customers. Seeded AI Builder credits in premium licenses are scheduled to be removed on November 1, 2026. AI Builder functionality continues, but licensing is moving toward Copilot Credits. More Details

About Estimator app

Show

A single-page calculator that turns a list of purchased Microsoft 365, Power Platform, Dynamics 365 Customer Engagement and Finance & Operations licenses into the storage capacity a tenant is entitled to. It runs entirely in your browser, saves nothing and sends nothing anywhere.

What it answers

How much capacity does this license mix entitle us to?
Which offer is actually granting the per-tenant default?
What does adding or removing n seats change?
Does our modelled entitlement agree with the tenant report?

The model in one minute

Capacity is granted several ways, and they are all added together:

Per-tenant capacity — granted once by the single most generous qualifying base license, decided independently for every capacity type.
Per-user capacity — a rate multiplied by every qualified licensed user.
Add-on capacity — added to the tenant total as purchased, never multiplied by user counts.
Sandbox add-ons — 10 GB Operations Database per environment. Tier 4 and Tier 5 add a further 0.125 GB (128 MB) per qualified F&O user license, calculated independently for each eligible environment.

Six pools are tracked: Dataverse Database, File and Log, Operations Database and File, and Process Mining. AI Builder credits are tracked separately.

How to use it

Enter seat counts under User licenses and offers purchased.
Enter purchased gigabytes under Capacity add-ons.
Read the tiles in Licensed capacity summary.
Open Contribution breakdown to see which offer contributed what.
Use Step-by-Step result for the full arithmetic ledger.

Getting the numbers out

Export to CSV on the entitlement result.
Export to CSV on the licenses table doubles as a save file – Import CSV loads it back and restores the estimate exactly.
Download .txt / .md from the step-by-step ledger.
Copy summary for pasting into mail or a ticket.
Print renders a clean, nav-free page to PDF.

Tenant CSV comparison

Upload a tenant capacity entitlement export and the app lines its figures up against this model, splitting each pool into accrued, tenant default and purchased capacity so you can see exactly where the two disagree.

Apply quantities writes the licenses found in the file straight into the tables above.

Know the limits

An estimate of entitlement, not a bill and not consumption.
Not the official Power Platform admin center capacity report.
Trials, promotions, grandfathered offers and negotiated terms are not modelled.
Operations Database and File SKUs retire after December 2025.

Privacy

No network calls, no analytics, no cookies and no localStorage. Everything you type stays in the tab and disappears when you close it, so it is safe to use with real customer numbers.

Where the numbers come from

Rates and tenant defaults are transcribed from the Dynamics 365, Power Platform and Copilot Studio licensing guides linked at the top of this page. Every rule the calculator applies is listed in Assumptions.

Found a discrepancy or a missing offer? Use the Feedback / Issues button in the header. Full documentation lives in the project README.

Licensed capacity summary

Totals recalculate as you type. All capacity is computed in binary units, where 1024 MB = 1 GB | 1024 GB = 1 TB | 1 TB = 1024 GB x 1024 MB. AI Builder credits are an allowance, not storage, and are never added to a capacity total.

Enter a license quantity below to see the breakdown.

Pooled breakdown

Show

The same lines combined across Dataverse and Operations, which is how the database and file pools are actually consumed.

Enter a license quantity below to see the breakdown.

Contribution breakdown

Show

How each capacity pool is made up — the tenant default plus every license that accrues into it.

Enter a license quantity below to see the breakdown.

Selected licenses only

User Licenses and offers purchased

Select a group header to collapse or expand it. Quantities below a license’s minimum seat count still accrue capacity but do not grant the per-tenant default. The AI Builder and Process Mining columns appear only once a selected license accrues them.

		Tenant default granted	Dataverse accrued			Dataverse or Operations accrued		AI Builder	Process Mining	Total from this license
License / offer	Qty	Included per tenant	Database	File	Log	Database	File	Credits	Capacity	Database · File · Log

Pre-paid Capacity add-on licenses and offers

Pre-paid (agreement) capacity add-ons, purchased separately and assigned in gigabytes. Each unit adds capacity directly to the tenant pool it is assigned to. These pre-paid capacity add-ons do not provide any default tenant entitlement and are not multiplied by user license counts. Pre-paid capacity (minimum annual commitment) is granted based on the quantity purchased. Where a SKU specifies a minimum, it represents the minimum purchase quantity, not a user or seat requirement.

Example: If a customer purchases 500 GB of pre-paid capacity add-ons as part of their agreement, the tenant receives 500 GB of additional capacity, regardless of whether the tenant has 10 users or 10,000 users. If the capacity add-on has a minimum quantity of 1,000 GB, the customer must purchase at least 1,000 GB, but no minimum number of user licenses is required.

The quantities entered here are added directly to the totals below, alongside capacity accrued from eligible user licenses.

		Tenant default granted	Dataverse purchased			Operations purchased		AI Builder	Process Mining	Total from this add-on
Add-on / offer - Pre-paid (agreement)	Qty	Included per tenant	Database	File	Log	Database	File	Credits	Capacity	Database · File · Log

Capacity add-on licenses and offers Azure Pay-as-you-go (PayGo)

Azure Pay-as-you-go (PayGo) capacity add-ons are metered monthly through an Azure subscription rather than pre-paid on an annual term. There is no annual commitment and no minimum purchase quantity, so capacity can be increased or reduced month to month as consumption changes.

Once granted, this capacity behaves exactly like a pre-paid add-on: each unit adds capacity directly to the tenant pool it is assigned to, grants no default tenant entitlement, and is not multiplied by user license counts. Only the commercial terms differ.

The quantities entered here are added directly to the totals below, alongside pre-paid add-ons and the capacity accrued from eligible user licenses.

		Tenant default granted	Dataverse purchased			Operations purchased		AI Builder	Process Mining	Total from this add-on
Add-on / offer - Azure Pay-as-you-go (PayGo)	Qty	Included per tenant	Database	File	Log	Database	File	Credits	Capacity	Database · File · Log

Entitlement result

Accrued capacity plus the per-tenant default, broken out by capacity type.

Entitlement result rows only · gigabytes and megabytes in separate columns

Capacity type	Accrued	Tenant incl.	Total entitled	Exact

Enter license quantities above to see the breakdown.

Step-by-Step result — line by line

Plain-text working, step by step, from every purchased license through the per-tenant default to the totals. Database, File and Log are separate pools and are never added together. Switch to markdown tables, or copy and download it straight into email, a ticket, a wiki or a document.

Fixed-width text · safe to paste anywhere

Tenant CSV comparison — Power Platform admin center

Upload a tenant capacity entitlements export (the Power Platform admin center CSV) to check this estimator’s step-by-step calculation against what the tenant was actually granted. The comparison is read-only: nothing on this page changes until you choose to apply the seat counts.

No file loaded

Drop the tenant capacity entitlements CSV here, or select a file Expected columns include Capacity Type, Capacity SubType, SubType Total Capacity, Entitlement Code, License Total Capacity and Paid Enabled. Capacity values are read in MB. The file is parsed in your browser and is never uploaded anywhere.

Assumptions — Background details and context behind the inputs into the estimates Show

Unit base

All capacity is computed in megabytes using 1024 MB = 1 GB, 1024 GB = 1 TB and 1 TB = 1024 GB x 1024 MB (binary throughout). Fractional grants — 250 MB, 500 MB and the 128 MB sandbox uplift — stay exact, so totals reconcile to the megabyte with no rounding. Anything below 1 GB is displayed in MB (250 MB, not 0.244 GB); 1 GB and above is displayed in GB with the exact MB shown alongside. Note: Microsoft capacity calculations may sometimes use decimal calculation, where 1 TB = 1,000 GB, or binary calculations where 1 TB = 1,024 GB. A terabyte figure quoted elsewhere may therefore differ from the one shown here.

First qualifying subscription sets the tenant default

The first base license (subscription) for a Dynamics 365 product includes its default capacity, which is shared per tenant. Default capacity is not cumulative, so additional licenses (either base or attach) do not increase your initial default per tenant capacity. However, each user license accrues additional database and file capacities at no charge per enterprise base license. More Details - Dynamics 365 Licensing Guide - August 2026 - Default subscription capacity included per tenant

Every tenant with a Power Apps, Power Automate, Power Pages or Copilot Studio license receives default capacity. In addition, for each Power Apps, Power Automate, Power and Power Pages license there is additional accrued capacity added to the tenant. More Details - Power Platform Licensing Guide - August 2026 - Dataverse default and accrued subscription capacity entitlements

Every tenant with at least one Copilot Credit purchasing option configured receives default capacity. The first Copilot Studio, Power Apps, Power Automate, Power Pages or select Dynamics 365 subscription provides the one-time default capacity entitlement for the tenant. Additional subscriptions do not add to the tenant’s default capacity. More Details - Microsoft Copilot Studio Licensing Guide - August 2026

The per-tenant default entitlement is granted only once and is not multiplied by the number of licenses purchased.

One qualifying Microsoft 365, Power Platform, or Dynamics 365 offer establishes the Dataverse tenant default.
One qualifying Dynamics 365 Finance and Operations offer establishes the Operations tenant default.

Within each entitlement category, only the highest qualifying offer is used:

The offer with the largest database entitlement wins.
The offer with the largest file entitlement wins.
The offer with the largest log entitlement wins.

This evaluation is performed independently within each product family (Microsoft 365, Power Platform, Power Apps, Power Automate, Power Pages, Copilot Studio, Customer Engagement, and Finance and Operations).

The Included per tenant column highlights in green the entitlement amounts contributed by the winning offer in each category.

Minimum seats

Minimum-seat thresholds gate the tenant default only — 20 seats for F&O base and Premium, 5 for Human Resources. Per-unit accrual applies from the first seat.

No-accrual licenses (0 GB)

Attach licenses, Team Members, and Human Resources Self Service grant access only and accrue no storage. They are listed for clarity but add nothing to the total.

Per-user accrual (Database / File GB)

F&O Premium 10 / 10 · F&O base 5 / 5 · HR (Not including Self Service) 1 / 2 · Activity 1 / 2 · Device 2 / 3. Activity is the only light-user tier that accrues. Dataverse apps accrue 250 MB–15 GB database and 2–35 GB file per USL.

Human Resources

Human Resources Self Service is a distinct limited-use/additional-user license and does NOT include full-user rights for Human Resources. Self Service is neither a Base license nor an Attach license, and Self Service does NOT include storage entitlements and is NOT included in the Sandbox Uplift calculations for Tier 4 / Tier 5 environments.

Commerce Scale Units

Each unit grants device rights — Basic 65 · Standard 225 · Premium 500 devices — and each device accrues 2 GB Operations Database / 3 GB Operations File. Counted per unit, so 2× Basic = 130 devices.

Sandbox add-ons

Each tier adds 10 GB tenant-wide Operations Database per environment. Tier 4 and Tier 5 additionally accrue 128 MB (0.125 GB) of Operations Database only per qualified F&O user license, per environment — the uplift does not add File capacity. The qualified F&O USL base is the combined seat count of Commerce, Finance, Human Resources, Project Operations, Supply Chain Management, Finance Premium and Supply Chain Management Premium — it is shown live on the Sandbox add-ons group header and itemised in the Step-by-step result. Attach licenses, Team Members, Operations – Activity, Operations – Device, Commerce Scale Units, Human Resources Self Service licenses and all Customer Engagement licenses are excluded, and the 20-seat minimum does not apply to this count.

Capacity add-ons

Purchased capacity is entered under Pre-paid Capacity add-on licenses and offers, which is listed separately from the user licenses because it behaves differently: each unit adds 1 GB straight to the pool it names, no per-tenant default is granted, and nothing is multiplied by a user count. Add-on capacity is included in every total, tile and export alongside accrued capacity. A minimum on an add-on is a minimum purchase quantity, not a seat gate: Dataverse Database Capacity Tier 2 trades a 1,000 GB minimum order for a lower per-GB price but accrues identically to the 1 GB SKU, so entering less than 1,000 still counts the capacity and only flags that the order is too small. The AI Builder add-on grants 1,000,000 service credits per add-on and no storage. Operations Database and Operations File add-ons are purchasable only through December 2025.

Storage Entitlement Pooled as of December 2025

Dataverse Database and Operations Database capacity entitlements are pooled together and consumed Database gigabytes (Consumed) is against the shared “Dataverse or Operations” Database storage pool. Dataverse File and Operations File capacity entitlements are pooled together and consumed File gigabytes (Consumed) is against the shared “Dataverse or Operations” File storage pool. F&O has no Operations Log; log capacity is Dataverse only.

AI Builder credits are being retired

Microsoft is retiring AI Builder credits and transitioning AI workloads to Copilot Credits. New AI Builder capacity add-on sales ended in November 2025 for new customers. Seeded AI Builder credits in premium licenses are scheduled to be removed on November 1, 2026. AI Builder functionality continues, but licensing is moving toward Copilot Credits.

Process Mining capacity

Process Mining capacity is a standalone pool. It is not pooled with Dataverse or Operations Database, File or Log. Only Power Automate Process Mining accrues it, at 100 GB per USL, and no license grants a Process Mining per-tenant default. It can also be bought outright through the Process Mining capacity add-on.

Scope

This tool reports licensed entitlement only — the capacity a tenant is granted. It does not model actual consumption, overage or cost. Compare the totals above against a customer provided screenshot of Power Platform admin center to assess whether additional capacity via USL/add-ons are required to be purchased by the customer.

Policy basis

Basis is the following three licensing guides: 1) Dynamics 365 Licensing Guide — “Capacity” section; 2) Microsoft Power Platform Licensing Guide; 3) Microsoft Copilot Studio Licensing Guide. Estimation only; the Microsoft 365 admin center is authoritative for billed capacity.

Tenant CSV comparison

The tenant capacity entitlements export reports one row per service plan per capacity subtype. A Base row is a per-tenant default and the tenant receives only the largest one, which is the same winner-takes-the-category rule this tool applies; Incremental rows are accrued per licensed unit and add together; AddOn rows are separately purchased capacity, which is compared against the quantities entered under Pre-paid Capacity add-on licenses and offers. The export pools Dataverse and Operations into single Database and File figures, so they are compared against the pooled rows rather than the four separate pools. A service plan sold under more than one SKU repeats its seat count on every row, so seats are deduplicated per SKU and then added, while its base grant is taken once. Seat counts are only written into the estimator when Apply quantities to the estimator is pressed, and only for plans matched by name or by identical rates — bundled plans and closest-match guesses are left out. Purchased capacity is applied instead to the matching offer under Pre-paid Capacity add-on licenses and offers, one unit per gigabyte.

Tests

Every calculation in this estimator is pinned by an automated regression suite that drives the page in a real browser, in both light and dark themes. These are the results of the latest run.

Test scripts, result reports and a sample step-by-step artifact folder

Suite	Result