Skip to content

Commit 079a4c2

Browse files
authored
Simplify peering status conditions explanation
1 parent a9db4d8 commit 079a4c2

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

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

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,6 @@ In the Azure portal, you can check the connectivity status of the virtual networ
2525
> [!Important]
2626
> Your peering isn't successfully established until both virtual networks in the peering have a status of **Connected**.
2727
28-
- 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.
28+
- The two peering status conditions are **Initiated** and **Connected**.
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**.

0 commit comments

Comments
 (0)