Forum Discussion
Considerations regarding Azure AD Connect and Hybdrid identitys
An alternate UPN suffix can be added to Windows AD. All users replicated to Azure AD will need the UPN Suffix changed to the alternate suffix before replicating the accounts with Azure AD. Use the IdFIx tool to verify consistency before replicating. As an alternative, you could add your Windows AD domain to Azure AD and continue using that domain.
Also, you will need and account with Global Admin rights to the Azure AD tenant to setup AD Connect.
An alternate UPN suffix can be added to Windows AD. All users replicated to Azure AD will need the UPN Suffix changed to the alternate suffix before replicating the accounts with Azure AD. Use the IdFIx tool to verify consistency before replicating. As an alternative, you could add your Windows AD domain to Azure AD and continue using that domain.
Also, you will need and account with Global Admin rights to the Azure AD tenant to setup AD Connect.
Thanks for reply TravisRoberts
Do i need to swap the old UPN Suffix to the new one before doing the synchronization?
I'll check out IDFIX aswell.
Am i able to use Single sign on/password sync even though its different identities?
SamirAbdou1999 Hello,
You do need to add the alternate UPN suffix to Windows AD and then update all users that will sync to the new UPN.
Single-sign on will work. This is a common scenario with organizations that have non-routable Windows domains (domain.local). Although both your domains are routable, the same principles apply.