From 633229061bab13759fdb3ba9ed21b15ad53f45fe Mon Sep 17 00:00:00 2001 From: AhmadAbdullah91 <91725950+AhmadAbdullah91@users.noreply.github.com> Date: Fri, 7 Nov 2025 17:21:38 +0300 Subject: [PATCH] Update FAQ with Private DNS zone information Added new FAQ entry regarding Private DNS zone linking in hub-spoke topology. --- articles/ai-foundry/agents/faq.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/articles/ai-foundry/agents/faq.yml b/articles/ai-foundry/agents/faq.yml index be797eb8566..61ce9a8ef77 100644 --- a/articles/ai-foundry/agents/faq.yml +++ b/articles/ai-foundry/agents/faq.yml @@ -108,4 +108,8 @@ sections: - question: | What additional configuration is needed if I want to add tools to my agents? answer: | - The template provides support for the built-in tools: Code Interpreter, File Search, Azure AI Search, Cosmos DB (all tools that use the Bring-Your-Own (BYO) resource connections). To configure tools that require the creation of a new connection, you must create a private endpoint from your `peSubnet`` and create a private link from the Azure Resource. \ No newline at end of file + The template provides support for the built-in tools: Code Interpreter, File Search, Azure AI Search, Cosmos DB (all tools that use the Bring-Your-Own (BYO) resource connections). To configure tools that require the creation of a new connection, you must create a private endpoint from your `peSubnet`` and create a private link from the Azure Resource. + - question: | + In hub-spoke like topology, If I have Private DNS zone(s) linked to my hub Vnet, do I still need to link them to spoke Vnet(s) such as Agent Vnet? + answer: | + Yes, you need to link the spoke VNet to the private DNS zone to resolve DNS names from the spoke network. Linking the hub VNet to the private DNS zone is not enough, as VNet peering does not automatically propagate the DNS zone link. To ensure resources in spoke VNets can resolve private endpoints, each spoke VNet (Agent Vnet) must have a link to the private DNS zone.