| Previous | Next |
| ERROR_DS_FLAT_NAME_EXISTS_IN_FOREST | ERROR_DS_OID_MAPPED_GROUP_CANT_HAVE_MEMBERS |
ERROR_INVALID_USER_PRINCIPAL_NAME
The User Principal Name (UPN) is invalid.
ERROR_INVALID_USER_PRINCIPAL_NAME is Windows status 8636 (0x000021BC) associated with validation of a User Principal Name for an account.
Likely impact: Invalid UPNs block sign-in and synchronization and should not be auto-corrected without an authoritative naming rule.
Typical causes
- the value lacks a valid user or suffix part.
- unsupported characters or whitespace are present.
- the suffix is not configured or is mistyped.
- provisioning supplied a display name instead of a UPN.
Troubleshooting steps
- Verify that the UPN has valid syntax, suffix, normalization, and directory uniqueness for the intended forest.
- Collect submitted UPN bytes and normalization and configured UPN suffixes.
Useful evidence
- Collect provisioning source field.
- Collect LDAP extended diagnostic.
Recovery and retry
Normalize and validate the intended sign-in name against configured suffixes before updating the account.
Related errors
ERROR_INVALID_ACCOUNT_NAME is a broader account-name failure; this code identifies UPN validation
Example
A CSV import places an email display string with spaces in userPrincipalName. Field-level validation rejects it before any directory modification.
References
Looking for a different code? Search another status or error code.