Skip to content

Commit 857bed9

Browse files
committed
Updates
1 parent 78e89b4 commit 857bed9

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

articles/virtual-network-manager/concept-cross-tenant.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,11 @@ Once both cross-tenant connections exist and the scopes are exactly the same, a
3737

3838
A cross-tenant connection can only be established and maintained when both objects from each party exist. When one of the connections is removed, the cross-tenant connection is broken. If you need to delete a cross-tenant connection, you'll perform the following:
3939

40-
- Remove cross-tenant connections from management tenant
41-
- Remove connection from managed tenant
40+
- Remove cross-tenant connection from the network manager side via Cross-tenant connections blade.
41+
- Remove cross-tenant connection from the tenant side via Virtual network manager hub's Cross-tenant connections blade.
42+
43+
> [!NOTE]
44+
> Once a connection is removed from either side, the network manager will no longer be able to view or manage the tenant's resources under that former connection's scope.
4245
## Required Permissions
4346

4447
To use cross-tenant connection in Azure Virtual Network Manager, users need the following permissions:

0 commit comments

Comments
 (0)