Session Abstract

Model Context Protocol (MCP) quickly became the thing everybody talks about who is doing AI in the moment and its adoption rate across different tech providers is rapid. Microsoft has embraced it as well and is combining it with an old friend of ours: (Custom) Connectors. In this session, Mats & Daniel will break down the differences between Model Context Protocol (MCP) and traditional connectors in the Power Platform. Attendees will learn how each works, where they fit best, and how they compare. The session includes practical demos showing how to get started with MCP and how it can work alongside connectors—not replace them. It’s aimed at solution architects, developers, and IT leaders looking to modernize how they build integrations. Do not miss this session if you want to get your AI solutions to the next level which will be increasingly connected to other system and working with your data. We will discuss if connectors together with MCP will get us to the true agentification which was promised.

Daniel Laskewitz

Daniel Laskewitz is a Principal Cloud Advocate at Microsoft. Half of his week goes into Copilot Studio, Copilot Cowork, Scout, GitHub Copilot and Microsoft 365 Copilot, usually with something unfinished open on screen. The other half he spends with the people building the same things, in sessions and workshops and in the community, and what they tell him goes back to the product teams. On stage he talks about getting an agent past the demo. Wiring it to real systems with MCP, working out when a plain connector is the better answer, and the part nobody puts in a keynote: making the thing safe to hand to somebody else. He has been speaking since 2015, often with a co-speaker.