Forum Discussion
Microsoft Foundry External MCP Server Traffic Routing via Corporate Firewall
Jamony covered the routing checks, so this is only about why a call that works can leave no trace in the firewall logs. The firewall writes nothing until a diagnostic setting sends the logs somewhere, and the table depends on that setting. With the legacy Azure diagnostics destination, rows land in AzureDiagnostics, not in AZFWApplicationRule or AZFWNetworkRule. With the resource specific destination they land in the AZFW tables. Query both, and wait up to 30 minutes after changing the setting before you test again.
On whether it's supported, Learn's table of tools with network isolation lists MCP as supported through your VNet subnet, and the Foundry networking page says to make sure no TLS inspection happens in the firewall. If both tables stay empty after a fresh call, I can't tell from outside whether the tool traffic is leaving through your subnet, so the support case Jamony described is the next step.