I was at Microsoft Ignite for the Foundry announcements, and the framing runs ahead of the substance. Microsoft rebranded most of its Azure AI stack as Microsoft Foundry: one PaaS spanning models, agents, tools, knowledge, and governance. Underneath the launch-day gloss, three things actually matter to anyone shipping enterprise agents.
Agent identity got real. Entra Agent ID gives every agent its own identity instead of a shared service principal, and the new Foundry Control Plane hangs governance off it: per-agent RBAC, input/output/tool-call guardrails, and OpenTelemetry tracing across Microsoft Agent Framework, LangGraph, and the OpenAI Agents SDK. If you have watched non-human identities sprawl into ungoverned secrets, this is the piece to pilot first.
Claude landed on Azure. Anthropic’s models now run in Foundry with unified Azure billing and enterprise controls. For teams that wanted Claude but were blocked by procurement or data-residency rules, that removes the main objection: no separate vendor, same tenant, same billing.
APIM became the AI Gateway. Azure API Management now sits in front of model, agent, and MCP-tool traffic as one policy and observability choke point. It is the least flashy announcement and the one I would build on, because it is the difference between per-agent security sprawl and a single enforced boundary.
What I would not do yet: rip out working orchestration to move onto Foundry Agent Service, or take Foundry IQ’s “36% better relevance than traditional RAG” at face value. That number is Microsoft’s own benchmark on its own retrieval engine. Model Router reaching GA is genuinely useful; treat the rest of the 1,900-model catalog as previews until you have run your own evals.
The Microsoft Agent Framework (Semantic Kernel and AutoGen merged into one open-source SDK) is worth tracking on its own, since it is where the .NET and Python agent stories consolidate.
Takeaways#
- Adopt now: Entra Agent ID plus Control Plane governance, and APIM as your AI Gateway. Those are the durable, portable parts.
- Useful immediately: Claude on Azure with unified billing removes a real procurement blocker.
- Watch, do not migrate: Foundry Agent Service and Foundry IQ look promising, but validate the vendor numbers before betting production on them.
The full session and lab list is in Microsoft’s Ignite 2025 next-steps repo; the platform overview lives in the Foundry docs.