Clarify listener disablement behavior for Key Vault connectivity scen… - #2104
Open
jinyi (jinyi-ms) wants to merge 1 commit into
Open
Clarify listener disablement behavior for Key Vault connectivity scen…#2104jinyi (jinyi-ms) wants to merge 1 commit into
jinyi (jinyi-ms) wants to merge 1 commit into
Conversation
…arios During a customer investigation, a scenario where Application Gateway could not reach Key Vault due to NSG blocking a Private Endpoint was initially interpreted as matching the article statement "Application Gateway cannot access Key Vault". However, after discussion with TA Eric Ashton, it was confirmed that transient network connectivity failures do not disable listeners. Listener disablement applies to Key Vault configuration or access errors such as 401, 403, and 404 responses. The current wording may lead customers and support engineers to interpret network connectivity failures as conditions that disable listeners. Consider clarifying the distinction between: ・Network connectivity failures (NSG blocking, routing issues, temporary connectivity problems) ・Key Vault configuration/access errors (401, 403, 404, deleted or disabled certificates, permission issues) This clarification would help prevent misinterpretation and align the article with the documented statement that transient connectivity problems do not impact listeners.
prmerger-automator
Bot
requested a review
from Kaushik Ainapure (kaushika-msft)
August 12, 2026 09:58
|
jinyi (@jinyi-ms) : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
Bot
added
azure-application-gateway/svc
Change sent to author
labels
Contributor
|
Learn Build status updates of commit a6ad6be: ✅ Validation status: passed
For more details, please refer to the build report. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The current wording may lead readers to interpret network connectivity failures as conditions that disable listeners.
Consider clarifying the distinction between transient network connectivity issues and Key Vault configuration/access errors (401, 403, 404) that can result in listener disablement.
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:
We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.
After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.