Nitin Kumar SinghSolutions Architect

Type to search. ↑↓ to move, Enter to open.

    ↑↓ move ↵ open esc close
    UpdateIndustry

    Microsoft Ignite 2025: Microsoft Foundry - The Unified Enterprise AI Platform

    Microsoft Ignite 2025 unveiled Microsoft Foundry — a unified enterprise platform for agents, models, tools, and governance. What to adopt now and watch.

    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 ID1 gives every agent its own identity instead of a shared service principal, and the new Foundry Control Plane2 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 models3 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 Management4 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.

    References

    1. Entra Agent ID — learn.microsoft.com ↩

    2. Foundry Control Plane — learn.microsoft.com ↩

    3. Anthropic’s models — azure.microsoft.com ↩

    4. Azure API Management — learn.microsoft.com ↩

    5. Ignite 2025 next-steps repo — github.com ↩

    Comments

    Comments are GitHub discussions. Sign in with GitHub to post; reactions need no account.