Microsoft Ignite 2026 Book of News: A Developer and Architect Review

Microsoft Ignite 2026 announcements for developers and architects grouped by generally available and preview status
On this page

Microsoft Ignite 2026 is running in San Francisco from 17 to 20 November, and Microsoft has published its Book of News for the event: one long page listing every announcement with its status. I read it end to end as someone who builds and designs systems on this platform. This is my summary of what matters to developers and architects, what I would act on now, and what the page leaves unanswered.

The short version: almost every item is about agents. The question it answers is less how to build one and more how to run them: where they execute, what identity they carry, what they are allowed to reach, and how you find out what they did. The items that are generally available today are mostly data services and evaluation tooling. Most of the agent runtime and control features are still in preview.

What was announced

The page has chapters on Azure, Microsoft Foundry, GitHub, Microsoft Copilot, Edge, Microsoft IQ, security and Windows. This table is my cut of it for people who write and design software. It leaves out most of the end-user Copilot and device management items.

AreaAnnouncementStatus
ComputeAzure Cobalt 200 Arm-based VMs, with up to 50% better CPU performance than Cobalt 100GA
Agents on AKSFoundry open-weight models and agents on your own AKS clusters, Agent Grid, Agent Sandbox extension, Flex nodesPreview
OperationsAzure Monitor health models; Chaos Studio Workspaces and AKS extensionGA
OperationsAzure SRE Agent additions; Azure Copilot spaces and custom skillsPreview
ModernizationAzure Catalyst platform and Azure Catalyst agentGA
DatabasesAzure HorizonDB, a managed PostgreSQL-compatible database with built-in vector searchGA
DatabasesAzure SQL Database container for local developmentPreview
DatabasesAzure Cosmos DB Shell with MCP integration, Rust SDK, semantic rerankerGA
DatabasesDatabase Hub in FabricGA
FoundryMulti-turn evaluation, production insights, Agent optimizerGA
FoundryManaged Training and Programmed TrainingPreview
ModelsMicrosoft-Decision-1.1; MAI-Code-2 and MAI-Code-2-Flash in GitHubGA
GitHubCopilot SDK 2.0 on a native Rust runtime, in six languagesGA
ContextMicrosoft IQ: Work IQ, Fabric IQ, Foundry IQ and Web IQ through MCPGA
IdentityMicrosoft MCP Server for Enterprise (Entra data)GA
IdentityEntra Agent ID for discovered local agents; MCP FirewallPreview
SecurityMicrosoft PerceptionGA
WindowsWindows Server 2028; process containers for agentsPreview
Microsoft Ignite 2026 announcements for developers and architects grouped by generally available and preview status
My reading of the Book of News: what is generally available and what is still in preview.

For developers

A local Azure SQL Database. The item I expect to use first is the smallest one on the page. The Azure SQL Database container, in preview, runs the Azure SQL Database engine on your machine with no subscription. Microsoft says it has the same T-SQL dialect, system views, connection protocol and driver behaviour as the service, supports vector search, ledger and Always Encrypted with secure enclaves, and can run integration tests in CI. The usual choices for local work have been a SQL Server container, which is not the same product, or a shared cloud database. If the container does what the page says, integration tests can stop depending on a cloud instance.

HorizonDB is generally available. Azure HorizonDB is a fully managed, PostgreSQL-compatible database with built-in vector search. The GA list covers what a platform team asks about first: Entra ID, private endpoints, managed identities, customer-managed keys and multi-zone replication. The AI features on top of it, model management, AI Functions and AI Pipelines, are in preview, as is mirroring into Fabric. A second product with the same name, Microsoft Fabric HorizonDB, is a serverless PostgreSQL inside Fabric and is in preview. Read which one a document means before you plan around it.

Cosmos DB gets a shell and a Rust SDK. The Azure Cosmos DB Shell is GA in VS Code and the portal, and it includes MCP integration, so an AI assistant can work against a database through it. The Rust SDK and the semantic reranker are GA too. The page says seven updates and lists six.

Evaluation becomes a loop. Foundry now has multi-turn evaluation, which scores a whole conversation and not one reply, production insights, which groups recurring failures such as hallucinations and token spikes, and an Agent optimizer that proposes changes and tests them against your evaluations. All three are GA. This is the part of agent development most teams skip, and having it as a product removes one excuse. The two training options that feed from it, Managed Training and Programmed Training, are in preview.

