How to Match Azure AD Accounts with Different Domains in Hybrid Deployments
Question details
The user needs to match on-premises Active Directory users with Azure AD accounts across different domains (Teams, Lync, Exchange, sign-in) during a hybrid deployment, ideally without changing existing primary SMTP addresses.

- Product
- Microsoft Azure AD
- Device & OS
- not provided
- Scenario
- Synchronizing and linking user accounts in a Microsoft 365 hybrid deployment using Azure AD Connect with multiple domain suffixes.
- Observed behavior
- Organizations face mismatched proxy addresses and need to ensure smooth soft-matching via UPN or SMTP while temporarily preserving separate sign-in domains.
Ensure that all custom domains are successfully verified in your Microsoft 365 tenant and that you have administrator access to both the on-premises Active Directory environment and the Azure AD Connect server.
Configure Azure AD Connect Soft Matching
Use soft matching to securely link on-premises AD accounts to existing Azure AD accounts using UPN or SMTP addresses without modifying the immutable ID.
Azure AD Connect handles identity synchronization by linking on-premises objects with cloud objects. By default, it uses a soft-matching process based on the User Principal Name (UPN) or primary SMTP address to prevent duplicate account creation.
Log in to the Microsoft 365 admin center. Navigate to Settings > Domains and verify that all domains used for Teams, Lync, Exchange, and user sign-ins are listed as 'Healthy'.
Open Active Directory Users and Computers (ADUC) on-premises. Ensure the User Principal Name (UPN), SMTP, and SIP proxy addresses are accurately configured in the user's Attribute Editor.
In the proxyAddresses attribute, format the desired primary email as 'SMTP:user@domain.com' (uppercase SMTP) and secondary addresses as 'smtp:user@otherdomain.com'. Azure AD Connect will read these values to preserve existing routing.
Open PowerShell on your Azure AD Connect server and run 'Start-ADSyncSyncCycle -PolicyType Delta'. Azure AD will automatically soft-match the users based on the matching UPN or primary SMTP address.

Temporarily Maintain Separate Sign-in Addresses
Configure temporary proxy addresses for phased hybrid deployments involving different domains for Teams and Lync.
Document Your IT Network Architecture with WPS Office
While WPS Office cannot directly manage Azure AD Connect or Microsoft 365 tenant synchronizations, it is highly recommended as a lightweight, free alternative to Microsoft Office for creating, tracking, and securely sharing your IT deployment guides and network infrastructure documentation.

Frequently Asked Questions
What is soft matching in Azure AD Connect?
Soft matching is an automated process where Azure AD Connect links an on-premises Active Directory account to an existing Azure AD account by evaluating and matching their User Principal Name (UPN) or primary SMTP address during directory synchronization.
When should I perform a hard match by modifying the immutable ID?
You should generally avoid changing the immutable ID. A hard match is only recommended when an automated soft match fails or when migrating users between different on-premises forests, which requires manual binding of the on-premises object to the cloud identity.
Can I use entirely different domains for Teams and Exchange in a hybrid setup?
Yes, it is possible temporarily. You can configure the on-premises UPN for the Teams domain while keeping the SIP or primary SMTP directed to your existing Exchange domain. However, Microsoft strongly recommends unifying UPN, SMTP, and SIP addresses under a single domain once the hybrid migration concludes.
How do proxy addresses affect synchronization from on-premises AD?
Proxy addresses, including primary (uppercase SMTP) and secondary (lowercase smtp) email aliases, dictate how communication is routed. Azure AD Connect copies these attributes directly from the on-premises environment to Azure AD, meaning all proxy modifications must be managed on-premises in a hybrid scenario.




