Microsoft Dataverse
by Microsoft
The default data platform for Power Platform and Dynamics 365 apps. Dataverse is a low-code data platform for building applications, automations and agents on common data, security and business logic. It was formerly called the Common Data Service.
Core model
- Tables — business data lives in tables with typed columns and relationships; standard tables cover typical scenarios and custom tables can be added. Older documentation calls tables “entities”.
- Layered security — business units, role-based, row-based and column-based security together control access. Roles grant privileges such as create, read, write, delete, append, assign and share on tables; column security can restrict specific columns even when a user has row access.
- Virtual tables — surface data stored outside Dataverse’s own storage for use in the Power Platform
- Shared by Dynamics 365 — Dataverse and a common layer of admin experiences are the backbone of the Dynamics 365 customer apps
- Agent access — the Dataverse MCP server reached general availability on 15 December 2025, after preview from May 2025. Billing for its tools is separate from storage capacity, and charges apply when agents created outside Copilot Studio use it.
Capacity and licensing
- Billing model — capacity is sold in three categories: database, file and log storage, with add-ons in 1 GB increments
- Copilot Studio default — the September 2026 Copilot Studio licensing guide lists 15 GB database, 20 GB file and 2 GB log as the tenant default; check Microsoft’s current licensing guide for amounts and prices
Getting Dataverse data into analytics
- Link to Microsoft Fabric — creates an optimised replica of Dataverse tables in Delta Parquet, the native Fabric format, stored in Dataverse storage. There is no storage account or Spark pool to run. Tables appear in OneLake as shortcuts; removing a table from the link removes the shortcut and stops sync, and does not delete the table in Dataverse.
- Azure Synapse Link for Dataverse — Microsoft’s transition FAQ says the retirement notice does not apply to Link to Fabric or Synapse Link for Dataverse. The Delta Lake and Parquet export path in Synapse Link is deprecated in favour of Link to Fabric. The Synapse Link name is being retired, and in Power Apps the option now appears as Link to data lake; existing links keep running.
- Parallel use — a Fabric community answer says both links can export from the same environment at the same time
Business Central
Business Central keeps its own data and does not use Dataverse by default. Two ways connect them:
- Virtual tables — Power Apps, Power Automate and Power Pages create, read, update and delete Business Central records in place. The data stays in Business Central, and virtual tables are built on Business Central API pages. Dataverse does not support virtual tables in charts.
- Data sync — copies records between Business Central and Dataverse
- Dual-write is a separate Dynamics 365 finance and operations feature and does not apply to Business Central
Related
- Real-time business context for SMEs on the Microsoft stack
- OneLake and the Fabric data platform
- Microsoft Fabric
- ms-dynamics
- Power BI
- Azure Synapse Analytics
Sources
- What is Microsoft Dataverse? — Microsoft Learn
- Configure your environment and link to Microsoft Fabric — Microsoft Learn
- Transitioning from legacy data integration services to Fabric link and Synapse Link for Dataverse — FAQ
- Power Platform integration with Business Central via virtual tables — Microsoft Learn
- Dataverse MCP Server general availability — Handsontek
- Microsoft Copilot Studio Licensing Guide, September 2026 — Licensing School