Fix Missing Email Aliases After Azure AD Connect Sync
Question details
Determine why some on-premises Active Directory users are missing SMTP aliases in Microsoft 365 after synchronization.

- Product
- Microsoft Entra Connect Sync (Azure AD Connect) and Microsoft 365
- Device & OS
- not provided
- Scenario
- On-premises Active Directory users are synchronized to Microsoft 365, but only some users have all expected email aliases.
- Observed behavior
- Some synchronized users are missing SMTP aliases in Microsoft 365, while other users synchronize correctly.
Identify an affected user and the missing alias, and confirm that you have permission to inspect on-premises Active Directory, the synchronization server, and Microsoft 365 recipients. Note the user's current userPrincipalName and proxyAddresses values for comparison.
Check Synchronization Errors and Correct Source Attributes
Use this approach to find duplicate, malformed, or excluded attributes that prevent aliases from appearing in Microsoft 365.
On the Microsoft Entra Connect server, open Synchronization Service Manager and select Operations. Review recent synchronization and export runs for errors involving the affected user or address.
In Active Directory Users and Computers, select View > Advanced Features, open the affected user's Properties, and select Attribute Editor. Inspect proxyAddresses and userPrincipalName for duplicates, invalid formatting, or unsupported lengths. SMTP entries normally use uppercase SMTP: for the primary address and lowercase smtp: for aliases.
Search for the missing address among users, groups, and contacts in the on-premises directory and Microsoft 365. Correct duplicate values at their authoritative source, and check that the alias uses a domain verified in Microsoft 365.
On the synchronization server, open Synchronization Rules Editor and review rules that apply to the affected user. Confirm that the user and the relevant attributes are not excluded or transformed unexpectedly.
Correct the authoritative source attributes using the appropriate management tools. For Exchange-managed recipients, use the supported Exchange management tools to change email addresses. Then open PowerShell on the synchronization server and run Start-ADSyncSyncCycle -PolicyType Delta.
After synchronization completes, open the Exchange admin center and go to Recipients > Mailboxes. Select the affected mailbox and review its email addresses for the expected alias.

Work with Office Files in WPS Office
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files, but it does not repair Azure AD Connect or synchronize Exchange aliases.

Frequently Asked Questions
Where can I see Azure AD Connect synchronization errors?
On the synchronization server, open Synchronization Service Manager and select Operations. Inspect recent runs and their errors for the affected user.
How should SMTP aliases appear in proxyAddresses?
In the user's Attribute Editor, proxyAddresses entries normally use uppercase SMTP: for the primary address and lowercase smtp: for aliases. Check each address for valid formatting and duplicates.
Can a duplicate address prevent an alias from synchronizing?
Yes. A conflicting proxy address on another user, group, or contact can prevent the expected address from being assigned. Find the conflicting object and correct the value at its authoritative source.
How do I run another synchronization after correcting an alias?
On the Microsoft Entra Connect server, open PowerShell and run Start-ADSyncSyncCycle -PolicyType Delta. After the cycle completes, check the recipient's email addresses in the Exchange admin center.
Can WPS Office fix missing Microsoft 365 aliases?
No. Alias synchronization is managed through Active Directory, Microsoft Entra Connect, and Exchange. WPS Office can help you maintain a troubleshooting spreadsheet, but it does not change directory or recipient settings.