Copilot SDK 2.0. GitHub’s only numbered item is the Copilot SDK 2.0, GA, described as a production-proven agent harness on a native Rust runtime, available in six languages, for agents embedded in applications including multi-tenant ones. The page does not name the six languages. The same chapter mentions that the GitHub Copilot app now works with Azure DevOps repositories, and that Copilot code review gains local reviews in the CLI, secret detection and cross-repository context.

A small, fast model for decisions. Microsoft-Decision-1.1 is GA for routing, classification and verification. It is built on Gemma 4, accepts images, and Microsoft says it is more than twice as fast as the first version at the same price. This is the kind of model an agent calls many times per task to decide what to do next, where speed and cost matter more than depth. MAI-Code-2 and MAI-Code-2-Flash are GA in GitHub.

Copilot Studio agents as code. Copilot Managed Runtime is GA. The developer-facing part is that Copilot Studio agents and workflows can be built locally, edited in your own tools, kept in version control and published with a CLI. The page gives no separate status for that part.

For architects

Agents get a place to run that you own. The AKS items belong together. Open-weight models and agents from Foundry can be deployed to your own AKS clusters, so you choose the GPUs and regions for cost, latency and data residency. Agent Sandbox runs code written by an agent in a sandbox isolated at virtual machine level. Agent Grid enforces policy on calls between agents, models, tools and Azure services. Flex nodes extend the same cluster to servers outside Azure. Together that is a reference shape for regulated workloads that cannot send prompts and data to a shared model endpoint. All four are in preview.

Context is now a platform. Microsoft IQ is GA with no new SKU. It packages four sources of context, Work IQ for Microsoft 365 data, Fabric IQ for business data, Foundry IQ for documents and Web IQ for the web, and exposes them to Microsoft Copilot, GitHub Copilot, Foundry and any agent harness through MCP. The design consequence is that retrieval stops being something each agent team builds. It also means the permissions on those sources become the permissions of every agent that connects, so the access review has to happen before the connection, not after.

Modernization has one name. Azure Catalyst, GA, joins the migration tooling in Azure with GitHub Copilot modernization. The agent that plans migrations is GA. Extending it into carrying out the modernization, and a BizTalk to Logic Apps path, are in preview. For estates with BizTalk still in production, that preview is worth an early look, because in my experience BizTalk estates are getting harder to staff.

Operations. Azure Monitor health models are GA. They turn telemetry into a health graph that separates platform problems from application failures and ranks incidents by business impact, which is what most teams build by hand in dashboards. Chaos Studio Workspaces are GA, with reusable scenarios such as losing an availability zone. Windows Server 2028 is in preview with post-quantum cryptography and NVMe over Fabrics. The page gives no release date.

Agent governance

The security chapter is the longest, and most of it answers one question: an agent is running somewhere in the estate, so who is it and what can it reach? Reading the items together, I see controls at five layers. The diagram is my arrangement of them, not Microsoft’s.

