https://github.com/jukkan/dataverse-capacity
Calculator for the Dataverse capacity you get from different Microsoft product licenses.
https://github.com/jukkan/dataverse-capacity
copilotstudio dataverse dynamics365 licensing lowcode powerplatform software-licensing
Last synced: 26 days ago
JSON representation
Calculator for the Dataverse capacity you get from different Microsoft product licenses.
- Host: GitHub
- URL: https://github.com/jukkan/dataverse-capacity
- Owner: jukkan
- Created: 2025-12-01T20:25:19.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2026-04-20T10:53:48.000Z (about 1 month ago)
- Last Synced: 2026-04-20T12:40:36.468Z (about 1 month ago)
- Topics: copilotstudio, dataverse, dynamics365, licensing, lowcode, powerplatform, software-licensing
- Language: JavaScript
- Homepage: https://dataverse.licensing.guide/
- Size: 262 KB
- Stars: 5
- Watchers: 0
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Dataverse Capacity Calculator
An interactive web-based calculator for estimating Microsoft Dataverse capacity based on Power Platform and Dynamics 365 product licenses.
[**OPEN CALCULATOR**](https://dataverse.licensing.guide/)
[Read intro blog post](https://licensing.guide/december-2025-dataverse-default-capacity-changes-illustrated/)
## 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
```mermaid
flowchart TD
INPUT["Input: selected licenses, counts,
add-on packs, PAYG environments"]
INPUT --> LOOP["For each license entry"]
LOOP --> LOOKUP{"SKU found
in catalog?"}
LOOKUP -- No --> ERR["Log error, skip"]
LOOKUP -- Yes --> CICHECK{"Requires
CI base?"}
CICHECK -- "Yes, base missing" --> ERR
CICHECK -- No / base present --> DEFAULT{"Eligible for
default capacity?"}
DEFAULT -- Yes --> MAXDEF["Update tenant default
max(current, SKU default)"]
DEFAULT -- No --> ACCRUAL
MAXDEF --> ACCRUAL{"Accrues
capacity?"}
ACCRUAL -- No --> NEXT
ACCRUAL -- Yes --> CAP{"Tenant cap
applies?"}
CAP -- Yes --> CAPDB["Clamp DB accrual
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
licenses?"}
MORE -- Yes --> LOOP
MORE -- No --> SUM
SUM["Tenant pool totals
DB = default + per-user + per-app + pack + add-ons
File = default + per-user + per-app + pack + add-ons"]
SUM --> PAYG["PAYG environments
1 GB DB + 1 GB File each
(separate from tenant pool)"]
PAYG --> RESULT["Result: totals, breakdown,
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
```
## Development
### Prerequisites
- Node.js 18+
- npm
### Getting Started
```bash
# 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/](https://dataverse.licensing.guide/)
## MCP Server
This repo also includes a deployable MCP server in [`mcp-server/`](./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
Public hosted endpoints for this repo:
- Health: `https://mcp.licensing.guide/health`
- Full MCP profile: `https://mcp.licensing.guide/mcp`
- Copilot Studio compatibility profile: `https://mcp.licensing.guide/copilot-mcp`
Use `https://mcp.licensing.guide/mcp` for capable MCP clients and `https://mcp.licensing.guide/copilot-mcp` for Copilot Studio.
The separate Copilot Studio profile exists because the initial Copilot Studio connection completed handshake traffic against the full `/mcp` endpoint but did not surface tools, while server logs confirmed successful requests from the Copilot Studio client. The working conclusion was that Copilot Studio was more sensitive to the richer nested schemas on the full profile, so the safer fix was to add a narrowed compatibility profile instead of weakening the main MCP surface for other clients.
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`](./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](https://admin.powerplatform.microsoft.com/).
## Resources
- [Microsoft licensing guides and docs](https://licensing.guide/resources/)