-
Notifications
You must be signed in to change notification settings - Fork 146
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.
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
Network communication between two tier 3 vnets #634
Labels
bicep
Related to Bicep code
Comments
I will update the ACs on this to enable peering between every tier 3 and tiers 0, 1, 2. @Phydeauxman is doing similar work - will consult with him on implementation. |
Done. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Benefit/Result/Outcome
So that customers have clear guidance, and possibly some automation, to allow two tier 3 vnets to communicate with each other.
Description
Network traffic is enabled by default between every tier 3 vnet and tiers 0, 1, and 2. However, each tier 3 vnet cannot communicate with other tier 3 vnets by default. This work involves adding guidance to the tier 3 example explaining how to enable traffic between the vnets, and possibly some Bicep automation code.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: