The same MCP flaw at Google, JPMorgan and DINUM: your audit
Google, JPMorgan Chase, Weaviate, France's DINUM and an Indonesian city government have each fixed the same server-side request forgery flaw in their MCP servers, with Google's case scored CVSS 8.0 as CVE-2026-14540. Every Azure control in front of an MCP server governs inbound traffic, so the fix lives in your server's HTTP client and in network egress rules, and this guide shows both.
AWS Strands harness on Azure: five defaults to change first
AWS released Strands harness on 21 September 2026, an open-source Python and TypeScript agent harness that AWS says cuts token cost by 28% and that can run on Azure Container Apps. Out of the box it calls Amazon Bedrock, approves every tool call and keeps memory in a local folder, so Swedish and EU Azure teams need to change five defaults before any company data goes near it.
A classifier is not a sandbox: isolating coding agents
A published attack chain achieved remote code execution against Claude Code in auto mode, with the safety classifier approving the steps that led to compromise and then blocking the cleanup command. What the break teaches teams running AI coding agents, and how to build real isolation on Azure with Hyper-V sandboxes, default-deny egress and short-lived credentials.
MCP's new roadmap: five priorities after the stateless spec
The MCP core maintainers published a new roadmap on 22 August 2026, four weeks after the 2026-07-28 spec made the protocol core stateless: five priorities covering agentic messaging, HTTP-native transport unification, agent identity with DPoP and Workload Identity Federation, improved primitives, and SDK developer experience. Here is how Azure-first EU teams should sort that list into adopt now, prepare, and watch.
The MCP 2026-07-28 spec is final: your Azure migration plan
The Model Context Protocol specification version 2026-07-28 shipped on 28 July with a stateless core, Multi Round-Trip Requests, required routing headers, cacheable list results and a hardened authorization model that deprecates Dynamic Client Registration in favour of Client ID Metadata Documents. All four Tier 1 SDKs shipped support on release day, so Azure teams running MCP servers on Container Apps, AKS or behind API Management can start migrating immediately.
MCP goes stateless: Azure MCP server migration checklist
MCP's 2026-07-28 release candidate removes the initialize handshake and the Mcp-Session-Id header, so every request is self-contained and Azure-hosted MCP servers can run behind plain load balancers without sticky sessions or Redis session stores. Tasks and MCP Apps land as formal extensions, six SEPs harden authorization around OAuth 2.0 and OpenID Connect, and Roots, Sampling and Logging enter a 12-month deprecation window.
Container Apps vs AKS for AI Workloads: Decision Matrix
A decision matrix for running AI workloads on Azure Container Apps versus AKS — GPU support, scale-to-zero economics, networking, blast radius, operational overhead, and when graduating from Container Apps to AKS actually pays off.
Running Open-Source AI Models at Scale: Azure Container Apps, AKS, and On-Premise Deployments - Microsoft Ignite 2025
Microsoft Ignite BRK117: Deploy open-source AI models (Llama 3.3, Mistral) with Azure Container Apps serverless GPUs, AKS with Kaido workflows, and on-premise infrastructure. Cost reduction 60-85%, data sovereignty, and hybrid architectures with Azure Arc.