Agent 365: Declarative MCP Servers

Key insights

• Demo overview: Lee Ford (Symity) demonstrated how to connect Agent 365 MCP servers to Declarative Agents in a Microsoft 365 Copilot demo.
  He showed real multi-step automations that call services like Outlook and SharePoint from within Copilot.
• What an MCP server does: An MCP (Model Context Protocol) server exposes tools and actions in a standard format so agents can discover and invoke them.
  This removes the need to hardcode each API and gives agents a consistent way to act on external systems.
• Declarative Agents integration: Declarative Agents now connect to MCP servers as actions by linking to an MCP URL, selecting tools, configuring authentication, and generating agent files.
  This flow simplifies building agents and reduces custom integration code.
• Enterprise governance with Agent 365: Agent 365 provides enterprise-grade MCP tooling that maps tools to permissions, enables admin approval, and supports auditing.
  That makes agent access safer and compliant for large or regulated organizations.
• Bring Your Own (BYO) MCP server: Organizations can register and govern their own MCP servers so internal systems become safely available to Copilot and agents.
  Admins control approval, consent, and access centrally.
• Developer toolkit and richer experiences: The Microsoft 365 Agents Toolkit scaffolds agents, discovers MCP tools, helps configure auth, and supports local testing.
  MCP apps can also render richer UI inside Copilot interfaces for scenarios like approvals and interactive workflows.

Microsoft 365 published a demo video that shows how developers can extend AI agents in Microsoft 365 by connecting them to Agent 365 MCP servers and using Declarative Agents. The recording, presented by Lee Ford during a Microsoft 365 & Power Platform community call on March 26, walks through practical steps for linking agents to APIs, SharePoint, and Outlook to build multi-step automations inside Microsoft 365 Copilot. Overall, the demo emphasizes a standard way to expose and govern tools through the Model Context Protocol (MCP), which aims to reduce custom integration work and improve enterprise readiness.

Overview of the Demo

The video starts with a clear problem statement: integrating many enterprise systems into agent workflows is error prone and costly when each integration is hand-coded. Consequently, Microsoft shows how an MCP server can present tools in a common format that Declarative Agents consume as actions, allowing Copilot-style experiences to call those tools securely. In the demo, Lee Ford illustrates how common Microsoft 365 services such as Outlook, SharePoint - Lists, and Teams can be surfaced through MCP endpoints, enabling agents to perform real business tasks rather than only returning data.

Moreover, the demonstration highlights that this approach supports both Microsoft-hosted tooling and customer-owned servers, so organizations do not have to modify their internal services radically. The presenter emphasizes that using MCP servers standardizes agent-tool interactions and makes auditing and governance simpler. Importantly, the demo also shows sample flows that chain multiple tool calls into business logic, which demonstrates how agents can do multi-step work inside the enterprise.

How It Works in Practice

Lee Ford walks viewers through the main steps to build an MCP-backed declarative agent: create a declarative agent, add an action, point to an MCP server URL, choose the tools to expose, configure authentication, and then generate and test the agent files. The demo highlights the way the Microsoft 365 Agents Toolkit can automate many of these steps by scaffolding the agent and discovering available tools from a server. This toolkit-driven flow reduces manual configuration and lets developers focus on orchestration logic and business rules rather than low-level plumbing.

In addition, the video demonstrates local testing and provisioning features so teams can iterate before deploying to production. The presenter runs through authentication configuration and shows how the generated manifest ties tools to agent actions, which is a key step for making agents behave predictably and securely. Thus, developers see a reproducible pipeline from discovery to deployment that shortens the development loop.

Governance, BYO, and Enterprise Controls

A central part of the demo covers governance: Microsoft depicts Agent 365 tooling servers as enterprise-grade MCP gateways that administrators can use to manage permissions and approvals. As a result, each registered MCP server can map to a set of permissions and admin approvals, and access becomes auditable through centralized controls. The demo also explains a formalized Bring Your Own (BYO) MCP server path so organizations can register and govern external or internal servers without sacrificing control.

This governance model balances the need for secure, auditable access with the desire to let developers innovate. Nevertheless, it introduces administrative overhead because teams must maintain server registrations, consent flows, and permission reviews. Therefore, organizations must weigh the benefit of centralized control against the cost of coordinating governance processes across IT, security, and development groups.

Developer Experience and New Capabilities

The demonstration shows the Microsoft 365 Agents Toolkit improving developer productivity by automatically generating plugin and manifest files and by helping configure authentication. As a result, developers can focus on business logic and user experience instead of repetitive manifest edits. The demo also surfaces an emerging trend: MCP-based tools can carry richer interactive UI experiences inside Copilot-style interfaces, which creates new possibilities for approvals, decision prompts, and guided interactions.

However, richer UIs come with testing and consistency challenges, because visual components must adapt to different host experiences and client platforms. Therefore, teams should plan for thorough user testing and cross-environment validation so those richer elements behave reliably in production. Overall, the toolkit lowers the barrier to entry, but delivering polished UI-driven agent experiences still requires design and QA investment.

Tradeoffs and Operational Challenges

Adopting MCP servers and declarative agents offers clear benefits—consistency, reduced custom code, and centralized governance—but it also forces tradeoffs that organizations should consider. For instance, centralized tooling can slow down rapid experiment cycles if approvals and registrations become bottlenecks, and running additional MCP servers increases operational surface area that teams must secure and maintain. Consequently, firms must balance agility with compliance and decide which flows deserve tight governance versus rapid developer access.

Other practical issues include latency from chained tool calls, the complexity of managing authentication across many services, and the need for thorough logging to meet audit requirements. To handle these challenges, the demo suggests incremental adoption: start with non-critical scenarios, validate governance workflows, and then expand to higher-value automations once the processes and monitoring are in place. In doing so, teams can reduce risk while still taking advantage of the new capabilities.

In conclusion, the Microsoft demo led by Lee Ford presents a pragmatic path to extend Declarative Agents using MCP servers, combining developer productivity with enterprise governance. The video provides hands-on examples and a clear toolkit-driven process that teams can replicate, while also warning about the governance and operational tradeoffs involved. Organizations evaluating this approach should begin with pilot projects, align IT and security reviews early, and plan for ongoing maintenance to ensure robust, scalable deployments of agent-driven automations.

Keywords

Agent 365 MCP servers, Declarative Agents, Deploying MCP servers with Declarative Agents, Azure Declarative Agents, Agent 365 migration guide, MCP server configuration, Declarative Agents best practices, Manage Agent 365 in Microsoft 365