Skip to content

Commit 11a5fe6

Browse files
authored
Simplify peering status explanation in 4-create.md
Removed redundant explanation about peering status changes.
1 parent 994b6f7 commit 11a5fe6

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

  • learn-pr/wwl-azure/configure-vnet-peering/includes

learn-pr/wwl-azure/configure-vnet-peering/includes/4-create.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,5 +28,3 @@ In the Azure portal, you can check the connectivity status of the virtual networ
2828
- For deployment with the Azure Resource Manager, the two primary status conditions are **Initiated** and **Connected**. For the classic deployment model, the **Updating** status condition is also used.
2929

3030
- When you create the initial peering _to_ the second (remote) virtual network from the first virtual network, the peering status for the first virtual network is **Initiated**.
31-
32-
- When you create the subsequent peering _from_ the second virtual network to the first virtual network, the peering status for both the first and remote virtual networks is **Connected**. In the Azure portal, you can see the status for the first virtual network change from **Initiated** to **Connected**.

0 commit comments

Comments
 (0)