Skip to content

Commit 42ff3e9

Browse files
authored
Merge pull request #230211 from MicrosoftDocs/main
Publish to live, Friday 4 AM PST, 3/10
2 parents f4d4635 + 881e030 commit 42ff3e9

File tree

130 files changed

+1565
-526
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

130 files changed

+1565
-526
lines changed

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

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: active-directory
55
ms.service: active-directory
66
ms.subservice: B2B
77
ms.topic: how-to
8-
ms.date: 02/14/2023
8+
ms.date: 03/03/2023
99

1010
ms.author: mimart
1111
author: msmimart
@@ -40,6 +40,9 @@ After each organization has completed these steps, Azure AD B2B collaboration be
4040
- **Decide on inbound and outbound access settings for the partner.** Selecting a cloud in your Microsoft cloud settings doesn't automatically enable B2B collaboration. Once you enable another Microsoft Azure cloud, all B2B collaboration is blocked by default for organizations in that cloud. You'll need to add the tenant you want to collaborate with to your Organizational settings. At that point, your default settings go into effect for that tenant only. You can allow the default settings to remain in effect. Or, you can modify the inbound and outbound settings for the organization.
4141
- **Obtain any required object IDs or app IDs.** If you want to apply access settings to specific users, groups, or applications in the partner organization, you'll need to contact the organization for information before configuring your settings. Obtain their user object IDs, group object IDs, or application IDs (*client app IDs* or *resource app IDs*) so you can target your settings correctly.
4242

43+
> [!NOTE]
44+
> Users from another Microsoft cloud must be invited using their user principal name (UPN). [Email as sign-in](/azure/active-directory/authentication/howto-authentication-use-email-signin#b2b-guest-user-sign-in-with-an-email-address) is not currently supported when collaborating with users from another Microsoft cloud.
45+
4346
## Enable the cloud in your Microsoft cloud settings
4447

4548
In your Microsoft cloud settings, enable the Microsoft Azure cloud you want to collaborate with.
@@ -96,6 +99,9 @@ The following scenarios are supported when collaborating with an organization fr
9699
- Use B2B collaboration to [share Power BI content to a user in the partner tenant](/power-bi/enterprise/service-admin-azure-ad-b2b#cross-cloud-b2b).
97100
- Apply Conditional Access policies to the B2B collaboration user and opt to trust multi-factor authentication or device claims (compliant claims and hybrid Azure AD joined claims) from the user’s home tenant.
98101

102+
> [!NOTE]
103+
> Enabling the [SharePoint and OneDrive integration with Azure AD B2B](/sharepoint/sharepoint-azureb2b-integration) will provide the best experience for inviting users from another Microsoft cloud within SharePoint and OneDrive.
104+
99105
## Next steps
100106

101107
See [Configure external collaboration settings](external-collaboration-settings-configure.md) for B2B collaboration with non-Azure AD identities, social identities, and non-IT managed external accounts.
126 KB
Loading
27.7 KB
Loading
-25 Bytes
Loading
-40 Bytes
Loading
36.1 KB
Loading
3.81 KB
Loading
7.65 KB
Loading
114 KB
Loading
124 KB
Loading

0 commit comments

Comments
 (0)