A technical reference on the Microsoft agent-development stack — Azure Foundry, Agent Framework, Copilot Studio, M365 Agents Toolkit and SDK. For team members ready to move beyond Agent Builder and ship production-grade custom agents. Prerequisites up front.
The tools in this report are powerful because they're real developer tools. That also means they assume a working knowledge of cloud, code, and command line. Read this first. If more than two items in the Skills column feel unfamiliar, spend a week on the Learning Path in Section 9 before going further.
az login and azd — both used heavily across all four tools in this report.
async / await, streaming responses, event-driven flows. Intimidating at first, fundamental by week two.
DefaultAzureCredential means in practice.
Azure AI User (least privilege) on the Foundry projects you use, or Azure AI Project Manager to manage projects.
Owner on the subscription or resource group is needed to create Foundry resources for the first time.
AI-901 is the updated Azure AI Fundamentals exam with stronger Foundry + generative AI coverage; AI-900 remains available alongside it. Check Microsoft Learn for current retirement dates.
Microsoft's advanced agent stack looks fragmented until you understand where each tool sits. Here they are in the order of increasing technical depth — from low-code Copilot Studio through open-source Agent Framework to full production on Foundry.
You've met Agent Builder in the prior report — the no-code interface inside the M365 Copilot app, great for small team helpers grounded on a SharePoint folder. This report is about everything past that point. It's where you go when Agent Builder's boundaries start to pinch — when you need custom actions, multi-step flows, external API calls, multi-agent orchestration, or production deployment.
The five tools below aren't competitors — they're a ladder. You'll often use two or three together on the same project. The question isn't "which one" but "which one first."
| Tool | Skill floor | Publish where | Best for |
|---|---|---|---|
| Copilot Studio (advanced) | Low-code. Visual designer + YAML view. No mandatory code. | Teams, Web, WhatsApp, SMS, Copilot Chat, M365 Copilot | Department or external-facing agents with connectors to SAP / Salesforce / Dynamics / custom APIs. |
| M365 Agents Toolkit (declarative) | JSON, YAML, light TypeScript. VS Code extension. | M365 Copilot (Chat, Word, PowerPoint), Teams | Pro-code agents for M365 Copilot. Runs on the same M365 Copilot orchestrator as Researcher and Analyst — new Copilot features tend to land in declarative agents first. |
| M365 Agents SDK (custom engine) | Full-stack Python, JS/TS, or .NET. | M365 Copilot, Teams, Web, Email, SMS, any channel | Custom-engine agents. Bring your own AI / orchestration. Multi-channel. |
| Microsoft Agent Framework | Python or .NET. Open-source SDK. | Anywhere — local, Azure, AWS, GCP, or Foundry | Multi-agent orchestration. Sequential, concurrent, handoff, group-chat, Magentic-One patterns. |
| Microsoft Foundry (Agent Service) | Python, .NET, JS/TS, Java. Managed runtime. | Any Foundry endpoint. Distribute to M365 Copilot, Teams, Entra Agent Registry. | Production agents at enterprise scale. Extensive Foundry model catalogue, private networking, Foundry IQ (RAG), full observability. |
The natural next step after Agent Builder. Still low-code enough for a non-developer, but with the connectors, flows, and governance to support department-wide and external-facing agents. This is where most technically-capable advisors will spend their time.
Copilot Studio is a standalone web portal (and the big sibling of Agent Builder). It targets IT pros, solution architects and power users — not developers by trade, but people comfortable with configuration, logic trees, and API connectors. It's included with your Microsoft 365 Copilot licence for internal agent use, with pay-as-you-go Copilot Credits for external deployment and advanced features. Every agent you build can be promoted from Agent Builder into Copilot Studio without starting over.
The pro-code path for building agents that run inside M365 Copilot — and the closest thing Microsoft has to "real developer" tooling for Copilot surfaces. VS Code extension, declarative manifests, one-click provisioning. If you can write TypeScript or Python and know JSON, you're ready.
Agents Toolkit is a suite of tools (VS Code extension, Visual Studio extension, CLI) for building declarative agents for M365 Copilot and custom-engine agents via the M365 Agents SDK. Templates, scaffolding, one-click provision/debug, CI/CD actions for GitHub and Azure DevOps, plus the Microsoft 365 Agents Playground for local testing without a dev tenant. Declarative agents built here run on the M365 Copilot orchestrator — the same orchestrator that powers Researcher, Analyst and other first-party Microsoft agents — which means new Copilot capabilities tend to land in declarative agents before Copilot Studio gets them.
.env filesThe open-source SDK that converges AutoGen (Microsoft Research multi-agent patterns) with Semantic Kernel (enterprise foundations). Production-ready at v1.0 as of early 2026. This is where advanced teams build sophisticated multi-agent systems.
Agent Framework is the open-source foundation for building sophisticated multi-agent systems. It hit v1.0 in early 2026 after several months in release candidate. You install it with one line in Python or .NET, and you're running agents in under 20 lines of code. But the reason it matters isn't simplicity — it's that it brings the five orchestration patterns from Microsoft Research (sequential, concurrent, handoff, group chat, Magentic-One) into a single production-ready library with streaming, checkpointing, human-in-the-loop approvals, pause/resume, OpenTelemetry, and Entra ID authentication.
The production platform for enterprise-grade AI. Unified portal, managed agent runtime, extensive Foundry model catalogue, broad connector ecosystem, private networking, full observability. Where the agents built in every other tool on this list ultimately run in production.
Microsoft Foundry (renamed from Azure AI Foundry in late 2025) is a unified platform combining a portal, an agent runtime, and a model catalogue. 80,000+ enterprises use it, including 80% of the Fortune 500. Foundry Agent Service — the runtime core — went GA in May 2025, is built on OpenAI's Responses API, and is wire-compatible with OpenAI agents. Foundry SDKs (Python, JS/TS, Java, .NET) all shipped stable 2.0.0 releases in March 2026. This is where production-grade agents actually live.
mcp.ai.azure.com with Entra authA five-question decision tree for picking the right advanced agent tool. Walk through it top to bottom. Stop at the first question where the answer is clear.
Agent Builder from Part III and ship in 15 minutes.M365 Agents Toolkit with declarative agents. Same M365 Copilot orchestrator as Researcher and Analyst, JSON/YAML, one-click provision from VS Code. Best pro-code path for M365-native agents.Copilot Studio. 1,500+ connectors, visual designer, YAML view for advanced control.Microsoft Agent Framework. Open-source SDK, Python or .NET, all five orchestration patterns, A2A + MCP, cross-cloud portable.Microsoft Foundry Agent Service. Managed runtime, broad Foundry model catalogue, Foundry IQ for RAG, private networking, full observability. Distributes to M365 Copilot / Teams / Entra Agent Registry.Agent Framework locally. Migrate to Foundry when it's time to ship.Four realistic Arup advisory scenarios where Agent Builder simply isn't enough, and the full advanced stack pays for itself. Each scenario shows the exact stack.
The fastest practical route from "comfortable with M365 Copilot" to "shipping a production agent." Assumes no prior Azure or agent experience, but Python or .NET basics. Four stages.
az login + azd. Walk through the "AI Agents for Beginners" course (lessons 1–4). Aim: one working local agent that calls Azure OpenAI.agent-framework. Build a single-agent sample with tools. Then a two-agent handoff. Then a Magentic-One multi-agent system. Clone the microsoft/spec-to-agents event-planner sample and run it locally.After six weeks, you'll have: a local MAF multi-agent system you wrote, a declarative agent that ships in M365 Copilot, a Foundry-hosted production agent with tracing, and enough grounding to read every Microsoft agent blog with comprehension. That's the bar for "ready to build for a client."
"Building AI agents shouldn't be rocket science. Yet many developers find themselves wrestling with complex orchestration logic, struggling to connect multiple AI models, or spending weeks building hosting infrastructure just to get a simple agent into production." — Microsoft Agent Framework launch, Oct 2025
The tools in this report exist precisely to stop that from being the bottleneck. Six weeks of deliberate practice is enough to move past Agent Builder and be genuinely useful to a client engagement that needs custom agents.