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

Let’s get agentic AI to do more things for us, they said. It will all be easier, they said. Well, after watching another Parks and Recreation episode, I truly wanted to put this to the test by solving for the perennial CRM problem; delegation and task assignment. To be perfectly honest, this is a challenge in many business scenarios. Or even personal life! Tasks arise in our head, in a meeting, on the way to work, during a conversation, you name it. Being on the go is always