Azure AD B2B in government and national clouds
Microsoft Azure national clouds are physically isolated instances of Azure. B2B collaboration isn't enabled by default across national cloud boundaries, but you can use Microsoft cloud settings (preview) to establish mutual B2B collaboration between the following Microsoft Azure clouds:
- Microsoft Azure global cloud and Microsoft Azure Government
- Microsoft Azure global cloud and Microsoft Azure China 21Vianet
B2B collaboration across Microsoft clouds
To set up B2B collaboration between tenants in different clouds, both tenants need to configure their Microsoft cloud settings to enable collaboration with the other cloud. Then each tenant must configure inbound and outbound cross-tenant access with the tenant in the other cloud. For details, see Microsoft cloud settings (preview).
B2B collaboration within the Microsoft Azure Government cloud
Within the Azure US Government cloud, B2B collaboration is enabled between tenants that are both within Azure US Government cloud and that both support B2B collaboration. Azure US Government tenants that support B2B collaboration can also collaborate with social users using Microsoft, Google accounts, or email one-time passcode accounts. If you invite a user outside of these groups (for example, if the user is in a tenant that isn't part of the Azure US Government cloud or doesn't yet support B2B collaboration), the invitation will fail or the user won't be able to redeem the invitation. For Microsoft accounts (MSAs), there are known limitations with accessing the Azure portal: newly invited MSA guests are unable to redeem direct link invitations to the Azure portal, and existing MSA guests are unable to sign in to the Azure portal. For details about other limitations, see Azure Active Directory Premium P1 and P2 Variations.
How can I tell if B2B collaboration is available in my Azure US Government tenant?
To find out if your Azure US Government cloud tenant supports B2B collaboration, do the following:
In a browser, go to the following URL, substituting your tenant name for <tenantname>:
"tenant_region_scope"in the JSON response:
"tenant_region_scope":"USGOV”appears, B2B is supported.
"tenant_region_scope":"USG"appears, B2B is not supported.
See the following articles on Azure AD B2B collaboration:
Pošlji in prikaži povratne informacije za