Hello friends,
Today I’m super excited to announce that the capability to collaborate across Microsoft clouds is generally available! This means there’s now support for Azure Active Directory (Azure AD) B2B collaboration across the following Microsoft clouds:
- Azure Commercial and Azure Government clouds
- Azure Commercial and Azure China clouds (operated by 21Vianet)
Many of you are already using Azure AD, part of Microsoft Entra, to collaborate with external users like suppliers, partners, and vendors within a Microsoft cloud. We heard you also need to share and collaborate with organizations hosted by Microsoft clouds that are different from the cloud hosting your organization. Until now, to do this, you’ve had to go through the complex process of setting up tenants in multiple clouds and issuing different accounts to the same user. But now, your users can collaborate seamlessly across Microsoft clouds using their primary identities, whether your organizations are in the Azure Commercial, Government, or China clouds.
Start collaborating across Microsoft clouds in three simple steps
Let’s walk through an example of how Contoso Industries, an organization in the Azure Government cloud, collaborates with their partners in the Azure Commercial cloud.
Contoso Industries supplies mission critical equipment to government agencies and commercial organizations. Given the sensitive nature of business, the government requires Contoso Industries to be hosted in the Government cloud.
Contoso Industries also has commercial partners like Woodgrove, which provides software for the equipment that Contoso Industries manufactures. Now, with the capability to collaborate across Microsoft clouds, Contoso Industries users can invite Woodgrove users to collaborate with them and give them access to the inventory application or SharePoint documents.
Let’s look at how to make this happen!
Step 1: Enable Microsoft cloud settings for External Identities
The Contoso Industries admin, Dean, enables the setting to collaborate with the Azure Commercial cloud by navigating to External Identities cross-tenant access settings in the Azure portal.
Enable Microsoft cloud settings in External Identities.
Dean then adds Woodgrove tenant to their list of partners in cross-tenant access settings. The admin at Woodgrove also makes corresponding changes in the Azure portal.
Dean can make additional changes, like leveraging granular controls to only allow specific users to access specific applications. This can further secure these collaborations. After completing these changes, Contoso Industries users can now invite users from Woodgrove to collaborate on the line-of-business apps, SaaS apps, Power BI reports, and SharePoint Online sites, documents, and files that are hosted by Contoso Industries.
Learn more about how to enable collaboration across Microsoft clouds.
Step 2: Govern external users from other Microsoft clouds on Day 1
Contoso Industries wants to ensure users from different clouds are governed so that the external users only have access to Contoso Industries resources for a limited time. Dean adds Woodgrove as a trusted connected organization.
Add connected organization from another Microsoft cloud.
Dean can now assign access packages that include specific resources, access reviews, and sponsors for approvals. This makes it easy for Woodgrove users to self-service onboard and to be governed by Contoso Industries access policies immediately.
Learn more about how to use connected organizations and access packages to onboard and govern users from a different Microsoft cloud.
Step 3: Secure and monitor external collaboration across Microsoft clouds
Dean wants to secure the resources that are shared with Woodgrove users. Because Woodgrove users are guest users in Contoso Industries, all Conditional Access policies can be applied to Woodgrove users, like requiring multi-factor authentication (MFA) before accessing Contoso Industries resources.
Contoso Industries can also leverage cross-tenant access settings to trust MFA or compliant Azure AD joined devices from Woodgrove, which enables a seamless collaboration experience for Woodgrove users while keeping their security posture intact.
Trust MFA and device signals from another Azure AD tenant.
When a Woodgrove user accesses resources in Contoso Industries, Dean can monitor the user’s activities using sign-in logs. Dean can also use the cross-tenant access activity workbook to get visibility into the resources Woodgrove users are accessing.
What customers are saying
We got some great feedback from customers like you during the previews:
“Collaboration across Microsoft clouds will enable us to finally migrate the last dozen or so apps from ADFS to Azure AD. ADFS has historically been our solution to provide SSO for both our corporate and China users to apps that they all need. Once this migration is complete, it will help us deprecate ADFS, greatly reducing cost, increasing reliability, and minimizing our security footprint.”
-Customer in financial services industry
“We’ve been unable to move our users to our government tenant due to lack of collaboration, and this feature will unblock that move!”
-Customer in engineering and construction industry
We love hearing from you, so please share your feedback on these updates through the Azure forum or by tagging @AzureAD on Twitter.
Robin Goldstein
Director of Product Management, Microsoft identity
Twitter: @RobinGo_MS
LinkedIn: Robin Goldstein | LinkedIn
Learn more about Microsoft identity:
- Return to the Azure Active Directory Identity blog home
- Join the conversation on Twitter and LinkedIn
- Share product suggestions on the Azure Feedback Forum
Microsoft
