# Microsoft expands Foundry Agent Service with voice GA, hosted agent controls and Microsoft 365 accounts

published: 2026-11-18T20:05:27.478Z
topic: infrastructure
source: https://devblogs.microsoft.com/foundry/whats-new-in-foundry-agent-service-at-ignite-2026/
url: https://aiagentnews.io/stories/microsoft-expands-foundry-agent-service-with-voice-ga-hosted-agent-controls-and

Microsoft announced at Ignite 2026 that voice agents in Foundry Agent Service are now generally available, along with new tool connections, hosted agent controls and continuous improvement features. Hosted agents can also receive their own Entra Agent ID, email address and Teams presence when supported.

Voice agents in Foundry Agent Service are now generally available, and can be added to existing agents without rewriting them, with native telephony connections to phone and contact center systems. Web Search powered by Web IQ is generally available for prompt agents, and computer use and browser automation are now generally available, with session recordings kept in customer-owned storage.

For hosted agents, shared subnet IPs and network egress controls are generally available, and long-running resiliency is generally available as an opt-in feature. Memory snapshots and private certificate authority trust are in public preview, and deployment to customer-owned AKS is planned for public preview in early December. Default quotas are 1,000 to 2,000 concurrent sessions per subscription and region.

Supported hosted agents can get their own Entra Agent ID, email address, Microsoft Teams presence and place in the org chart, and Foundry is integrating with Microsoft 365 Resources for Agents for a mailbox, calendar and OneDrive workspace. Insights for production traces is generally available, with annotations, evaluation datasets and Agent Optimizer in preview or public preview.

## Why it matters if you build agents

Developers building voice or browser-based agents can now rely on generally available features rather than previews. Hosted agents that crash or restart mid-job can resume only if the handler saves its progress and avoids duplicate side effects, since recovery reruns the handler.

Teams should audit outbound traffic before enforcing egress rules to build an allowlist from real usage. Several controls, including memory snapshots and Azure Policy governance, are still in preview, so their behavior may change before general availability.
