You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<maml:para>The first command gets a virtual network object called vnet1 associated with resource group “MyResourceGroup”. Similarly, the second command gets a virtual network object called vnet2 associated with the same resource group. The third command then adds a Vnet peering link from vnet1 to vnet2. This link is named LinkToVnet2. Finally, the forth command adds a link from vnet2 to vnet1 called LinkToVnet1. Note that vnet1 and vnet2 are assumed to be previously created in this example. Note that a link must be created from vnet1 to vnet2 and vice versa in order for peering to work.</maml:para>
7192
7192
<maml:para />
@@ -7199,9 +7199,10 @@ Id : /subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxx
<maml:para>This command gets a previously created Virtual Network Peering called “LinkToVNet2” located in “MyVirtualNetwork” within the resource group called “MyResourceGroup”</maml:para>
<maml:para>This command deletes a previously created Virtual Network Peering called “LinkToVNet2” located in “MyVirtualNetwork” within the resource group called “MyResourceGroup”
36618
-
</maml:para>
36617
+
<maml:para>This command deletes a previously created Virtual Network Peering called “LinkToVNet2” located in “MyVirtualNetwork” within the resource group called “MyResourceGroup”</maml:para>
<maml:para>This example shows how to change the forwarded traffic configuration to true instead of the default false option on a previously established VNet peering link. The first command gets the associated information regarding the link, in this case, called LinkToVNet2 within “MyResourceGroup” in virtual network “MyVirtualNetwork”. The next command updates the variable property to true. The final command changes the setting for the “LinkToVNet2” virtual network peering link to true.</maml:para>
<maml:para>This example shows how to change the Virtual Network Access property configuration to false instead of the default true option on a previously established VNet peering link. The first command gets the associated information regarding the link, in this case, called LinkToVNet2 within “MyResourceGroup” in virtual network “MyVirtualNetwork”. The next command updates the variable associated with the property to false. The final command changes the setting for the “LinkToVNet2” virtual network peering link to false.</maml:para>
<maml:para>This example shows how to change the gateway transit property configuration to true instead of the default false option on a previously established VNet peering link. The first command gets the associated information regarding the link, in this case, called LinkToVNet2 within “MyResourceGroup” in virtual network “MyVirtualNetwork”. The next command updates the variable associated with this property to true. The final command changes the setting for the “LinkToVNet2” virtual network peering link to true. By changing this property to true, the peer VNet is allowed to use your VNet gateway.</maml:para>
0 commit comments