Forum Discussion
Microsoft Entra ID Provisioning: SelectUniqueValue and the "Apply this mapping" limitation
I should also point out that I used usernames and UPNs merely as examples because, in our organization, we use SelectUniqueValue() to detect and resolve naming conflicts when multiple employees share the same first and last names.
When an employee undergoes a legal name change, our preference is to update their username and UPN accordingly. However, because SelectUniqueValue() requires the attribute mapping to be configured as "Only during object creation," we cannot use that same uniqueness-checking logic with an "Always" mapping configuration to accommodate subsequent changes.
More importantly, this limitation is not specific to usernames, UPNs, or our organization's naming policies. It applies to any supported attribute mapping that uses SelectUniqueValue(), and there are numerous scenarios in which an organization may need to validate uniqueness when updating an existing object.
The broader point is not whether an organization should or should not change usernames or UPNs after account creation. That is a business decision specific to each organization.
The issue is that Microsoft provides a built-in function for evaluating candidate values and resolving conflicts, but restricts that functionality to object creation. As a result, organizations cannot use the same native uniqueness-validation logic when updating existing objects, even when the update is driven by legitimate changes in authoritative source data.
Removing this restriction would allow organizations to implement more comprehensive provisioning logic without having to develop and maintain external processes to perform uniqueness checks during updates.