Skip to content

Commit a75e02e

Browse files
roygararoygara
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into fSD
2 parents 1a4b856 + 9c67426 commit a75e02e

File tree

104 files changed

+1012
-606
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

104 files changed

+1012
-606
lines changed

‎articles/active-directory/authentication/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -138,6 +138,8 @@
138138
href: howto-password-ban-bad-on-premises-agent-versions.md
139139
- name: Use SMS-based authentication (preview)
140140
href: howto-authentication-sms-signin.md
141+
- name: Use email address sign-in (preview)
142+
href: howto-authentication-use-email-signin.md
141143
- name: Azure AD smart lockout
142144
href: howto-password-smart-lockout.md
143145
- name: Certificate-based authentication

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

Lines changed: 186 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,186 @@
1+
---
2+
title: Sign in with email as an alternate login ID for Azure Active Directory
3+
description: Learn how to configure and enable users to sign in to Azure Active Directory using their email address as an alternate login ID (preview)
4+
5+
services: active-directory
6+
ms.service: active-directory
7+
ms.subservice: authentication
8+
ms.topic: how-to
9+
ms.date: 05/22/2020
10+
11+
ms.author: iainfou
12+
author: iainfoulds
13+
manager: daveba
14+
ms.reviewer: scottsta
15+
16+
---
17+
# Sign-in to Azure using email as an alternate login ID (preview)
18+
19+
Many organizations want to let users sign in to Azure using the same credentials as their on-premises directory environment. With this approach, known as hybrid authentication, users only need to remember one set of credentials.
20+
21+
Some organizations haven't moved to hybrid authentication for the following reasons:
22+
23+
* By default, the Azure Active Directory (Azure AD) user principal name (UPN) is set to the same UPN as the on-premises directory.
24+
* Changing the Azure AD UPN creates a mis-match between on-prem and Azure environments that could cause problems with certain applications and services.
25+
* Due to business or compliance reasons, the organization doesn't want to use the on-premises UPN to sign in to Azure.
26+
27+
To help with the move to hybrid authentication, you can now configure Azure AD to let users sign in to Azure with an email in your verified domain as an alternate login ID. For example, if *Contoso* rebranded to *Fabrikam*, rather than continuing to sign in with the legacy `[email protected]` UPN, email as an alternate login ID can now be used. To access an application or services, users would sign in to Azure using their assigned email, such as `[email protected]`.
28+
29+
| |
30+
| --- |
31+
| Sign in to Azure AD with email as an alternate login ID is a public preview feature of Azure Active Directory. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).|
32+
| |
33+
34+
## Overview of Azure AD sign-in approaches
35+
36+
User Principal Names (UPNs) are unique identifiers for a user account in both your on-premises directory, and in Azure AD. Each user account in a directory is represented by a UPN, such as `[email protected]`. By default, when you synchronize an on-premises Active Directory Domain Services (AD DS) environment with Azure AD, the Azure AD UPN is to set to match the on-premises UPN.
37+
38+
In many organizations, it's fine to set the on-premises UPN and Azure AD UPN to match. When users sign in to Azure applications and services, they use their Azure AD UPN. However, some organizations can't use matching UPNs for sign-in due to business policies or user experience issues.
39+
40+
Organizations that can't use matching UPNs in Azure AD have a few options:
41+
42+
* One approach is to set the Azure AD UPN to something different based on the business needs, such as `[email protected]`.
43+
* However, not all applications and services are compatible with using a different value for the on-premises UPN and the Azure AD UPN.
44+
* A better approach is to ensure the Azure AD and on-premises UPNs are set to the same value, and configure Azure AD to let users sign into Azure with their email as an alternate login ID.
45+
46+
With email as an alternate login ID, users can still sign in to Azure by entering their UPN, but can also sign in using their email. To support this, you define an email address in the user's *ProxyAddresses* attribute in the on-premises directory. This *ProxyAddress* attribute supports one or more email addresses.
47+
48+
## Synchronize sign-in email addresses to Azure AD
49+
50+
Traditional Active Directory Domain Services (AD DS) or Active Directory Federation Services (AD FS) authentication happens directly on your network and is handled by your AD DS infrastructure. With hybrid authentication, users can instead sign in directly to Azure AD.
51+
52+
To support this hybrid authentication approach, you synchronize your on-premises AD DS environment to Azure AD using [Azure AD Connect][azure-ad-connect] and configure it to use Password Hash Sync (PHS) or Pass-Through Authentication (PTA).
53+
54+
In both configuration options, the user submits their username and password to Azure AD, which validates the credentials and issues a ticket. When users sign in to Azure AD, it removes the need for your organization to host and manage an AD FS infrastructure.
55+
56+
![Diagram of Azure AD hybrid identity with password hash synchronization](media/howto-authentication-use-email-signin/hybrid-password-hash-sync.png)
57+
58+
![Diagram of Azure AD hybrid identity with pass-through authentication](media/howto-authentication-use-email-signin/hybrid-pass-through-authentication.png)
59+
60+
One of the user attributes that's automatically synchronized by Azure AD Connect is *ProxyAddresses*. If users have an email address defined in the on-prem AD DS environment as part of the *ProxyAddresses* attribute, it's automatically synchronized to Azure AD. This email address can then be used directly in the Azure AD sign-in process as an alternate login ID.
61+
62+
> [!IMPORTANT]
63+
> Only emails in verified domains for the tenant are synchronized to Azure AD. Each Azure AD tenant has one or more verified domains, for which you have proven ownership, and are uniquely bound to you tenant.
64+
>
65+
> For more information, see [Add and verify a custom domain name in Azure AD][verify-domain].
66+
67+
For more information, see [Choose the right authentication method for your Azure AD hybrid identity solution][hybrid-auth-methods].
68+
69+
## Enable user sign-in with an email address
70+
71+
Once users with the *ProxyAddresses* attribute applied are synchronized to Azure AD using Azure AD Connect, you need to enable the feature for users to sign in with email as an alternate login ID for your tenant. This feature tells the Azure AD login servers to not only check the sign-in name against UPN values, but also against *ProxyAddresses* values for the email address.
72+
73+
During preview, you can currently only enable the sign-in with email as an alternate login ID feature using PowerShell. You need *tenant administrator* permissions to complete the following steps:
74+
75+
1. Open an PowerShell session as an administrator, then install the *AzureADPreview* module using the [Install-Module][Install-Module] cmdlet:
76+
77+
```powershell
78+
Install-Module AzureADPreview
79+
```
80+
81+
If prompted, select **Y** to install NuGet or to install from an untrusted repository.
82+
83+
1. Sign in to your Azure AD tenant as a *tenant administrator* using the [Connect-AzureAD][Connect-AzureAD] cmdlet:
84+
85+
```powershell
86+
Connect-AzureAD
87+
```
88+
89+
The command returns information about your account, environment, and tenant ID.
90+
91+
1. Check if the *HomeRealmDiscoveryPolicy* policy already exists in your tenant using the [Get-AzureADPolicy][Get-AzureADPolicy] cmdlet as follows:
92+
93+
```powershell
94+
Get-AzureADPolicy | where-object {$_.Type -eq "HomeRealmDiscoveryPolicy"} | fl *
95+
```
96+
97+
1. If there's no policy currently configured, the command returns nothing. If a policy is returned, skip this step and move on to the next step to update an existing policy.
98+
99+
To add the *HomeRealmDiscoveryPolicy* policy to the tenant, use the [New-AzureADPolicy][New-AzureADPolicy] cmdlet and set the *AlternateIdLogin* attribute to *"Enabled": true* as shown in the following example:
100+
101+
```powershell
102+
New-AzureADPolicy -Definition @('{"HomeRealmDiscoveryPolicy" :{"AlternateIdLogin":{"Enabled": true}}}') `
103+
-DisplayName "BasicAutoAccelerationPolicy" `
104+
-IsOrganizationDefault $true `
105+
-Type "HomeRealmDiscoveryPolicy"
106+
```
107+
108+
When the policy has been successfully created, the command returns the policy ID, as shown in the following example output:
109+
110+
```powershell
111+
Id                                   DisplayName                 Type                     IsOrganizationDefault
112+
--                                   -----------                 ----                     ---------------------
113+
5de3afbe-4b7a-4b33-86b0-7bbe308db7f7 BasicAutoAccelerationPolicy HomeRealmDiscoveryPolicy True
114+
```
115+
116+
1. If there's already a configured policy, check if the *AlternateIdLogin* attribute is enabled, as shown in the following example policy output:
117+
118+
```powershell
119+
Id : 5de3afbe-4b7a-4b33-86b0-7bbe308db7f7
120+
OdataType :
121+
AlternativeIdentifier :
122+
Definition : {{"HomeRealmDiscoveryPolicy" :{"AlternateIdLogin":{"Enabled": true}}}}
123+
DisplayName : BasicAutoAccelerationPolicy
124+
IsOrganizationDefault : True
125+
KeyCredentials : {}
126+
Type : HomeRealmDiscoveryPolicy
127+
```
128+
129+
If the policy exists but the *AlternateIdLogin* attribute that isn't present or enabled, or if other attributes exist on the policy you wish to preserve, update the existing policy using the [Set-AzureADPolicy][Set-AzureADPolicy] cmdlet.
130+
131+
> [!IMPORTANT]
132+
> When you update the policy, make sure you include any old settings and the new *AlternateIdLogin* attribute.
133+
134+
The following example adds the *AlternateIdLogin* attribute and preserves the *AllowCloudPasswordValidation* attribute that may have already been set:
135+
136+
```powershell
137+
Set-AzureADPolicy -id b581c39c-8fe3-4bb5-b53d-ea3de05abb4b `
138+
-Definition @('{"HomeRealmDiscoveryPolicy" :{"AllowCloudPasswordValidation":true,"AlternateIdLogin":{"Enabled": true}}}') `
139+
-DisplayName "BasicAutoAccelerationPolicy" `
140+
-IsOrganizationDefault $true `
141+
-Type "HomeRealmDiscoveryPolicy"
142+
```
143+
144+
Confirm that the updated policy shows your changes and that the *AlternateIdLogin* attribute is now enabled:
145+
146+
```powershell
147+
Get-AzureADPolicy | where-object {$_.Type -eq "HomeRealmDiscoveryPolicy"} | fl *
148+
```
149+
150+
## Test user sign-in with email
151+
152+
To test that users can sign in with email, browse to [https://myprofile.microsoft.com][my-profile] and sign in with a user account based on their email address, such as `[email protected]`, not their UPN, such as `[email protected]`. The sign-in experience should look and feel the same as with a UPN-based sign-in event.
153+
154+
## Troubleshoot
155+
156+
If users have trouble with sign-in events using their email address, review the following troubleshooting steps:
157+
158+
1. Make sure the user account has their email address set for the *ProxyAddresses* attribute in the on-prem AD DS environment.
159+
1. Verify that Azure AD Connect is configured and successfully synchronizes user accounts from the on-prem AD DS environment into Azure AD.
160+
1. Confirm that the Azure AD *HomeRealmDiscoveryPolicy* policy has the *AlternateIdLogin* attribute set to *"Enabled": true*:
161+
162+
```powershell
163+
Get-AzureADPolicy | where-object {$_.Type -eq "HomeRealmDiscoveryPolicy"} | fl *
164+
```
165+
166+
## Next steps
167+
168+
To learn more about hybrid identity, such as Azure AD App Proxy or Azure AD Domain Services, see [Azure AD hybrid identity for access and management of on-prem workloads][hybrid-overview].
169+
170+
For more information on hybrid identity operations, see [how password hash sync][phs-overview] or [pass-through authentication][pta-overview] synchronization work.
171+
172+
<!-- INTERNAL LINKS -->
173+
[verify-domain]: ../fundamentals/add-custom-domain.md
174+
[hybrid-auth-methods]: ../hybrid/choose-ad-authn.md
175+
[azure-ad-connect]: ../hybrid/whatis-azure-ad-connect.md
176+
[hybrid-overview]: ../hybrid/cloud-governed-management-for-on-premises.md
177+
[phs-overview]: ../hybrid/how-to-connect-password-hash-synchronization.md
178+
[pta-overview]: ../hybrid/how-to-connect-pta-how-it-works.md
179+
180+
<!-- EXTERNAL LINKS -->
181+
[Install-Module]: /powershell/module/powershellget/install-module
182+
[Connect-AzureAD]: /powershell/module/azuread/connect-azuread
183+
[Get-AzureADPolicy]: /powershell/module/azuread/get-azureadpolicy
184+
[New-AzureADPolicy]: /powershell/module/azuread/new-azureadpolicy
185+
[Set-AzureADPolicy]: /powershell/module/azuread/set-azureadpolicy
186+
[my-profile]: https://myprofile.microsoft.com

‎articles/active-directory/authentication/media/howto-authentication-use-email-signin/hybrid-pass-through-authentication.png

89.4 KB
Loading

‎articles/active-directory/authentication/media/howto-authentication-use-email-signin/hybrid-password-hash-sync.png

79.7 KB
Loading

‎articles/active-directory/b2b/redemption-experience.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,9 +41,9 @@ As an alternative to the invitation email, you can give a guest a direct link to
4141

4242
> [!IMPORTANT]
4343
> The direct link must be tenant-specific. In other words, it must include a tenant ID or verified domain so the guest can be authenticated in your tenant, where the shared app is located. A common URL like https://myapps.microsoft.com won’t work for a guest because it will redirect to their home tenant for authentication. Here are some examples of direct links with tenant context:
44-
> - Apps access panel: https://myapps.microsoft.com/?tenantid=&lt;tenant id&gt;
45-
> - Apps access panel for a verified domain: https://myapps.microsoft.com/&lt;verified domain&gt;
46-
> - Azure portal: https://portal.azure.com/&lt;tenant id&gt;
44+
> - Apps access panel: `https://myapps.microsoft.com/?tenantid=<tenant id>`
45+
> - Apps access panel for a verified domain: `https://myapps.microsoft.com/<;verified domain>`
46+
> - Azure portal: `https://portal.azure.com/<tenant id>`
4747
> - Individual app: see how to use a [direct sign-on link](../manage-apps/end-user-experiences.md#direct-sign-on-links)
4848
4949
There are some cases where the invitation email is recommended over a direct link. If these special cases are important to your organization, we recommend that you invite users by using methods that still send the invitation email:

‎articles/automation/automation-alert-metric.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,4 +71,4 @@ Once the metric is no longer outside of the threshold defined, the alert is deac
7171

7272
## Next steps
7373

74-
* [Use an alert to trigger an Azure Automation runbook](automation-create-alert-triggered-runbook.md)
74+
* For more information, see [Use an alert to trigger an Azure Automation runbook](automation-create-alert-triggered-runbook.md).

‎articles/automation/automation-child-runbooks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -111,5 +111,5 @@ Start-AzAutomationRunbook `
111111

112112
## Next steps
113113

114-
* [Start a runbook in Azure Automation](start-runbooks.md)
115-
* [Runbook output and messages in Azure Automation](automation-runbook-output-and-messages.md)
114+
* To run run your runbook, see [Start a runbook in Azure Automation](start-runbooks.md).
115+
* For monitoring of runbook operation, see [Runbook output and messages in Azure Automation](automation-runbook-output-and-messages.md).

‎articles/automation/automation-config-aws-account.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,4 +33,4 @@ After you have created and copied your AWS security keys, you must create a Cred
3333

3434
## Next steps
3535

36-
* [Automate deployment of a VM in Amazon Web Services](automation-scenario-aws-deployment.md)
36+
* To learn how to create runbooks to automate tasks in AWS, see [Deploy an Amazon Web Services VM with a runbook](automation-scenario-aws-deployment.md).

‎articles/automation/automation-configure-windows-update.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,4 +56,4 @@ To restrict machines to the internal update service, set [Do not connect to any
5656

5757
## Next steps
5858

59-
[Manage updates and patches for your Azure VMs](automation-tutorial-update-management.md)
59+
Schedule an update deployment by following instructions in [Manage updates and patches for your Azure VMs](automation-tutorial-update-management.md).

‎articles/automation/automation-connections.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -187,6 +187,6 @@ azure_credential = get_automation_runas_credential(runas_connection)
187187

188188
## Next steps
189189

190-
* [Manage modules in Azure Automation](shared-resources/modules.md)
191-
* [Runbook execution in Azure Automation](automation-runbook-execution.md)
192-
* [State Configuration overview](automation-dsc-overview.md)
190+
* To learn more about the cmdlets used to access connections, see [Manage modules in Azure Automation](shared-resources/modules.md).
191+
* For general information about runbooks, see [Runbook execution in Azure Automation](automation-runbook-execution.md).
192+
* For details of DSC configurations, see [State Configuration overview](automation-dsc-overview.md).

0 commit comments

Comments
 (0)