Network communication between two tier 3 vnets

[brooke-hamilton]

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

• Documentation exists in the tier 3 example README.md to describe how to enable traffic between two tier 3 vnets.
• Optional: automation exists in the tier 3 example (either within the Bicep template or as an additional Bicep template).
• If the optional automation (above) is not implemented with this work, then an AZ CLI command or commands should be shown in the tier 3 example README.md along with the documentation to show how to implement the settings.

[brooke-hamilton]

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.

[brooke-hamilton]

I will update the ACs on this to enable peering between every tier 3 and tiers 0, 1, 2.

Done.