There’s been an important development in the AI Agents space that caught my attention, and I wanted to break it down — not just what was announced, but why it matters and how it fits into the bigger picture.
What’s New
When we launchedMicrosoft Agent Frameworklast October, we made a promise: building production-grade AI agents should feel as natural and structured as building any other software.
Today, we’re delivering on that promise — with thev1.0 release of Microsoft Agent Frameworkand thegeneral availability ofFoundry Toolkitfor Visual Studio Code(formerly AI Toolkit for VS Code), new capabilities inmemory(preview) in Foundry Agent Service,Toolbox in Foundry(preview) to give your agents the right tools, a faster and more securehostedagentsexperience in Foundry Agent Service (preview), andObservability in Foundry Control Planereaching full GA on core capabilities including end-to-end tracing now in place.
Customers likeSitecoreare already putting this stack to work.Their SitecoreAI platform powers Agentic Studio, a collaborative workspace where marketing teams and AI agents execute campaigns together. It’s built on Microsoft Agent Framework, with Foundry IQ ensuring each agent connects to the right brand knowledge at the right time with built-in governance.
Step 1: Build Locally with Microsoft Agent Framework + Foundry Toolkit for VS Code
Every agent starts on a developer’s machine.Microsoft Agent Frameworkhas now reached its v1.0 release and is stable across Python and .NET. It’s the open-source SDK and runtime that unifies the enterprise-grade foundations of Semantic Kernel with the multi-agent orchestration innovation of AutoGen, so developers no longer have to choose between them. We’ve published detailedmigration guidesfor existing Semantic Kernel and AutoGen users to make the transition straightforward.
Multi-modeland agent platform support— Azure OpenAI, Anthropic, Google Gemini, Amazon Bedrock, Ollama, and more
Workflows— programmatic and declarative multi-step agent pipelines, including visual export inDevUI
Native Foundry integration— memory, hosted agents, Observability (Tracing, Monitoring, and Evaluations), and Foundry Tools as first-class building blocks
Step 2: Build Agents That Actually Do Things — Agent Harness & Multi-Agent Composition (Public Preview)
Microsoft Agent Framework handles multi-agent orchestration— but orchestrating agents is only half the picture. The other half is what happens when an individual agent needs to operate autonomously over extended periods: executing shell commands, reading and writing to the filesystem, and managing context across long-running sessions without losing coherence. Microsoft Agent Framework addresses this in two ways: a built-inAgent Harness(public preview) and integrations with coding agents (public preview).
Key Takeaways
- When we launchedMicrosoft Agent Frameworklast October, we made a promise: building production-grade AI agents should feel as natural and structured as building any other software.
- Today, we’re delivering on that promise — with thev1.0 release of Microsoft Agent Frameworkand thegeneral availability ofFoundry Toolkitfor Visual Studio Code(formerly AI Toolkit for VS Code), new capabilities inmemory(preview) in Foundry Agent Service,Toolbox in Foundry(preview) to give your agents the right tools, a faster and more securehostedagentsexperience in Foundry Agent Service (preview), andObservability in Foundry Control Planereaching full GA on core capabilities including end-to-end tracing now in place.
- Customers likeSitecoreare already putting this stack to work.Their SitecoreAI platform powers Agentic Studio, a collaborative workspace where marketing teams and AI agents execute campaigns together.
- Every agent starts on a developer’s machine.Microsoft Agent Frameworkhas now reached its v1.0 release and is stable across Python and .NET.
- Foundry Toolkit for VS Code, now generally available, gives you a purpose-built VS Code experience alongside Microsoft Agent Framework: create agents from templates or with GitHub Copilot, test and debug runs locally with visualization and traces, and deploy to Foundry Agent Service directly — all without leaving the familiar VS Code environment.
Why This Matters
Agentic AI is where the industry is heading. From code generation to customer service to data analysis, agents can handle multi-step workflows that previously required human intervention at every stage. This isn’t just automation — it’s a fundamentally new way of building software.
This development is particularly significant because it reflects the broader industry shift toward making AI more accessible, enterprise-ready, and integrated into existing workflows. For teams already invested in the Microsoft ecosystem, this is a clear signal of where the platform is heading.
My Take
The technical frontier in AI agents right now is the orchestration problem — how do you reliably coordinate multiple specialized agents, each with different capabilities and knowledge, to solve complex tasks? The key architectural patterns emerging are: handoff protocols (A2A for cross-platform agent communication), governance layers (constraining agent actions within policy boundaries without killing autonomy), and state management (maintaining coherent context as work passes between agents). What I find most technically interesting is the convergence of code-generating agents (Copilot, Codex) with tool-using agents (function calling, MCP) — agents that can both write and execute code create a self-improving loop that’s qualitatively different from static automation. The challenge is reliability: current agents succeed ~70-85% on complex tasks. Getting to 99%+ requires better evaluation frameworks, graceful degradation patterns, and human-in-the-loop checkpoints for high-stakes decisions.
Business Translation
For the C-Suite: AI agents represent the next wave of operational leverage — not just automating tasks, but automating judgment. Early adopters are seeing 40-70% reduction in operational costs for knowledge work (customer service, compliance review, data analysis). The strategic question isn’t whether to adopt agents, but where to deploy them first for maximum ROI. The playbook: start with high-volume, medium-complexity workflows where errors are recoverable (customer inquiries, internal operations), then expand to higher-stakes domains as confidence grows. The organizations that build agent infrastructure now will have a 2-3 year head start when the technology matures.
📖 Read the original article for the full details and official documentation.
Written by Cyril Bou-Harb — Solution Engineer, Cloud & AI at Microsoft. Opinions and analysis are my own and do not represent Microsoft’s official position.