November 18th, 2026
0 reactions

Hosted agents in Foundry Agent Service at Ignite 2026: from pilot to production inside your enterprise boundaries

Over the last few months I’ve worked with a lot of teams taking a hosted agent from pilot to production. A working demo is only the start. The questions that decide whether it ships come next: Will the subnet hold up when usage takes off? Can the agent call internal services that use our own certificates? Where exactly can it connect, and who decides? Can it run on the Azure Kubernetes Service (AKS) clusters we already operate? And what happens when a two-hour job gets interrupted?

At Microsoft Ignite 2026, we’re announcing a solution to each of these challenges for hosted agents in Foundry Agent Service. Below you’ll find what’s new, what you can use today, and what’s still to come. The egress and private CA updates apply to managed hosted agents, the ones Foundry runs for you; BYO-AKS support will be documented separately.

At a glance

What’s new What it means for you Status
Shared subnet IPs Run many more sessions from the same subnet; your session quota still applies Generally available (GA)
Private CA trust Call internal services that use your company’s certificates, with certificate checks still on Public preview
Network egress controls One place to decide where an agent can connect, enforced outside the agent Generally available (GA)
Azure Policy governance for egress Admins require compliant egress settings across a subscription or resource group Public preview, starting in three regions
Deploy hosted agents to your own AKS clusters Foundry’s agent runtime on your own AKS cluster Public preview targeted for early December
Long-running resilient execution Opt-in recovery for long jobs after a crash or redeploy Generally available
Configurable idle timeout Sessions can wait from 2 minutes to 4 hours between requests Generally available
Memory snapshots Faster cold starts for agents with heavy startup Public preview
A2A passthrough Host your A2A v1.0 agent on Foundry with a small Python adapter Public preview

Scale: run far more sessions from the subnet you already have (GA)

If you run hosted agents in your own virtual network, each session used to take its own IP address from your delegated subnet. A /24 topped out at about 250 concurrent sessions, and teams with a tight IP plan hit that wall fast.

Hosted agent sessions now share subnet IP addresses. Each session still runs in its own VM-isolated sandbox. What changes is how far your subnet goes: our planning estimate for a /24 is now about 60,000 concurrent sessions, and even a /27, the smallest supported size, is planned for about 7,500. IP sharing is on for everyone, with no request needed.

These are planning estimates, not guarantees, and we still recommend a /24 or larger for production so there’s room for upgrades and maintenance. For most teams, your regional session quota is now the practical ceiling: by default 2,000 or 1,000 concurrent sessions per subscription, depending on the region. You can ask for more through a support request.

Status: Generally available now. See subnet size and concurrent sessions.

Trust: call internal services that use your company’s certificates (public preview)

Internal MCP servers, APIs and model gateways often use certificates from a private certificate authority (CA). Agents didn’t trust them, so calls failed, and the tempting fix was turning off certificate checks. Security teams don’t like that fix, for good reason.

Now you register your CA once on the Foundry resource. The CA certificate lives in Azure Key Vault, and every project in the resource picks it up. Certificate and hostname checks stay on, public CAs stay trusted, and you don’t bake CA files into container images or recreate project capability hosts.

Trust covers two paths. Tools, toolboxes and bring-your-own-model gateways use your CA in projects on your own virtual network, usually within a minute of the update. Hosted agent code that calls internal services directly trusts your CA in new sessions. The docs list what isn’t covered yet, such as remote builds and mutual TLS.

Status: Public preview. See Connect agents to services that use a private certificate authority.

Control: network egress controls are generally available (GA)

A tool list isn’t a network boundary. Agent code can start a subprocess, a library can follow a redirect, and generated code can call anything. Security teams want one place to say “these hosts, nothing else.”

Network egress controls for hosted agents are now generally available. You attach an ordered list of rules to an agent: allow or deny hosts, add headers on the way out, or send traffic through your own gateway. Foundry enforces the rules outside the agent’s sandbox, before requests reach their destination, so they don’t depend on the agent’s code behaving. If a policy can’t be evaluated, the request is denied. Egress controls add to your own network controls, like Azure Firewall; they don’t replace them.

If security review is what’s holding your agent back, start here. Turn on Audit mode with a default of deny. In Audit mode, Foundry logs every request it would have blocked but lets it through. Header changes and rewrites still apply, so test them in a non-production environment first. Run representative tasks, review the destinations you see, and refine the allowlist. Then switch to Enforce and deploy a new agent version, since running sessions keep the policy they started with. Your security team reviews a list built from real traffic instead of a guess.

Admins get a central check too. With Azure Policy governance (public preview), you assign policy at a scope such as a subscription or resource group, and Azure Policy checks that egress settings and new hosted agent versions follow your rules, like Enforce mode, a default of deny, and only approved destinations. Start in Audit to see what doesn’t comply, then switch to Deny to block noncompliant changes. Sessions that are already running keep going uninterrupted. The governance preview starts in Canada Central, Spain Central and Korea Central.

