Blog Post

Microsoft Foundry Blog
11 MIN READ

Foundry Agents and Custom Engine Agents through the Corporate Firewall

graemefoster's avatar
graemefoster
Icon for Microsoft rankMicrosoft
Apr 01, 2026

Implementing checks and balances to allow your Foundry and Custom Engine Agents to be accessed through corporate firewalls.

It's easy to publish Foundry Agents and your own Custom Engine Agents, so they can be accessed in Teams and Copilot. But if you want to run your agents on your own private network you'll hit an issue...
Updated Mar 29, 2026
Version 1.0
GORANJANEVSKI's avatar
GORANJANEVSKI
Copper Contributor
May 01, 2026

How is this different from a solution I have seen from Microsoft involving Direct Line App Service Extension?  Frankly, that approach seems simpler as it only provisions via the Azure Portal.  Also, these public/private NAT network problems seem easier done there using web sockets.

Finally, which one of the two solutions - yours and the Direct Line App Service Extension support the agent talking to multiple channels simultaneously?  How much work in your solution to make it work with multiple channels?

Thanks,