%%{init: {'theme':'base','themeVariables':{'primaryColor':'#FFF3E0','primaryTextColor':'#232F3E','primaryBorderColor':'#FF9900','lineColor':'#232F3E','clusterBkg':'#F8FAFC','clusterBorder':'#CBD5E1','edgeLabelBackground':'#FFFFFF','nodeTextColor':'#232F3E'}}}%%
flowchart TD
    A["Identity:
Entra Agent ID for cloud and local agents"] --> B["Network:
Global Secure Access, MCP Firewall"] B --> C["Device:
Intune compliance, Windows process containers"] C --> D["Runtime:
Agent Sandbox and Agent Grid on AKS"] D --> E["Data:
Purview protection for agent interactions"] E --> F["Oversight:
Agent 365 inventory, risk and cost"] style A fill:#EBF8FF,stroke:#0073BB,stroke-width:2px,color:#004C74 style B fill:#F3E8FF,stroke:#7C3AED,stroke-width:2px,color:#4C1D95 style C fill:#FFF3E0,stroke:#FF9900,stroke-width:2px,color:#232F3E style D fill:#FFF3E0,stroke:#FF9900,stroke-width:2px,color:#232F3E style E fill:#F0FFF4,stroke:#1D8102,stroke-width:2px,color:#145202 style F fill:#FEF2F2,stroke:#D13212,stroke-width:2px,color:#991B1B
  • Identity. Entra Agent ID is extended to local agents that are discovered on devices, starting with GitHub Copilot CLI and Claude Code, so their activity can be told apart from the person’s. Preview.
  • Network. An MCP Firewall in Entra Global Secure Access controls access to MCP servers, tools, resources and prompts. Preview. Acquiring agent traffic selectively is GA.
  • Device. Intune can mark a device with unapproved agents as noncompliant, and Conditional Access can then block it from company data. Windows adds process containers that give each agent a workspace with limits on communication and network reach. Both preview.
  • Runtime protection. Defender runtime protection for local agents on Windows is GA, and the page names Claude Code and GitHub Copilot CLI among those covered.
  • Oversight. Agent 365 adds a risk level per agent in preview, governance for plugins and skills at GA, and MCP governance for Azure AI Gateway and LiteLLM in preview.

One GA item sits apart from these: the Microsoft MCP Server for Enterprise, which lets agents and applications query Entra data through a permissions-based interface. It is the first of these controls a developer can build against today.

⚠️
MOST OF THE CONTROL PLANE IS PREVIEW

Agents are already running in many organisations. Agent identity for local agents, the MCP Firewall, device compliance for agents, process containers and the AKS sandbox are all in preview. If you are approving agents for production now, the controls you can rely on are the ones you already had: application identities, network policy, and review of what each agent is connected to.

This matches what I found last week when I tested an approval flow in Building an Agentic UI with Blazor and .NET 11: the protocol let a caller approve an action the agent never proposed, and the fix was a check on the server. Platform controls will help. They do not replace knowing who is allowed to approve what in your own service.

What to do next

This is how I would sort the announcements for a team planning its next quarter. It is a judgement from reading the page, and nothing here has been tried yet.

DecisionItemsWhy
Use nowFoundry multi-turn evaluation and production insights; Azure Monitor health models; Cosmos DB Shell; Microsoft MCP Server for EnterpriseGA, low risk to adopt, and each replaces something teams build by hand
Evaluate for a real workloadAzure HorizonDB; Cobalt 200 VMs; Microsoft-Decision-1.1; Copilot SDK 2.0; Azure CatalystGA, but the page gives no limits or prices, so test with your own data and load
Try in a sandboxAzure SQL Database container; Agent Sandbox and Agent Grid on AKS; Entra Agent ID for local agents; MCP FirewallPreview. Learn the model now, do not depend on it yet
WatchWindows Server 2028; Fabric HorizonDB; Managed and Programmed Training; BizTalk to Logic AppsPreview with no dates given
Suggested sorting of Microsoft Ignite 2026 announcements into use now, evaluate, try in a sandbox and watch
How I would sort the announcements for planning. A judgement from reading, not from testing.

Open questions

A Book of News is an index of announcements. These are the things I looked for and did not find on the page. The linked product posts may answer some of them.

  • HorizonDB limits and price. The page gives no storage ceiling, replica count, vector index type or pricing.
  • How close the SQL container really is. “Same engine” needs testing. The page does not say what happens with service features such as elastic pools, geo-replication and Entra authentication.
  • The six languages of Copilot SDK 2.0. Not named on the page.
  • Agent Grid and Agent Sandbox prerequisites. Which AKS versions, node types and regions, and what the sandbox costs in start-up time.
  • What an Agent ID for a local agent can be scoped to. The page says activity is separated from the human’s. It does not say whether permissions can be narrower than the user’s.
  • Dates. Windows Server 2028 and most previews have no stated release date.

Key takeaways

  • Ignite 2026 is about operating agents: where they run, what identity they have, and what they can reach.
  • The generally available items a developer can use today are in data and evaluation: HorizonDB, the Cosmos DB Shell, Foundry evaluation and production insights, Copilot SDK 2.0.
  • The agent runtime on AKS and most agent governance controls are in preview. Plan for them, and keep your own controls until they ship.
  • The Azure SQL Database container is a small item with a large effect on local development and CI, if it holds up in testing.
  • Microsoft IQ makes enterprise context available to any MCP-capable agent. Review access to the underlying sources before connecting agents to them.
  • Two products are called HorizonDB. Check which one a document means.
📝
HOW THIS WAS CHECKED

This article is a reading of one source, Microsoft’s Ignite 2026 Book of News, as published on 19 November 2026. Every product name, status and figure comes from that page. Nothing was installed, deployed or measured, and no session was attended. I did not open the product posts the page links to, so details that live only there are not covered. The grouping into layers, the use, evaluate, try and watch sorting, and the opinions are mine. Preview features change, and the page may be updated after this date.

References & Further Reading


Discover more from C4: Container, Code, Cloud & Context

Subscribe to get the latest posts sent to your email.

Written by

Nithin Mohan TK

Hello Namaste! 👋🏻 I'm an accomplished Enterprise Solution Architect & Engineering Leader with 20+ years of progressive experience architecting, building, and scaling transformative enterprise solutions. ⚜️ Solution Architect / AI & Cloud 📌 Galway, Ireland

Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.