manager: celestedg
ms.custom: it-pro
ms.collection: M365-identity-device-management
#customer intent: As an IT admin, I want to configure tenant restrictions v2 so that I can control access to external apps and enhance security for users signing in from my organization's networks or devices.
---
# Set up tenant restrictions v2
> [!NOTE]
> Certain features described in this article are preview features. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
To enhance security, you can limit what your users can access when they use an external account to sign in from your networks or devices. The **Tenant restrictions** settings, included with [cross-tenant access settings](cross-tenant-access-overview.md), let you create a policy to control access to external apps.
For example, suppose a user in your organization created a separate account in an unknown tenant, or an external organization gave your user an account that lets them sign in to their organization. You can use tenant restrictions to prevent the user from using some or all external apps while they're signed in with the external account on your network or devices.
| Step | Description |
|---------|---------|
|**1** | Contoso configures tenant restrictions in its cross-tenant access settings to block all external accounts and external apps. Contoso adds enforcement signaling with the tenant restrictions v2 header via either [universal tenant restrictions v2](#option-1-universal-tenant-restrictions-v2-as-part-of-microsoft-entra-global-secure-access) or a [corporate proxy](#option-2-set-up-tenant-restrictions-v2-on-your-corporate-proxy). Microsoft Entra ID enforces the tenant restrictions v2 policy when the header is present on the request. |
|**2** | A user who's using a Contoso-managed device tries to sign in to an external app by using an account from an unknown tenant. The tenant restrictions v2 HTTP header, with Contoso's tenant ID and the tenant restrictions policy ID, is added to the authentication request. |
|**3** | *Authentication plane protection:* Microsoft Entra ID enforces Contoso's tenant restrictions v2 policy and blocks external accounts from accessing external tenants during the authentication, in accordance with the Contoso tenant restrictions v2 policy. |
|**4** | *Data plane protection (preview):* Microsoft Entra ID blocks any anonymous access to Microsoft forms, SharePoint files, or Microsoft Teams meetings. Microsoft Entra ID also blocks user access to the resource with an infiltrated token. |
manager: celestedg
ms.custom: it-pro
ms.collection: M365-identity-device-management
#customer intent: As an IT admin, I want to configure tenant restrictions v2 so that I can control access to external apps and enhance security for users who sign in from my organization's networks or devices.
---
# Set up tenant restrictions v2
> [!NOTE]
> Certain features described in this article are preview features. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
To enhance security, you can limit what your users can access when they use an external account to sign in from your networks or devices. The *tenant restrictions* settings, included with [cross-tenant access settings](cross-tenant-access-overview.md), let you create a policy to control access to external apps.
For example, suppose a user in your organization created a separate account in an unknown tenant, or an external organization gave your user an account that lets them sign in to their organization. You can use tenant restrictions to prevent the user from using some or all external apps while they're signed in with the external account on your network or devices.
| Step | Description |
|---------|---------|
|**1** | Contoso configures tenant restrictions in its cross-tenant access settings to block all external accounts and external apps. Contoso adds enforcement signaling with the tenant restrictions v2 header via either [universal tenant restrictions v2](#option-1-universal-tenant-restrictions-v2-as-part-of-microsoft-entra-global-secure-access) or a [corporate proxy](#option-2-set-up-tenant-restrictions-v2-on-your-corporate-proxy). Microsoft Entra ID enforces the tenant restrictions v2 policy when the header is present on the request. |
|**2** | The user of a Contoso-managed device tries to sign in to an external app by using an account from an unknown tenant. The tenant restrictions v2 HTTP header, with Contoso's tenant ID and the tenant restrictions policy ID, is added to the authentication request. |
|**3** | *Authentication plane protection:* Microsoft Entra ID enforces Contoso's tenant restrictions v2 policy and blocks external accounts from accessing external tenants during the authentication. |
|**4** | *Data plane protection (preview):* Microsoft Entra ID blocks any anonymous access to Microsoft Forms, SharePoint files, or Microsoft Teams meetings. Microsoft Entra ID also blocks user access to the resource with an infiltrated token. |