|
1 | 1 | ---
|
2 |
| -title: Alternate email user sign in for Azure Active Directory |
| 2 | +title: Alternate email user sign-in for Azure Active Directory |
3 | 3 | description: Learn how to configure and enable users to sign in to Azure Active Directory using alternate email address (preview)
|
4 | 4 |
|
5 | 5 | services: active-directory
|
6 | 6 | ms.service: active-directory
|
7 | 7 | ms.subservice: authentication
|
8 | 8 | ms.topic: how-to
|
9 |
| -ms.date: 05/04/2020 |
| 9 | +ms.date: 05/11/2020 |
10 | 10 |
|
11 | 11 | ms.author: iainfou
|
12 | 12 | author: iainfoulds
|
13 | 13 | manager: daveba
|
14 | 14 | ms.reviewer: scottsta
|
15 | 15 |
|
16 | 16 | ---
|
17 |
| - |
18 | 17 | # Configure user sign-in with an alternate email address in Azure Active Directory (preview)
|
19 | 18 |
|
20 | 19 | Many organizations want to use hybrid authentication to allow their users to sign in directly to Azure Active Directory (Azure AD). With hybrid authentication, users have the same sign-in credentials in an on-premises environment and in the cloud. However, hybrid authentication may currently be blocked in your environment because of the following reasons:
|
21 | 20 |
|
22 |
| -* The unique principal name (UPN) for a user must be identical in the on-premises directory and in Azure AD. |
| 21 | +* For best compatibility, you require the user principle name (UPN) for the user to be identical in the on-premises directory and in Azure AD. |
23 | 22 | * Azure AD requires users to sign in with their Azure AD UPN.
|
24 | 23 | * Your users can't sign in with their UPN because they don't know, can't remember, or just don't associate with their UPN.
|
25 | 24 | * Especially for large organizations with multiple subsidiaries or acquired companies, users may not be allowed to use an account with the parent company as part of their UPN.
|
26 | 25 |
|
27 |
| -If this situation describes your organization, you can now use the preview for Azure AD user sign-in with an alternate email address. With this approach, you enable your users to sign in with their well-known email address in the cloud, just like they do in your on-premises network. Users only need to know their email address, not their UPN. |
| 26 | +For these scenarios and more, you can now use the preview for Azure AD user sign-in with an alternate email address. With this approach, you enable your users to sign in with their well-known email address in the cloud, just like they do in your on-premises network. Users only need to know their email address, not their UPN. |
28 | 27 |
|
29 | 28 | | |
|
30 | 29 | | --- |
|
@@ -73,7 +72,7 @@ Once your users with the *ProxyAddresses* attribute set are synchronized to Azur
|
73 | 72 |
|
74 | 73 | During preview, you can currently only enable the alternate email user sign-in feature using PowerShell. You need *tenant administrator* permissions to complete the following steps:
|
75 | 74 |
|
76 |
| -1. Open an PowerShell session and install the *AzureADPreview* module using the [Install-Module][Install-Module] cmdlet: |
| 75 | +1. Open an PowerShell session as an administrator, then install the *AzureADPreview* module using the [Install-Module][Install-Module] cmdlet: |
77 | 76 |
|
78 | 77 | ```powershell
|
79 | 78 | Install-Module AzureADPreview
|
|
0 commit comments