Adding Your Firewall's CA Won't Fix Azure Hosted Agent Timeouts
Microsoft Foundry Principal Product Manager Muzz Imam explains why teams deploying hosted agents in locked-down networks still hit timeouts after registering their firewall's CA with Private CA trust: the platform's own Entra ID and managed identity traffic falls outside the scope of that trust mechanism. The actual fix is a no-decrypt rule for three specific Entra hosts on the firewall.
When a financial services team moves hosted agents into its own virtual network with public access disabled, TLS-inspecting firewalls on all outbound traffic, and private endpoints for Cosmos DB and Storage, the deployment succeeds but the Agents page spins and times out. The team's first instinct is to register the firewall's CA certificate with Private CA trust, a public preview feature that lets agents call internal services using corporate certificates. That fix does not work, and Muzz Imam, Principal Product Manager on the Microsoft Foundry team, explains why in a November 21, 2026 blog post.
The reason is a scope limitation: Private CA trust does not apply to the platform's own Microsoft Entra ID and managed identity traffic from the agent subnet. When the agent infrastructure signs in to Entra ID before calling your resources, that traffic is still being inspected and re-signed by the firewall. Adding the firewall's CA to the trust store changes nothing because the platform's sign-in path is excluded from the trust mechanism entirely. Imam reproduced this in a test subscription by routing the agent subnet's Entra traffic through a decrypting proxy; registering the proxy's CA made no difference, and a no-decrypt rule for the Entra hosts fixed it.
The actual fix has two parts. First, exclude three specific host patterns from TLS inspection: login.microsoftonline.com, {region}.login.microsoft.com, and control-{region}.identity.azure.net. Second, allow those hosts on the firewall plus the managed identity FQDNs from the Azure Container Apps firewall guidance or the AzureActiveDirectory service tag. If an NSG sits on the agent subnet, it needs a matching outbound rule for the same service tag. Private CA trust remains useful for what it was built for: letting tools, model gateways and agent code call internal services that use the company's own certificates.