Dataverse
A cloud-based relational data platform launched by Microsoft in 2016, built on Azure infrastructure. It provides unified storage and management of enterprise data, includes over 200 standard business entities, and is deeply integrated with the Power Platform ecosystem. A plugin supporting the MCP protocol has been introduced for coding agents.
Timeline (last 90 days)
Installing the Copilot for Finance and Operations apps application provides a Copilot plugin that lets Dataverse execute X++ code, which is used when creating custom APIs, and it takes about 1 hour.
MCP currently mainly targets interactive agent scenarios; switching the main flow to a workflow that directly calls Dataverse actions can bypass the limitation that a conversation must be initiated by a person.
Installing the Finance and Operations Virtual Entities app for an environment in the Power Platform admin center brings F&O data entities into Dataverse as virtual tables, and the installation takes about 15 minutes.
Dataverse virtual tables do not store a local copy of the data; instead, they map data entities of an external system (such as F&O) to a local table structure, and reads and writes are forwarded to the external system in real time.
Creating a solution in a brand-new sandbox environment may throw an error because F&O is retrying synchronization of the virtual tables of the vendor collaboration app; the workaround is to adjust the next run time of the CDS virtual entity auto-creation batch job.
For a custom API's plugin type, you need to select Microsoft's InvokeNoCustomAPI plugin, which is the bridge through which Dataverse calls F&O classes.
Setting a custom API's binding type to global corresponds to an unbound action, and calls do not need to specify an entity record as context; if set to entity, a specific record must be associated.
For organizations that already have large amounts of historical systems (such as SAP, Oracle, or self-built ticketing systems), mapping this data into Dataverse and keeping it in sync remains a major engineering challenge at the implementation stage
Dataverse is the unified data storage and modeling service under Microsoft Power Platform, and it is also the underlying data platform for Dynamics 365 Sales and Customer Service
Within the same Dataverse environment, entities such as customers, contacts, opportunities, and cases share the same table structure and permission model, and the accounts a salesperson sees and the tickets a service agent opens are linked by native foreign key relationships
5 more timeline events
All Facts (15)
Installing the Copilot for Finance and Operations apps application provides a Copilot plugin that lets Dataverse execute X++ code, which is used when creating custom APIs, and it takes about 1 hour.
50%UnverifiedMCP currently mainly targets interactive agent scenarios; switching the main flow to a workflow that directly calls Dataverse actions can bypass the limitation that a conversation must be initiated by a person.
50%UnverifiedInstalling the Finance and Operations Virtual Entities app for an environment in the Power Platform admin center brings F&O data entities into Dataverse as virtual tables, and the installation takes about 15 minutes.
50%UnverifiedDataverse virtual tables do not store a local copy of the data; instead, they map data entities of an external system (such as F&O) to a local table structure, and reads and writes are forwarded to the external system in real time.
50%UnverifiedCreating a solution in a brand-new sandbox environment may throw an error because F&O is retrying synchronization of the virtual tables of the vendor collaboration app; the workaround is to adjust the next run time of the CDS virtual entity auto-creation batch job.
50%UnverifiedFor a custom API's plugin type, you need to select Microsoft's InvokeNoCustomAPI plugin, which is the bridge through which Dataverse calls F&O classes.
50%UnverifiedSetting a custom API's binding type to global corresponds to an unbound action, and calls do not need to specify an entity record as context; if set to entity, a specific record must be associated.
50%UnverifiedFor organizations that already have large amounts of historical systems (such as SAP, Oracle, or self-built ticketing systems), mapping this data into Dataverse and keeping it in sync remains a major engineering challenge at the implementation stage
50%UnverifiedDataverse is the unified data storage and modeling service under Microsoft Power Platform, and it is also the underlying data platform for Dynamics 365 Sales and Customer Service
50%UnverifiedWithin the same Dataverse environment, entities such as customers, contacts, opportunities, and cases share the same table structure and permission model, and the accounts a salesperson sees and the tickets a service agent opens are linked by native foreign key relationships
50%UnverifiedThe Power Platform ecosystem has more than 1,500 official and custom connectors, covering systems such as SharePoint, Dataverse, SAP, and Salesforce.
50%UnverifiedCopilot Studio's built-in knowledge sources include public websites, SharePoint, Dataverse tables, and uploaded files, and it also supports connectors and Azure AI Search as knowledge sources.
50%UnverifiedMCP servers come from three sources: built-in (Dataverse, SharePoint), partner (such as Adobe and DocuSign), and custom-built.
50%UnverifiedCopilot Studio allows enterprise users to create custom AI assistants through a graphical interface and connect to data sources such as SharePoint, Dataverse, and external APIs.
50%UnverifiedIn the demo, after an anonymous user queried the beer pong agent, the agent returned 22 contact and account records from Dataverse and was able to generate a CSV or Excel file.
50%