Dataverse Capacity Calculator

An interactive web-based calculator for estimating Microsoft Dataverse capacity based on Power Platform and Dynamics 365 product licenses.

OPEN CALCULATOR

Read intro blog post

Features

• Interactive Product Selection: Choose from all major Dynamics 365 and Power Platform products
• Real-time Calculations: See capacity updates instantly as you add products and adjust user counts
• Visual Capacity Gauges: Clear visualization of default vs. per-user capacity allocation
• Detailed Breakdown Table: Line-by-line breakdown of capacity contributions
• Helpful Tooltips: Hover over products to see capacity details
• "How it Works" Guide: Built-in explanation of Dataverse capacity licensing
• Mobile Responsive: Works on desktop and mobile devices
• Print-friendly: Clean output for printing or sharing

Capacity Calculation

How Capacity Works

1. Default Capacity: When you license any Dataverse product, your tenant receives a one-time default capacity allocation. The highest tier product determines this amount.

2. Per-User Accrual: Many products add additional capacity for each licensed user. This stacks across all products.

3. Tier Priority (highest to lowest):

   • D365 ERP Premium (125 GB DB / 110 GB File)
   • D365 ERP Standard (90 GB DB / 80 GB File)
   • D365 CRM (30 GB DB / 40 GB File)
   • Power Platform Premium (20 GB DB / 40 GB File)
   • Power Platform Workload (15 GB DB / 20 GB File)

Calculation Logic

flowchart TD
    INPUT["Input: selected licenses, counts,<br/>add-on packs, PAYG environments"]

    INPUT --> LOOP["For each license entry"]
    LOOP --> LOOKUP{"SKU found<br/>in catalog?"}
    LOOKUP -- No --> ERR["Log error, skip"]
    LOOKUP -- Yes --> CICHECK{"Requires<br/>CI base?"}
    CICHECK -- "Yes, base missing" --> ERR
    CICHECK -- No / base present --> DEFAULT{"Eligible for<br/>default capacity?"}

    DEFAULT -- Yes --> MAXDEF["Update tenant default<br/>max(current, SKU default)"]
    DEFAULT -- No --> ACCRUAL

    MAXDEF --> ACCRUAL{"Accrues<br/>capacity?"}
    ACCRUAL -- No --> NEXT
    ACCRUAL -- Yes --> CAP{"Tenant cap<br/>applies?"}

    CAP -- Yes --> CAPDB["Clamp DB accrual<br/>to remaining cap"]
    CAP -- No --> CLASSIFY
    CAPDB --> CLASSIFY

    CLASSIFY{"License type?"}
    CLASSIFY -- PerUser --> USERACC["Add to per-user accrual"]
    CLASSIFY -- PerApp --> APPACC["Add to per-app accrual"]
    CLASSIFY -- CapacityPack --> PACKACC["Add to pack accrual"]

    USERACC --> NEXT[" "]
    APPACC --> NEXT
    PACKACC --> NEXT
    NEXT --> MORE{"More<br/>licenses?"}
    MORE -- Yes --> LOOP
    MORE -- No --> SUM

    SUM["Tenant pool totals<br/>DB = default + per-user + per-app + pack + add-ons<br/>File = default + per-user + per-app + pack + add-ons"]
    SUM --> PAYG["PAYG environments<br/>1 GB DB + 1 GB File each<br/>(separate from tenant pool)"]

    PAYG --> RESULT["Result: totals, breakdown,<br/>PAYG, errors"]

    ERR --> NEXT

    style INPUT fill:#4f46e5,color:#fff,stroke:none
    style RESULT fill:#059669,color:#fff,stroke:none
    style ERR fill:#dc2626,color:#fff,stroke:none
    style SUM fill:#0284c7,color:#fff,stroke:none

Loading

Development

Prerequisites

• Node.js 18+
• npm

Getting Started

# Install dependencies
npm install

# Start development server
npm run dev

# Build for production
npm run build

# Preview production build
npm run preview

Tech Stack

• React 18 - UI framework
• Vite - Build tool and dev server
• Tailwind CSS - Utility-first CSS framework

Deployment

The site automatically deploys to GitHub Pages when changes are pushed to the main branch via GitHub Actions.

Live Site: https://dataverse.licensing.guide/

MCP Server

This repo also includes a deployable MCP server in mcp-server/.

The MCP implementation uses the same deterministic calculation engine as the web UI, so the capacity numbers stay aligned across:

• the public calculator
• local stdio MCP clients such as VS Code or Claude Desktop
• remote HTTP MCP deployments behind a reverse proxy

The MCP package now exposes two transports:

• src/index.js for local stdio clients
• src/http.js for stateless Streamable HTTP deployments

The hosted HTTP deployment can also expose multiple MCP profiles from the same server, such as:

• a full profile for capable MCP clients
• a narrowed compatibility profile for clients like Copilot Studio

That means other operators can deploy the MCP server on their own infrastructure without depending on the public hosted endpoint, while still preserving a richer API surface for some clients and a safer fallback for others. For setup details, see mcp-server/README.md.

Disclaimer

This calculator provides estimates based on publicly available licensing information (December 2025 values). Always verify actual entitlements in the Power Platform Admin Center.

Resources

• Microsoft licensing guides and docs