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

In this article, you'll learn how to create cross-tenant connections 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.


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.


  • Two Azure tenants with virtual networks that you want to manage through Azure Virtual Network Manager. This article refers to the tenants as follows:
    • Central management tenant: The tenant where an Azure Virtual Network Manager instance is installed, and where you'll centrally manage network groups from cross-tenant connections.
    • Target managed tenant: The tenant that contains virtual networks to be managed. This tenant will be connected to the central management tenant.
  • Azure Virtual Network Manager deployed in the central management tenant.
  • These permissions:
    • The administrator of the central management tenant has a guest account in the target managed tenant.
    • The administrator guest account has Network Contributor permissions applied at the appropriate scope level (management group, subscription, or virtual network).

Need help with setting up permissions? Check out how to add guest users in the Azure portal and how to assign user roles to resources in the Azure portal.

Create a scope connection within a network manager

Creation of the scope connection begins on the central management tenant with a network manager deployed. This is the network manager where you plan to manage all of your resources across tenants.

In this task, you set up a scope connection to add a subscription from a target tenant:

  1. Go to Azure Virtual Network Manager.

  2. Under Settings, select Cross-tenant connections, and then select Create cross-tenant connection.

    Screenshot of cross-tenant connections in a network manager.

  3. On the Create a connection page, enter the connection name and target tenant information, and then select Create.

    Screenshot of settings entered to create a connection.

  4. Verify that the scope connection is listed under Cross-tenant connections and the status is Pending.

Create a network manager connection on a subscription in another tenant

After you create the scope connection, switch to the target managed tenant. Connect to the target managed tenant by creating another cross-tenant connection in the Virtual Network Manager hub:

  1. In the target tenant, search for virtual network manager and select Virtual Network Manager.

  2. Under Virtual network manager, select Cross-tenant connections.

    Screenshot of network managers in Virtual Network Manager on a target tenant.

  3. Select Create a connection.

    Screenshot of the pane for cross-tenant connections.

  4. On the Create a connection page, enter the information for your central management tenant, and then select Create.

    Screenshot of settings for creating a cross-tenant connection.

Verify the connection status

After you create both connections, it's time to verify the connection on the central management tenant:

  1. On your central management tenant, select your network manager.

  2. Select Cross-tenant connections under Settings, and verify that your cross-tenant connection is listed as Connected.

    Screenshot that shows a cross-connection status of Connected.

Add static members to a network group

Now, add virtual networks from both tenants into a network group for static members.


Currently, cross-tenant connections support only static memberships within a network group. Dynamic membership with Azure Policy is not supported.

  1. From your network manager, add a network group if needed.

  2. Select your network group, and then select Add virtual networks under Manually add members.

  3. On the Manually add members page, select Tenant:... next to the search box, select the linked tenant from the list, and then select Apply.

    Screenshot of available tenants to choose for static network group membership.

  4. To view the available virtual networks from the target managed tenant, select authenticate and proceed through the authentication process. If you have multiple Azure accounts, select the one you're currently signed in with that has permissions to the target managed tenant.

  5. Select the virtual networks to include in the network group, and then select Add.

Verify group members

In the final step, you verify the virtual networks that are now members of the network group.

On the Overview page of the network group, select View group members. Verify that the virtual networks that you added manually are listed.

Screenshot of network group membership.

Next steps

In this article, you deployed a cross-tenant connection between two Azure subscriptions. To learn more about using Azure Virtual Network Manager, see: