Clarify default route breaks public comms for vnet #1145
Merged
Conversation
This file contains 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
Just had a customer case and we have no clarification about this
|
@PedroPerezMSFT, |
|
@cherylmc Hi Cheryl Please review these proposed contributions. Thanks. |
|
@yushwang - can you please review? |
|
Some wording changes required. Let me get to that later today. |
|
I don't know how to change to the branch and update the PR. So here goes: "Please note this will force all VNet egress traffic towards your on-premises site, and will prevent the VNet VMs from accepting public communication from the Internet directly, such RDP or SSH from the Internet to the VMs." @PedroPerezMSFT could you update your PR? Or we can close this one and I can make the update directly. Thanks, |
PedroPerezMSFT
commented
Apr 12, 2017
|
#sign-off |
rajumsys
pushed a commit
to rajumsys/azure-docs
that referenced
this pull request
May 4, 2017
Design updates to all ref sections in landing pages
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Just had a customer case and we have no clarification about this. I think it would be good to clarify beforehand and avoid customer pain.