Azure Functions Ships Serverless Agents Runtime at Build 2026
Public-preview runtime defining agents in .agent.md markdown with YAML triggers, MCP server access, 1,400+ connectors, and sandboxed execution.
18 articles · 5 categories
Friday, Jun 19, 2026
In 30 seconds
Friday was a runtime day. The platforms an AI agent actually lives in kept hardening: Microsoft shipped a serverless agents runtime in Azure Functions at Build 2026 (agents defined in .agent.md files with YAML triggers, MCP access, and sandboxed execution), Mantyx pitched a batteries-included managed agent runtime, and Anthropic quietly paused token-based billing for the Claude Agent SDK — a reminder that the commercial model for agent infrastructure is still being figured out in real time.
Underneath the runtimes, the connective tissue stayed in focus. Sean Lynch (via Simon Willison) made the sharp point that MCP's real edge over plain skills/CLI is isolating the auth flow outside the agent's context window — a framing that lines up with two security stories landing the same day: BleepingComputer arguing every AI agent is an identity most orgs don't govern, and Microsoft positioning Windows (with a new Execution Context model) as the trustworthy OS for autonomous agents. The plumbing is maturing faster than the governance around it.
On the model front, the open-weights story finally read like a frontier story: Latent Space's AINews flagged GLM-5.2 passing everyone's vibe check, with Z.ai forecasting an open Fable-class model by December. And on evals, a recurring theme — simplicity wins — surfaced in a harness claiming SOTA on SWE-Pro, Terminal-Bench 2, and SWE-Verified across 21 models with a deliberately simple agent.
Where agents run kept consolidating — a serverless runtime from Azure, a managed runtime startup, and a billing pause from Anthropic.
Public-preview runtime defining agents in .agent.md markdown with YAML triggers, MCP server access, 1,400+ connectors, and sandboxed execution.
Anthropic halts token-based billing for the Claude Agent SDK — a signal that pricing for agent infrastructure is still in flux.
A managed agent runtime pitching an all-in-one operational layer so teams don't have to assemble their own.
The connective layer between agents and the world — MCP's real value, plus a wave of small tools that give agents coding, browsing, and validation hands.
MCP's distinct value: isolating the auth flow outside the agent's context window — and potentially out of the harness entirely.
Brings CI-style validation directly into an AI coding agent's inner development loop instead of waiting for a separate pipeline.
An MCP server that hands any LLM agent a coding toolset, lowering the bar to wire code execution into an agent.
A CLI that converts web pages into clean Markdown so agents ingest readable context instead of raw HTML.
An MCP-based integration letting an Adobe marketing agent authenticate and pull campaign insights into Amazon Quick.
As agents get more autonomy, the identity and OS-level trust questions moved to the foreground.
Argues agents need first-class identity governance — credentials, scope, and audit — that most orgs haven't built.
Microsoft positions Windows as the trustworthy OS for autonomous agents, introducing a Microsoft Execution Context model.
The open-weights race started to look like a genuine frontier story.
GLM-5.2 clears the community vibe check and Z.ai forecasts an open Fable-class model by December, sharpening the open-vs-closed frontier story.
A recurring 'simplicity wins' thread in agent design, plus practitioners comparing loops and multi-model orchestration.
A benchmark harness claims SOTA on SWE-Pro, Terminal-Bench 2, and SWE-Verified across 21 models using a deliberately simple agent.
OpenAI's Kepler, an internal data-analyst agent over 600+ PB, handles context limits via MCP, automated code crawling, and RAG.
A consensus-style agent loop the team uses to ship production code, contributing to the day's 'how should the loop work' debate.
Practitioners compare models by strength (Gemini for refactoring, GPT/Claude for coding) and ask how to orchestrate them together.