Skip to content

Commit 4b71cc1

Browse files
authored
Update to reflect updated functionality
Doc update to illustrate UPN updated to federated accounts is now allowed. Also, removing the broken link to a support doc which is no longer available.
1 parent 29222a9 commit 4b71cc1

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/active-directory/hybrid/how-to-connect-syncservice-features.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,12 +84,14 @@ Set-MsolDirSyncFeature -Feature EnableSoftMatchOnUpn -Enable $true
8484

8585
## Synchronize userPrincipalName updates
8686

87-
Historically, updates to the UserPrincipalName attribute using the sync service from on-premises has been blocked, unless both of these conditions are true:
87+
Historically, updates to the UserPrincipalName attribute using the sync service from on-premises has been blocked, unless both of these conditions were true:
8888

8989
* The user is managed (non-federated).
9090
* The user has not been assigned a license.
9191

92-
For more details, see [User names in Office 365, Azure, or Intune don't match the on-premises UPN or alternate login ID](https://support.microsoft.com/kb/2523192).
92+
> [!NOTE]
93+
> From March 2019, synchronizing UPN changes for federated user accounts is allowed.
94+
>
9395
9496
Enabling this feature allows the sync engine to update the userPrincipalName when it is changed on-premises and you use password hash sync or pass-through authentication.
9597

0 commit comments

Comments
 (0)