I recently had the opportunity to attend as well as speak at the 5th annual Power Platform Community Conference (PPCC) held at the end of October in Las Vegas, USA. It is a multi-day, in-person event focused entirely on Microsoft Power Platform. It brings together product leaders, MVPs, and industry experts who actively build solutions using Power Apps, Power Automate, Power BI, Power Pages, Dataverse, and Copilot. Keynote We heard directly from Charles Lamanna, Executive Vic

You got the Dynamics 365 project. The requirements are clear. More or less. In modern enterprise solutions, it is quite common to have a rich data model with a lot of different tables entwined with each other in various ways. Which naturally creates lookups in forms. This creates connections between records giving the opportunity for a 360-degree view of your customers, leads, opportunities, projects etc. Or in my geeky case of the Avenge 365 app based on Dynamics 365 Sales,

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