Azure Weekly: Ignite 2026 Turns Azure Into an Agent Platform Microsoft used Ignite 2026 to reposition Azure around agents as the primary workload, making GPT-6.2 Astra and GPT-6.2 Sol generally available in Foundry, spinning out Azure AI Gateway as a standalone managed service, and adding managed GPU and CVM node pools on AKS. Microsoft says Astra beat GPT-6 Astra on average accuracy with substantially fewer output tokens at the same per-token price, a vendor benchmark the source urges teams to verify on their own evals. Preview features include an AKS AI Manager for Foundry, an Agent Sandbox extension, and Pod Snapshot for running untrusted agent-generated code. Ignite week always buries you in announcements. Strip the keynote gloss and one story is left: Azure is rebuilding itself around agents as the primary workload. Models, gateways, Kubernetes, and observability all changed this week with that assumption baked in. | Area | Announcement | Status | |---|---|---| | Models | GPT-6.2 Astra and GPT-6.2 Sol in Foundry | GA | | Governance | Azure AI Gateway standalone service | GA | | Kubernetes | Managed GPU node pools, CVM node pools on Azure Container Linux | GA | | Kubernetes | AKS AI Manager for Foundry, Agent Sandbox extension, Pod Snapshot | Preview | | Agents | Foundry continuous improvement, Foundry IQ knowledge graphs | New | GPT-6.2 Astra and GPT-6.2 Sol are generally available in Foundry https://techcommunity.microsoft.com/blog/azure-ai-foundry-blog/gpt-6-2-astra-and-gpt-6-2-sol-now-generally-available-in-microsoft-foundry/4574122 . Astra is the reasoning-heavy model; Sol targets production agents, coding, and high-frequency work. The interesting claim isn't capability. Microsoft says Astra scored higher average accuracy than GPT-6 Astra with substantially fewer output tokens in Foundry testing, at the same per-token price. That's a vendor benchmark, so verify it on your own evals. But the framing is right: stop comparing price per token and start measuring cost per task. The other detail worth your attention is 12-hour cache writes on Standard deployments, alongside the 30-minute default. If you run agents that go quiet overnight, long-lived system prompts and tool definitions can now stay cached at discounted read rates. This is the same discipline I argued for in context engineering https://htek.dev/articles/context-engineering-key-to-ai-development/ : the cheapest token is the one you don't re-send. If you're still deciding how to call these models, my breakdown of choosing the right AI SDK https://htek.dev/articles/choosing-the-right-ai-sdk/ still applies. Azure AI Gateway is now GA https://techcommunity.microsoft.com/blog/integrationsonazureblog/azure-ai-gateway-is-now-generally-available-ship-faster-stay-in-control/4572644 . It's the former AI Gateway tier of API Management, spun out as its own fully managed product with an AI-only roadmap. What you get: Pricing is freemium: 10,000 free requests per gateway per month, with paid billing starting January 1, 2027 . It launches in 17 regions. My take: every team running more than one agent will end up building this layer by hand, badly. Credentials scattered across apps, no central cost view, and no kill switch. A managed gateway is the right default. The multi-provider support is the tell: Microsoft knows you're not single-vendor, and it's choosing to be the control plane instead of fighting that. The AKS Ignite roundup https://techcommunity.microsoft.com/blog/appsonazureblog/run-models-and-agents-on-your-own-kubernetes-clusters-aks-at-microsoft-ignite-20/4573912 is the densest of the week. AKS AI Manager for Foundry limited preview lets you deploy open-weight models and Foundry hosted agents onto AKS clusters you already run. Developers stay in the Foundry workflow and the same azd flow; platform teams keep their networking, identity, policy, and GPU capacity. For regulated shops, this is the version of Foundry that gets past the security review. Three previews attack the same problem, running untrusted agent-generated code without making users wait: Per-session isolation is the correct security model for code-executing agents. I covered the broader shift in agentic DevOps as the next evolution of shift-left https://htek.dev/articles/agentic-devops-next-evolution-of-shift-left/ : the guardrails have to live in the platform, not in the prompt. Managed GPU pools remove an entire category of "why is the driver mismatched" tickets. That alone justifies the upgrade. Microsoft also announced continuous improvement in Foundry https://azure.microsoft.com/en-us/blog/continuous-improvement-comes-to-microsoft-foundry/ : feed traces and user input back into the system, let Foundry find and test improvements, see the trade-offs across quality, speed, and cost, and then you decide what ships. Microsoft also claims its model router can save up to 65% versus sending everything to a frontier model. Treat that as a ceiling, not a forecast. There's also Foundry IQ with knowledge graphs https://techcommunity.microsoft.com/blog/azure-ai-foundry-blog/foundry-iq-introducing-knowledge-graphs-engineered-for-agents/4572683 for agent grounding. The human-approves-the-change step is what I like. Self-modifying agents with no review gate are an incident waiting to happen. Last year Azure sold you models. This week it sold you the whole operating environment for agents: identity, gateway, sandboxes, GPUs, and a feedback loop. The pattern is clear: Microsoft wants to be the governed runtime underneath whatever model you choose. If that holds, the competitive ground moves from "who has the best model" to "who makes agents safest to operate", and that's a DevOps problem, which is good news for those of us who've been solving it for years.