Skip to content

Update FAQ with Private DNS zone information #591

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update FAQ with Private DNS zone information #591

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion articles/ai-foundry/agents/faq.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
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?
Copy link

Copilot AI Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Multiple spelling and capitalization issues in the question:

  1. "hub-spoke like topology" should be "hub-spoke topology" (remove "like")
  2. "If" should be lowercase "if" since it's not the first word of the sentence
  3. "Vnet" should be "VNet" (capital N) consistently throughout to match Azure standard terminology and the capitalization used in the answer
Suggested change
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?
In a hub-spoke 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?

Copilot uses AI. Check for mistakes.
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.
Copy link

Copilot AI Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There appear to be trailing spaces at the end of this line. Trailing whitespace should be removed for consistency.

Suggested change
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.
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.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent capitalization: "Vnet" in "Agent Vnet" should be "VNet" (capital N) to match the standard Azure terminology and the capitalization used in the answer text ("Agent VNet", "spoke VNet", "spoke VNets").

Suggested change
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.
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.

Copilot uses AI. Check for mistakes.