Source: devblogs.microsoft.com/foundry/hosted-agents-foundry-agent-service-ignite-2026
Hosted agents in your own virtual network now share subnet IP addresses across sessions, which Microsoft says raises the planning estimate for a /24 to about 60,000 concurrent sessions. Each session still runs in its own VM-isolated sandbox, and the regional session quota becomes the practical limit for most teams.
Network egress controls are now generally available. Admins can attach an ordered list of allow and deny rules to an agent, and Foundry enforces them outside the agent's sandbox. An Audit mode logs requests that would be blocked before switching to Enforce, and Azure Policy governance for egress is in public preview in Canada Central, Spain Central and Korea Central.
Other updates include private CA trust, currently in public preview, which lets agents call internal services using a company's certificates with checks still enabled. Long-running resilient execution and a configurable idle timeout of 2 minutes to 4 hours are generally available, and memory snapshots and A2A passthrough are in public preview. Running hosted agents on customer-managed AKS clusters is targeted for public preview in early December.
Why it matters if you build agents
Teams with tight IP plans can run far more concurrent sessions without requesting a larger subnet, though the regional session quota still applies.
Egress rules are enforced outside agent code, so developers can restrict destinations without relying on the agent to behave, but should test header rewrites in a non-production environment first.
Recovered long jobs rerun the handler, so agents should save progress as they go and avoid repeating actions such as sending an email.
Get stories like this every weekday
One short email with the day's agent tooling news.