Skip to content

Commit 3f83c18

Browse files
authored
Update tenant-restrictions-v2.md
1 parent 949422a commit 3f83c18

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/active-directory/external-identities/tenant-restrictions-v2.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -315,7 +315,7 @@ Suppose you use tenant restrictions to block access by default, but you want to
315315
316316
## Step 3: Enable tenant restrictions on Windows managed devices
317317

318-
After you create a tenant restrictions V2 policy, you can enforce the policy on each Windows 10, Windows 11, and Windows Server 2022 device by adding your tenant ID and the policy ID to the device's **Tenant Restrictions** configuration. When tenant restrictions are enabled on a Windows device, corporate proxies aren't required for policy enforcement. Devices don't need to be Azure AD managed to enforce tenant restrictions V2; domain-joined devices that are managed with Group Policy are also supported.
318+
After you create a tenant restrictions V2 policy, you can enforce the policy on each Windows 10 and Windows 11 device by adding your tenant ID and the policy ID to the device's **Tenant Restrictions** configuration. When tenant restrictions are enabled on a Windows device, corporate proxies aren't required for policy enforcement. Devices don't need to be Azure AD managed to enforce tenant restrictions V2; domain-joined devices that are managed with Group Policy are also supported.
319319

320320
### Administrative Templates (.admx) for Windows 10 November 2021 Update (21H2) and Group policy settings
321321

@@ -330,7 +330,7 @@ To test the tenant restrictions V2 policy on a device, follow these steps.
330330

331331
> [!NOTE]
332332
>
333-
> - The device must be running Windows 10, Windows 11, or Windows Server 2022 with the latest updates.
333+
> - The device must be running Windows 10 or Windows 11 with the latest updates.
334334
335335
1. On the Windows computer, press the Windows key, type **gpedit**, and then select **Edit group policy (Control panel)**.
336336

@@ -349,7 +349,7 @@ To test the tenant restrictions V2 policy on a device, follow these steps.
349349

350350
## Step 4: Set up tenant restrictions V2 on your corporate proxy
351351

352-
Tenant restrictions V2 policies can't be directly enforced on non-Windows 10, Windows 11, or Windows Server 2022 devices, such as Mac computers, mobile devices, unsupported Windows applications, and Chrome browsers. To ensure sign-ins are restricted on all devices and apps in your corporate network, configure your corporate proxy to enforce tenant restrictions V2. Although configuring tenant restrictions on your corporate proxy don't provide data plane protection, it does provide authentication plane protection.
352+
Tenant restrictions V2 policies can't be directly enforced on non-Windows 10 or Windows 11 devices, such as Mac computers, mobile devices, unsupported Windows applications, and Chrome browsers. To ensure sign-ins are restricted on all devices and apps in your corporate network, configure your corporate proxy to enforce tenant restrictions V2. Although configuring tenant restrictions on your corporate proxy don't provide data plane protection, it does provide authentication plane protection.
353353

354354
> [!IMPORTANT]
355355
> If you've previously set up tenant restrictions, you'll need to stop sending `restrict-msa` to login.live.com. Otherwise, the new settings will conflict with your existing instructions to the MSA login service.

0 commit comments

Comments
 (0)