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
Copy file name to clipboardExpand all lines: articles/virtual-network-manager/how-to-configure-cross-tenant-cli.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.custom: template-how-to
10
10
#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.
11
11
---
12
12
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
14
14
15
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 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.
16
16
@@ -38,7 +38,7 @@ Creation of the scope connection begins on the central management tenant with a
38
38
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}`.
39
39
40
40
```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
42
42
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"
43
43
```
44
44
@@ -50,14 +50,14 @@ After you create the scope connection, you switch to your target tenant for the
50
50
51
51
```azurecli
52
52
53
-
# Log in to target managed tenant
53
+
# Log in to the target managed tenant
54
54
# Change the --tenant value to the appropriate tenant ID
55
55
az login --tenant "12345678-12a3-4abc-5cde-678909876543"
56
56
```
57
57
58
58
You're required to complete authentication with your organization, based on your organization's policies.
59
59
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.
61
61
62
62
```azurecli
63
63
# Set the Azure subscription
@@ -77,7 +77,7 @@ After you create the scope connection, you switch to your target tenant for the
77
77
az network manager connection subscription show --name "toCentralManagementTenant"
78
78
```
79
79
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:
81
81
82
82
```azurecli
83
83
# View the subscription added to the network manager
@@ -95,7 +95,7 @@ az network manager group static-member create --network-group-name "CrossTenantN
95
95
```
96
96
## Delete network manager configurations
97
97
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:
Copy file name to clipboardExpand all lines: articles/virtual-network-manager/how-to-configure-cross-tenant-portal.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.custom: template-how-to
12
12
13
13
# Configure a cross-tenant connection in Azure Virtual Network Manager Preview - portal
14
14
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.
16
16
17
17
> [!IMPORTANT]
18
18
> 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
55
55
1. Select **Create a connection**.
56
56
57
57
:::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**.
59
59
60
60
:::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.":::
61
61
@@ -64,9 +64,9 @@ After you create the scope connection, switch to the target managed tenant. Conn
64
64
After you create both connections, it's time to verify the connection on the central management tenant:
65
65
66
66
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**.
68
68
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.":::
0 commit comments