Skip to content

Commit ed3b3cd

Browse files
committed
edit pass: how-to-configure-cross-tenant
1 parent f00a5d1 commit ed3b3cd

File tree

2 files changed

+10
-10
lines changed

2 files changed

+10
-10
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.custom: template-how-to
1010
#customerintent: As a cloud admin, I need to manage multiple tenants from a single network manager so that I can easily manage all network resources governed by Azure Virtual Network Manager.
1111
---
1212

13-
# Configure a cross-tenant connection in Azure Virtual Network Manager - CLI
13+
# Configure a cross-tenant connection in Azure Virtual Network Manager Preview - CLI
1414

1515
In this article, you'll learn how to create [cross-tenant connections](concept-cross-tenant.md) in Azure Virtual Network Manager by using the [Azure CLI](/cli/azure/network/manager/scope-connection). Cross-tenant support allows organizations to use a central network manager for managing virtual networks across tenants and subscriptions.
1616

@@ -38,7 +38,7 @@ Creation of the scope connection begins on the central management tenant with a
3838
In this task, you set up a scope connection to add a subscription from a target tenant. If you want to use a management group, modify the `–resource-id` argument to look like `/providers/Microsoft.Management/managementGroups/{mgId}`.
3939

4040
```azurecli
41-
# Create scope connection in the network manager in the central management tenant
41+
# Create a scope connection in the network manager in the central management tenant
4242
az network manager scope-connection create --resource-group "myRG" --network-manager-name "myAVNM" --name "ToTargetManagedTenant" --description "This is a connection to manage resources in the target managed tenant" --resource-id "/subscriptions/13579864-1234-5678-abcd-0987654321ab" --tenant-id "24680975-1234-abcd-56fg-121314ab5643"
4343
```
4444

@@ -50,14 +50,14 @@ After you create the scope connection, you switch to your target tenant for the
5050

5151
```azurecli
5252
53-
# Log in to target managed tenant
53+
# Log in to the target managed tenant
5454
# Change the --tenant value to the appropriate tenant ID
5555
az login --tenant "12345678-12a3-4abc-5cde-678909876543"
5656
```
5757

5858
You're required to complete authentication with your organization, based on your organization's policies.
5959

60-
1. Enter the following command to set the subscription and to create the cross-tenant connection on the central management tenant. The subscription is the same as the one that the connection referenced in the previous step.
60+
1. Enter the following commands to set the subscription and to create the cross-tenant connection on the central management tenant. The subscription is the same as the one that the connection referenced in the previous step.
6161

6262
```azurecli
6363
# Set the Azure subscription
@@ -77,7 +77,7 @@ After you create the scope connection, you switch to your target tenant for the
7777
az network manager connection subscription show --name "toCentralManagementTenant"
7878
```
7979
80-
1. Switch back to the central management tenant. Use the `show` command for the network manager to show the subscription added via the cross-tenant scope's property:
80+
1. Switch back to the central management tenant. Use the `show` command for the network manager to show the subscription added via the property for cross-tenant scopes:
8181
8282
```azurecli
8383
# View the subscription added to the network manager
@@ -95,7 +95,7 @@ az network manager group static-member create --network-group-name "CrossTenantN
9595
```
9696
## Delete network manager configurations
9797

98-
Now that the virtual network is in the network group, configurations are applied. To remove the static member or cross-tenant resources, use the corresponding delete commands:
98+
Now that the virtual network is in the network group, configurations are applied. To remove the static member or cross-tenant resources, use the corresponding `delete` commands:
9999

100100
```azurecli
101101

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.custom: template-how-to
1212

1313
# Configure a cross-tenant connection in Azure Virtual Network Manager Preview - portal
1414

15-
In this article, you'll learn how to create [cross-tenant connections](concept-cross-tenant.md) in Azure Virtual Network Manager by using the Azure portal. First, you'll create the scope connection on the central network manager. Then, you'll create the network manager connection on the connecting tenant and verify the connection. Last, you'll add virtual networks from different tenants to your network group and verify. After you complete all the tasks, you can centrally manage the resources of other tenants from single network manager.
15+
In this article, you'll learn how to create [cross-tenant connections](concept-cross-tenant.md) in Azure Virtual Network Manager by using the Azure portal. First, you'll create the scope connection on the central network manager. Then, you'll create the network manager connection on the connecting tenant and verify the connection. Last, you'll add virtual networks from different tenants to your network group and verify. After you complete all the tasks, you can centrally manage the resources of other tenants from a single network manager.
1616

1717
> [!IMPORTANT]
1818
> Azure Virtual Network Manager is currently in public preview. We provide this preview version without a service-level agreement, and we don't recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
@@ -55,7 +55,7 @@ After you create the scope connection, switch to the target managed tenant. Conn
5555
1. Select **Create a connection**.
5656

5757
:::image type="content" source="media/how-to-configure-cross-tenant-portal/create-connection-target.png" alt-text="Screenshot of the pane for cross-tenant connections.":::
58-
1. On the **Create a connection** page, enter the information for your central network manager tenant, and then select **Create**.
58+
1. On the **Create a connection** page, enter the information for your central management tenant, and then select **Create**.
5959

6060
:::image type="content" source="media/how-to-configure-cross-tenant-portal/create-connection-settings-target.png" alt-text="Screenshot of settings for creating a cross-tenant connection.":::
6161

@@ -64,9 +64,9 @@ After you create the scope connection, switch to the target managed tenant. Conn
6464
After you create both connections, it's time to verify the connection on the central management tenant:
6565

6666
1. On your central management tenant, select your network manager.
67-
1. Select **Cross-tenant connections** under **Settings**, and verify your cross-tenant connection is listed as **Connected**.
67+
1. Select **Cross-tenant connections** under **Settings**, and verify that your cross-tenant connection is listed as **Connected**.
6868

69-
:::image type="content" source="media/how-to-configure-cross-tenant-portal/verify-status.png" alt-text="Screenshot that shows a cross-connection status of Connected.":::
69+
:::image type="content" source="media/how-to-configure-cross-tenant-portal/verify-status.png" alt-text="Screenshot that shows a cross-connection status of Connected.":::
7070

7171
## Add static members to a network group
7272

0 commit comments

Comments
 (0)