Above Security runs its AI investigative agents on hosted agents inside its own network:

“Insider risk is an investigation problem, not a policy problem, and Microsoft Foundry gives our AI investigative agents a secure home on Azure. With hosted agents in Foundry Agent Service running inside our own network and Claude served natively through Foundry, we can bring our agents to Azure customers without rewriting them.”

Amir Boldo, CPTO & Co-founder, Above Security

Status: Egress controls are generally available (GA). Azure Policy governance is in public preview. See Add guardrails to a hosted agent and Govern hosted agent egress with Azure Policy.

Deploy: run agents on clusters you already operate (public preview targeted for early December)

With this new deployment option, Foundry runs the agent runtime on your Azure Kubernetes Service (AKS) cluster. You build, deploy and call agents through Foundry the same way you do today, with the same APIs, azd flow and endpoint. Each session runs as its own pod in a lightweight VM (AKS pod sandboxing), so sessions stay isolated from each other. Your networking, container registry, policies and capacity stay yours.

Managed Hosted Agents are the best fit when you want Foundry to operate the hosting infrastructure for you. The option to BYO-AKS is designed for organizations that already operate AKS as a platform or need agent workloads to run within an infrastructure, network or compliance boundary they manage. It gives customers a choice of operating model without changing how developers work with agents in Foundry.

Your platform team controls the cluster capacity and scaling, network configuration, container supply chain, storage settings and infrastructure monitoring. You can apply existing virtual networks, private connectivity, DNS, routing, firewall and egress controls; choose node pools and registry integrations; and use your established storage and observability practices.

Responsibility is shared. Foundry manages the agent lifecycle and the Foundry-managed integration components. You operate the AKS cluster and its supporting resources, such as networking, node pools and storage.

OctopusOS runs on hosted agents today and sees the AKS deployment as the way to extend into its customers’ own environments:

“At OctopusOS, our customers – like accounting firms handling sensitive client data – need agents to run where their data and compliance boundaries are. Foundry Agent Service already gives us a managed, governed agent runtime; bringing our own AKS lets us extend that same experience into customer-controlled environments without rebuilding our platform.”

Ran Tao, CEO & Founder, OctopusOS

Status: Public preview is targeted for early December. Sign up now and tell us what you need.

Recover: keep long-running jobs going through restarts and long pauses (GA)

With resilient execution, agents that opt in can recover long jobs after a crash, restart or redeploy instead of starting over, and reconnecting clients can pick up the streamed output. Recovery reruns your handler, so save progress as you go and make sure actions like sending an email aren’t repeated.

Sessions can also wait longer between requests. You can set the idle timeout per agent version from 2 minutes to 4 hours (15 minutes by default). Without memory snapshots, session files survive idle periods, and a session is deleted after 30 days of inactivity.

For full workflow orchestration, we’re working with Temporal. Customers who want to combine Temporal’s durable workflows with hosted agents can contact Temporal for early access to the integration. Public preview is planned for early 2027.

Status: Resilient execution and configurable idle timeout are generally available (GA). See Resilience for long-running hosted agents.

Accelerate: cut cold starts with memory snapshots (public preview)

Cold starts add up when every new session imports the same libraries and loads the same data. With memory snapshots, Foundry captures your agent once it’s ready and restores that state for new sessions, so they skip repeated startup work. You turn it on per agent version, in Python or .NET.

One catch: a snapshot restores your agent’s ready-to-run starting point, not a running session. Memory and local files, including $HOME, don’t survive an idle period in snapshot sessions, so keep state you need later in external storage, or leave snapshots off.

Status: Public preview. See Enable memory snapshots for hosted agents.

Connect: bring your A2A agent (public preview)

If you already built an Agent2Agent (A2A) v1.0 agent, you can now host it on Foundry with A2A passthrough (preview) and keep your own message and task logic. A small Python adapter wraps your existing agent card and handler, and Foundry handles the endpoint, authentication and compute. The preview supports JSON-RPC, without streaming or push notifications for now, and works in all supported Foundry regions with no enrollment.

Status: Public preview. See Host an A2A-native agent.

See it at Ignite

If you’re attending Microsoft Ignite 2026, or watching on-demand content later, be sure to check out these sessions:

Get started

Tell us what’s still in the way

What still keeps your hosted agent out of production? Tell us in the comments what you’re trying to run and what’s blocking it. Most of what’s in this post started as exactly that kind of feedback.

Author

Muzz Imam
Principal Product Manager

Muzz Imam is a Principal Product Manager on Microsoft Foundry, where he works on the agent platform: hosted agents, network egress controls, private CA trust, deploying agents to your own AKS clusters, and cost control. He spends most of his time with customers taking agents from pilot to production.

Work in Microsoft Foundry developing the agent platform.

0 comments