Skip to content

Commit ec79789

Browse files
committed
Update howto-authentication-use-email-signin.md
1 parent 2be6d59 commit ec79789

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/active-directory/authentication/howto-authentication-use-email-signin.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 07/07/2021
9+
ms.date: 06/17/2022
1010

1111
ms.author: justinha
1212
author: calui
@@ -43,7 +43,7 @@ Here's what you need to know about email as an alternate login ID:
4343
* The feature supports managed authentication with Password Hash Sync (PHS) or Pass-Through Authentication (PTA).
4444
* There are two options for configuring the feature:
4545
* [Home Realm Discovery (HRD) policy](#enable-user-sign-in-with-an-email-address) - Use this option to enable the feature for the entire tenant. Global administrator privileges required.
46-
* [Staged rollout policy](#enable-staged-rollout-to-test-user-sign-in-with-an-email-address) - Use this option to test the feature with specific Azure AD groups. Global administrator privileges required.
46+
* [Staged rollout policy](#enable-staged-rollout-to-test-user-sign-in-with-an-email-address) - Use this option to test the feature with specific Azure AD groups. Global administrator privileges required. When you first add a security group for staged rollout, you're limited to 200 users to avoid a UX time-out. After you've added the group, you can add more users directly to it, as required.
4747

4848
## Preview limitations
4949

0 commit comments

Comments
 (0)