Microsoft expands Foundry hosted agents with enterprise controls

Microsoft is expanding hosted agents in Foundry Agent Service with networking, governance and deployment features aimed at moving enterprise projects from pilots into production. The announcements, made at Microsoft Ignite 2026, include generally available egress controls and subnet IP sharing, alongside previews for private certificate authority support and customer-managed AKS deployments.
- Subnet IP sharing is generally available for hosted agents.
- A /24 subnet has a planning estimate of about 60,000 concurrent sessions.
- Network egress controls are generally available.
- Private CA trust and Azure Policy egress governance are in public preview.
- BYO-AKS public preview is targeted for early December.
More sessions from existing network capacity
Hosted agents running in a customer’s virtual network previously used a separate IP address for each session. Microsoft says that meant a /24 subnet topped out at about 250 concurrent sessions, which could quickly become a constraint for teams with limited address space.
Sessions can now share subnet IP addresses while continuing to run in separate VM-isolated sandboxes. Microsoft’s planning estimate for a /24 is about 60,000 concurrent sessions, while a /27, the smallest supported size, is planned for about 7,500. The company stresses that these are planning estimates, not guarantees, and recommends a /24 or larger for production.
The feature is generally available without a request. For most teams, Microsoft says the practical limit will now be the regional session quota, which is 2,000 or 1,000 concurrent sessions per subscription by default, depending on the region. Customers can request a higher quota through support.
Controls for certificates and outbound connections
Foundry hosted agents can also use certificates issued by a company’s private certificate authority. Customers register the CA on the Foundry resource, with the certificate stored in Azure Key Vault. Projects in that resource can then use the certificate, while certificate and hostname checks remain enabled and public CAs continue to be trusted.
The private CA feature is in public preview. Microsoft says it supports tools, toolboxes and bring-your-own-model gateways in projects on a customer’s virtual network, as well as hosted agent code that directly calls internal services in new sessions. The company lists remote builds and mutual TLS among the scenarios not yet covered.
Network egress controls are generally available. Administrators can attach ordered rules to an agent to allow or deny hosts, add outbound headers or route traffic through a customer’s gateway. Foundry enforces those rules outside the agent sandbox, and denies a request if a policy cannot be evaluated.
Azure Policy governance for egress is in public preview. It allows administrators to check settings and new hosted agent versions at subscription or resource group scope. The preview starts in Canada Central, Spain Central and Korea Central.
A customer-operated AKS option
Microsoft is also preparing a bring-your-own-AKS deployment option. Foundry will run the agent runtime on a customer’s Azure Kubernetes Service cluster, while developers continue to build, deploy and call agents through Foundry using the same APIs, azd flow and endpoint.
Each session will run as its own pod in a lightweight VM through AKS pod sandboxing. Customers will retain control of cluster capacity and scaling, networking, container supply chain, storage settings and infrastructure monitoring. Foundry will manage the agent lifecycle and its managed integration components, while the customer operates the AKS cluster and supporting resources.
The public preview is targeted for early December. Microsoft positions the option for organizations that already operate AKS or need agent workloads to remain within infrastructure, network or compliance boundaries they manage. That gives enterprise teams a choice between managed hosting and customer-operated infrastructure without changing how developers work with agents in Foundry.


