Skip to content

Update configuration-infrastructure.md #125871

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

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

Update configuration-infrastructure.md #125871

wants to merge 1 commit into from
+14 −0

Conversation

AgnesLi666
Copy link
Contributor

Hello there,

I am from MS support Azure networking team. The customer is having access issue to Key Vault when KV has Private Endpoint configured. Customer has customer DNS server configured and could not understand why his APPGW Vnet must have a vnet link with key vault private DNS zone. He also mentioned none of our public doc mentioned this.

It is very important to let them know that some of the domains will always be resolved by Azure default DNS. And they must link the private DNS zone with the Vnet if they want to make it work.
@AgnesLi666
Update configuration-infrastructure.md
719232d 
Hello there, 

I am from MS support Azure networking team. The customer is having access issue to Key Vault when KV has Private Endpoint configured. Customer has customer DNS server configured and could not understand why his APPGW Vnet must have a vnet link with key vault private DNS zone. He also mentioned none of our public doc mentioned this. 

It is very important to let them know that some of the domains will always be resolved by Azure default DNS. And they must link the private DNS zone with the Vnet if they want to make it work.
@prmerger-automator PRMerger Automator
Copy link
Contributor

@AgnesLi666 : Thanks for your contribution! The author(s) have been notified to review your proposed change.
@learn-build-service-prod Learn Build Service (PROD)
Copy link
Contributor

Learn Build status updates of commit 719232d:

💡 Validation status: suggestions

File Status Preview URL Details
articles/application-gateway/configuration-infrastructure.md 💡Suggestion Details

articles/application-gateway/configuration-infrastructure.md

  • Line 98, Column 1: [Suggestion: table-syntax-invalid - See documentation] Table syntax is invalid. Ensure your table includes a header and is surrounded by empty lines.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:
@v-dirichards
Copy link
Contributor

@greg-lindsay

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team
@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Feb 20, 2025
@v-ccolin
Copy link
Contributor

v-ccolin commented Apr 6, 2025

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team
@v-dirichards
Copy link
Contributor

I sent a Teams message to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aq-pr-triaged tracking label for the PR review team azure-application-gateway/svc Change sent to author do-not-merge qualifies-for-auto-merge
4 participants
@AgnesLi666 @v-dirichards @v-ccolin @greg-lindsay