Skip to content

Commit 372d413

Browse files
committed
updating
1 parent 72b1004 commit 372d413

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/active-directory/hybrid/how-to-connect-pta-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ No. Pass-through Authentication is only available in the worldwide instance of A
3939
Yes. All Conditional Access capabilities, including Azure Multi-Factor Authentication, work with Pass-through Authentication.
4040

4141
## Does Pass-through Authentication support "Alternate ID" as the username, instead of "userPrincipalName"?
42-
To a limited extent, Pass-through Authentication supports Alternate ID as the username when configured in Azure AD Connect. As a pre-requisite, Azure AD Connect needs to synchronize the on-premises Active Directory `UserPrincipalName` attribute to Azure AD. This makes the `UserPrincipalName` on the on-premises AD and Azure AD become identical. If you would like to use another attribute to synchronize from on-premises AD as the UPN to Azure AD, you will have to use either Password Hash sync or AD FS. For more information, see [Custom installation of Azure AD Connect](how-to-connect-install-custom.md). Not all Office 365 applications support `Alternate ID`. Refer to the specific application's documentation support statement.
42+
Sign in using a non-UPN value, such as an alternate email, is currently being tested in private preview for both pass-through authentication (PTA) and password hash sync (PHS).
4343

4444
## Does password hash synchronization act as a fallback to Pass-through Authentication?
4545

0 commit comments

Comments
 (0)