AI-103 Practice Question 22: Network Isolated Agent Tools
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 3 · question 2 of 10
A government contractor has deployed a Foundry resource with public network access disabled, a private endpoint for inbound traffic, and virtual network injection for the agent's outbound traffic. Their compliance rule is absolute: no agent traffic may leave the customer-defined network boundary or the Microsoft backbone. An architect has drafted an agent that uses four tools.
Which of these tools violates the rule as designed?
Show answer and explanation
Answer:
Microsoft's tool-support table for network-isolated deployments marks Bing grounding, web search and SharePoint grounding as supported, but over a public endpoint, and calls this out explicitly: these tools "work in network-isolated environments but communicate over the public internet… If your organization requires that all traffic remain within a private network, these tools may not meet your compliance requirements." Where a tool must be blocked outright, Azure Policy is the documented lever.
- A is wrong because the Azure AI Search tool is supported through a private endpoint. (One operational caveat from the same page: if an indexer must traverse private endpoints, set its executionEnvironment to "Private", or indexing fails silently.) - C is wrong because the Azure Functions tool routes through your VNet subnet, as do the MCP, OpenAPI and A2A tools. - D is wrong because code interpreter (like function calling) travels over the Microsoft backbone network, needs no private endpoint, and never traverses the public internet.
Reference: How to configure network isolation for Microsoft Foundry