Exchange Connection Problems

Fix Missing Email Aliases After Azure AD Connect Sync

Huda QurayshiHuda Qurayshi Nov 20, 2026 868 views

Question details

Determine why some on-premises Active Directory users are missing SMTP aliases in Microsoft 365 after synchronization.

Fix Missing Email Aliases After Azure AD Connect Sync
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.
Before you start

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.

Solution 1Recommended

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.

1
Inspect synchronization errors

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.

2
Review the source attributes

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.

3
Check for address conflicts

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.

4
Review synchronization scope

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.

5
Correct and synchronize

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.

6
Verify the aliases

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.

Check Synchronization Errors and Correct Source Attributes
Allow for synchronization processing: A delta cycle processes ordinary attribute changes. Changes to synchronization rules or configuration may require additional steps or a full synchronization; review the applicable Microsoft guidance before running one.
Free Microsoft Office alternative

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.

Open and edit Microsoft Word, Excel, and PowerPoint formats, including DOCX, XLSX, and PPTX.Use a familiar interface to make moving existing Office files easier.Keep a spreadsheet of affected users and missing aliases for troubleshooting.Work with common Office files in a free, lightweight suite.
microsoft office alternative - wps office

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.