The death of BizApps and the rise of the agentic Power Platform

Sometime last summer, it started to dawn on me that business applications as we know them might soon be a thing of the past.

I had been experimenting with the Model Context Protocol for a while, building custom agents that read and wrote to Dataverse directly - no UI in between. Talking to my business application in natural language, with MCP doing the plumbing, was unexpectedly delightful - and surprisingly productive.

Declarative Agents with Work IQ MCP Servers

It has been a while since I last looked into Agent 365 SDK, and since then a couple of interesting things have happened.

Dataverse MCP Server revisited, agent context reduction strategies and the future of BizApps

It has been a while since I last tried the Dataverse MCP Server. Last summer, when it was in preview, I experimented with it extensively and posted my experiences to LinkedIn and to my blog:

• In this LinkedIn post, I showed how the Dataverse MCP Server can be used from Claude Code, Claude Desktop and Gemini CLI.

Agent 365 notifications

In my last blog post I explained in detail how to use the Agent 365 CLI to set up the infrastructure necessary to deploy a custom agent to Agent 365. So if you are just starting out, that post is a great way to get the prerequisites in place to be able to start developing your agent.

In this blog post I discuss how to build the actual agent, using the Agent 365 SDK, with specific focus on how to use the notification functionality in the SDK.

Exploring the Agent 365 CLI

Ever since Agent 365 was announced at this year’s Microsoft Ignite, I have wanted to explore this exciting technology and the possibilities it creates. Since the Model Context Protocol is a topic that is dear to my heart, I got especially interested in the Agent 365 MCP Servers, and the way they make it possible for an agent to interact with the various Microsoft productivity applications, such as Word and Teams, in different ways.