updates

Author: Michael Bender

articles/virtual-network-manager/how-to-configure-cross-tenant-powershell.md

@@ -1,6 +1,6 @@
 ---
 title: Configure cross-tenant connection in Azure Virtual Network Manager - PowerShell
-description: #Required; article description that is displayed in search results. 
+description: Learn to connect Azure subscriptions in Azure Virtual Network Manager using cross-tenant connections for the management of virtual networks across subscriptions using Azure PowerShell.
 author: mbender-ms
 ms.author: mbender
 ms.service: virtual-network-manager
@@ -55,51 +55,84 @@ Set-AzContext -TenantId 12345678-12a3-4abc-5cde-678909876543
 Select-AzSubscription 87654321-abcd-1234-1def-0987654321ab
 
 # 
-New-AzNetworkManagerSubscriptionConnection -Name toContosoTenantNM -Description "This connection allows management of the tenant by a central management tenant" -NetworkManagerId "/subscriptions/13579864-1234-5678-abcd-0987654321ab/resourceGroups/$rg.name/providers/Microsoft.Network/networkManagers/"myAVNM""
+New-AzNetworkManagerSubscriptionConnection -Name toCentralManagementTenant -Description "This connection allows management of the tenant by a central management tenant" -NetworkManagerId "/subscriptions/13579864-1234-5678-abcd-0987654321ab/resourceGroups/myAVNMResourceGroup/providers/Microsoft.Network/networkManagers/"myAVNM""
 
 #
-Get-AzNetworkManagerSubscriptionConnection -Name toContosoTenantNM
+Get-AzNetworkManagerSubscriptionConnection -Name toCentralManagementTenant
 ```
 
 ## Verify the connection state is ‘Connected’ (via grid item ‘Status’)
 
-Switch back to the Contoso tenant, and performing a get on the network manager should show the subscription added via the cross tenant scopes property.
+Switch back to the central management tenant, and verify the subscription is added to the virtual network manager via the cross tenant scopes property.
 
 ```azurepowershell
 
-Get-AzNetworkManager -ResourceGroup $rg.name -Name "myAVN"
+Get-AzNetworkManager -ResourceGroup "myAVNMResourceGroup" -Name "myAVNM"
 
 ```
 
 ## Generate auth tokens for PowerShell
-From Azure Portal and Azure CLI we generate the auth tokens needed for the put static member request behind the scenes. Unfortunately, this is not possible (yet) via AVNM’s powershell cmdlets, so the tokens must be generated manually and the request must be sent via the ‘Invoke-RestMethod’ cmdlet
+For Azure Portal and Azure CLI, we generate the auth tokens needed for the put static member request behind the scenes. Unfortunately, this is not possible (yet) via AVNM’s pPowershell cmdlets, so the tokens must be generated manually and the request must be sent via the ‘Invoke-RestMethod’ cmdlet
 
 
-# Get the group you want to add the static members to
-$group = Get-AzNetworkManagerGroup -NetworkManagerName "myAVN" -ResourceGroup $rg.name -Name containsCrossTenantResources
+### Get the group you want to add the static members to
+$group = Get-AzNetworkManagerGroup -NetworkManagerName "myAVN" -ResourceGroup myAVNMResourceGroup -Name containsCrossTenantResources
 
 # Need to be modified
+
+```azurepowershell
+
 $networkManagerTenant = "24680975-1234-abcd-56fg-121314ab5643"
-$vnetTenant = "12345678-12a3-4abc-5cde-678909876543"
+$targetTenant = "12345678-12a3-4abc-5cde-678909876543"
 $staticMemberName = "crossTenantMember"
-$vnetResourceId = “/subscriptions/795fe552-a2fc-466a-b436-de4520b73dd2/resourceGroups/temp/providers/Microsoft.Network/virtualNetworks/Vnet1”
+$targetResourceID = “/subscriptions/87654321-abcd-1234-1def-0987654321ab/resourceGroups/temp/providers/Microsoft.Network/virtualNetworks/targetVnet01”
 
 # Everything after this can be copy/pasted
 $networkManagerToken = Get-AzAccessToken -TenantId $networkManagerTenant
-$vnetToken = Get-AzAccessToken -TenantId $vnetTenant
+$targetToken = Get-AzAccessToken -TenantId $targetTenant
 
 $authHeader = @{
    'Content-Type'='application/json'
    'Authorization'='Bearer ' + $networkManagerToken.Token
-   'x-ms-authorization-auxiliary'='Bearer ' + $vnetToken.Token
+   'x-ms-authorization-auxiliary'='Bearer ' + $targetToken.Token
 }
 
 $body = (@{
 	‘properties'= @{
-		'resourceId'=$vnetResourceId
+		'resourceId'=$targetResourceID
 	}
 } | ConvertTo-Json)
 
 $restUri = "https://management.azure.com" + $group.Id + "/staticMembers/" + $staticMemberName + "?api-version=2022-01-01"
 Invoke-RestMethod -Uri $restUri -Method Put -Headers $authHeader -Body $body
 
+```
+
+## Delete virtual network manager configurations
+
+Now that the virtual network is in the network group, configurations will be applied. To remove the static member or cross-tenant resources, using the commands below:
+
+```azurepowershell
+
+# delete connection on target managed tenant
+Remove-AzNetworkManagerScopeConnection -Name ToTargetManagedTenant -ResourceGroup "myAVNMResourceGroup" -NetworkManagerName "myAVNM"
+
+# delete static member group
+Remove-AzNetworkManagerStaticMember -Name crossTenantMember -ResourceGroup "myAVNMResourceGroup" -NetworkManagerName "myAVNM"–NetworkGroupName containsCrossTenantResources
+
+# Switch to ‘managed tenant’ if needed
+
+# delete connection on central management tenant
+
+Remove-AzNetworkManagerSubscriptionConnection -Name toCentralManagementTenant 
+
+```
+## Next steps
+
+> [!div class="nextstepaction"]
+
+- Learn more about [Security admin rules](concept-security-admins.md).
+
+- Learn how to [create a mesh network topology with Azure Virtual Network Manager using the Azure portal](how-to-create-mesh-network.md)
+
+- Check out the [Azure Virtual Network Manager FAQ](faq.md)