Microsoft Ignite Unveils Production Capabilities for Foundry Hosted Agents: Shared Subnet IPs and Private CA Trust
At Ignite 2026, Microsoft announced updates to Azure Foundry Agent Service, including shared subnet IPs supporting tens of thousands of concurrent sessions, private CA certificate trust, and generally available network egress controls.
Microsoft announced at its Ignite conference on November 18, 2026, that several new capabilities are now available for Hosted Agents in Azure Foundry Agent Service, designed to resolve bottlenecks preventing enterprises from moving AI agents from pilot to production. These updates focus on network scalability, secure internal service connectivity, and deployment flexibility.
To address IP address exhaustion, which previously limited large-scale deployments, hosted agent sessions now support shared subnet IPs. Microsoft states that each session continues to run in its own VM-isolated sandbox but no longer requires a dedicated IP address. According to planning estimates, a /24 subnet can now support approximately 60,000 concurrent sessions, while the smallest supported /27 subnet is projected to handle about 7,500. This change is Generally Available (GA) and requires no additional request.
On the security front, support for trusting Private Certificate Authorities (Private CAs) has been introduced, currently in public preview. Previously, agents often failed calls to internal MCP servers or APIs using corporate certificates due to strict certificate checks. Now, administrators can register a CA certificate once on the Foundry resource (stored in Azure Key Vault), allowing projects within that resource to automatically trust it. This maintains hostname and certificate validation without disabling security checks.
Network Egress Controls are also Generally Available. This feature allows organizations to enforce allow/deny rules for specific hosts outside the agent's sandbox, addressing the security concern that "a tool list is not a network boundary." Additionally, Microsoft previewed a "Bring Your Own AKS" (BYO-AKS) deployment option, targeted for early December public preview, which enables organizations to run the Foundry agent runtime on their own Azure Kubernetes Service clusters to meet specific compliance and network management requirements.