Merge pull request #201222 from jkdouglas/cross-cloud-direct-connect

Note that direct connect is not supported cross-cloud

Author: PRMerger4

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

@@ -34,6 +34,9 @@ To set up B2B collaboration between partner organizations in different Microsoft
 
 After each organization has completed these steps, Azure AD B2B collaboration between the organizations is enabled.
 
+> [!NOTE]
+> B2B direct connect is not supported for collaboration with Azure AD tenants in a different Microsoft cloud.
+
 ## Before you begin
 
 - **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.

articles/active-directory/external-identities/cross-tenant-access-overview.md

@@ -69,6 +69,9 @@ To set up B2B collaboration, both organizations configure their Microsoft cloud
 - Use B2B collaboration to invite a user in the partner tenant to access resources in your organization, including web line-of-business apps, SaaS apps, and SharePoint Online sites, documents, and files.
 - Apply Conditional Access policies to the B2B collaboration user and opt to trust device claims (compliant claims and hybrid Azure AD joined claims) from the user’s home tenant.
 
+> [!NOTE]
+> B2B direct connect is not supported for collaboration with Azure AD tenants in a different Microsoft cloud.
+
 For configuration steps, see [Configure Microsoft cloud settings for B2B collaboration (Preview)](cross-cloud-settings.md).
 
 > [!NOTE]