Cross-tenant access settings
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 2dbf17e · +5 −5 lines · also on GitHub
11
---
22
title: Cross-tenant access overview
3
−description: Get an overview of cross-tenant access in Microsoft Entra External ID. Learn how to manage your B2B collaboration with other Microsoft Entra organizations through this overview of cross-tenant access settings.
3
+description: Learn how to manage cross-tenant access in Microsoft Entra External ID. Configure B2B collaboration and direct connect settings to control access and trust for external organizations.
44
55
ms.service: entra-external-id
66
ms.topic: overview
7
−ms.date: 08/20/2024
7
+ms.date: 03/28/2025
88
99
ms.author: cmulligan
1010
author: csmulligan
⋯ 13 unchanged lines
2424
This article covers cross-tenant access settings for managing B2B collaboration and B2B direct connect with external Microsoft Entra organizations, including across Microsoft clouds. Other settings are available for B2B collaboration with non-Microsoft Entra identities (for example, social identities or non-IT managed external accounts). These [external collaboration settings](external-collaboration-settings-configure.md) include options for restricting guest user access, specifying who can invite guests, and allowing or blocking domains.
2525
2626
There are no limits to the number of organizations you can add in cross-tenant access settings.
27
−␣
27
+
2828
## Manage external access with inbound and outbound settings
2929
3030
The external identities cross-tenant access settings manage how you collaborate with other Microsoft Entra organizations. These settings determine both the level of inbound access users in external Microsoft Entra organizations have to your resources, and the level of outbound access your users have to external organizations.
3131
3232
The following diagram shows the cross-tenant access inbound and outbound settings. The **Resource Microsoft Entra tenant** is the tenant containing the resources to be shared. For B2B collaboration, the resource tenant is the inviting tenant (for example, your corporate tenant, where you want to invite the external users). The **User's home Microsoft Entra tenant** is the tenant where the external users are managed.
3333
34
−:::image type="content" source="media/cross-tenant-access-overview/cross-tenant-access-settings-overview.png" alt-text="Overview diagram of cross-tenant access settings.":::
34
+:::image type="content" source="media/cross-tenant-access-overview/cross-tenant-access-settings-overview.png" alt-text="Screenshot of a diagram showing cross-tenant access settings for inbound and outbound collaboration.":::
3535
3636
By default, B2B collaboration with other Microsoft Entra organizations is enabled, and B2B direct connect is blocked. But the following comprehensive admin settings let you manage both of these features.
3737
⋯ 60 unchanged lines
9898
9999
### Direct federation for Microsoft Entra ID verified domains
100100
101
−SAML/WS-Fed identity provider federation (Direct federation) is now supported for Microsoft Entra ID verified domains. This feature allows you to set up a Direct federation with an external identity provider for a domain that is verified in Microsoft Entra.
101
+SAML/WS-Fed identity provider federation (Direct federation) is now supported for Microsoft Entra ID verified domains. This feature allows you to set up a Direct federation with an external identity provider for a domain that is verified in another Microsoft Entra tenant
102102
103103
> [!NOTE]
104104
> Ensure that the domain is not verified in the same tenant in which you are trying to set up the Direct federation configuration.
⋯ 106 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 07:21 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.