Skip to content

Commit 85af653

Browse files
committed
Update
1 parent 2967bc2 commit 85af653

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/external-identities/cross-cloud-settings.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,9 @@ To set up B2B collaboration between partner organizations in different Microsoft
3434

3535
After each organization has completed these steps, Azure AD B2B collaboration between the organizations is enabled.
3636

37+
> [!NOTE]
38+
> B2B direct connect is not supported for collaboration with Azure AD tenants in a different Microsoft cloud.
39+
3740
## Before you begin
3841

3942
- **Obtain the partner's tenant ID.** To enable B2B collaboration with a partner's Azure AD organization in another Microsoft Azure cloud, you'll need the partner's tenant ID. Using an organization's domain name for lookup isn't available in cross-cloud scenarios.
@@ -81,9 +84,6 @@ Follow these steps to add the tenant you want to collaborate with to your Organi
8184

8285
1. If you want to change the cross-tenant access settings for this organization, select the **Inherited from default** link under the **Inbound access** or **Outbound access** column. Then follow the detailed steps in these sections:
8386

84-
> [!NOTE]
85-
> B2B direct connect is not supported for collaboration with Azure AD tenants in a different Microsoft cloud.
86-
8787
- [Modify inbound access settings](cross-tenant-access-settings-b2b-collaboration.md#modify-inbound-access-settings)
8888
- [Modify outbound access settings](cross-tenant-access-settings-b2b-collaboration.md#modify-outbound-access-settings)
8989

0 commit comments

Comments
 (0)