In the last blog post, I covered how Copilot Studio really accesses Dataverse through various lenses with the Dataverse Knowledge Source, Dataverse Connector and Dataverse MCP Server. From the way the core model works, to the way inputs and outputs are managed, schema awareness, CRUD support and bound/ unbound actions. Here is what the summary looked like: Capability Knowledge Source Connector MCP Server Core Model Search/ index based, for retrieval + grounding Deterministic

There’s a moment in every agentic strategy project where you realize: how your agent connects to data matters just as much as what data it sees. Now, coming from the world of Dynamics 365 and Model-Driven Power Apps, Dataverse is the golden data source. So naturally, when there is an ask to create a custom agent which can “speak” the business app’s language, what is the next step? Connect to Dataverse of course! Looking at your metaphorical whiteboard, three (plus a bonus one

Agents! Agents! Agents! It is like the more we say it, more of them come out! Especially in Sales, we have seen an exponential increase not only in agents but also features. Which is fantastic for us Dynamics 365 geeks! Before we get to the heart of this blog post… A short recap of the cool agents available, with some still in preview: Sales Research Agent : (Backed by our old friend Project Sophia) Answers complex questions about our CRM data using natural language and gene