merging on prem domain with cloud domain azure ad

%3CLINGO-SUB%20id%3D%22lingo-sub-1430246%22%20slang%3D%22en-US%22%3Emerging%20on%20prem%20domain%20with%20cloud%20domain%20azure%20ad%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1430246%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20created%20a%20cloud%20only%20domain%20for%20using%20Microsoft%20Teams%20(%20managed%20in%20azure%20ad)%20college.edu%20but%20have%20another%20domain%20college.ac%20which%20is%20our%20primary%20on-premise%20domain%20managed%20in%20AD.%20We%20did%20this%20because%20we%20were%20not%20ready%20to%20migrate%20our%20mailboxes%20to%20the%20cloud%20or%20use%20our%20AD%20to%20manage%20cloud%20users%20at%20that%20point.%20So%20each%20user%20has%20an%20edu%20and%20an%20ac%20upn%20one%20for%20the%20cloud%20and%20the%20other%20on-premise%3C%2FP%3E%3CP%3ENow%20we%20have%20decided%20to%20migrate%20our%20on%20premise%20accounts%20to%20the%20cloud%20using%20an%20express%20migration%20procedure%20and%20then%20manage%20all%20users%20in%20Azure%20AD.%20Once%20we%20do%20this%2C%20we%20would%20like%20to%20merge%20the%20two%20accounts%20for%20each%20individual%20retaining%20the%20%22ac%22%20(previously%20on-prem)%20domain%20as%20the%20upn.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20could%20discard%20the%20edu%20address%20but%20that%20will%20mean%20recreating%20over%20a%201000%20groups%20and%20mailboxes%20on%20cloud%20would%20be%20lost.%20(losing%20the%20mailbox%20on%20cloud%20is%20a%20compromise%20that%20is%20acceptable%2C%20if%20there%20is%20no%20way%20of%20merging%20the%20two%20upns%20in%20the%20cloud.%20Please%20note%20we%20do%20not%20want%20maintain%20a%20long-term%20hybrid%20co-existence%20and%20this%20merge%20needs%20to%20be%20done%20only%20after%20we%20have%20disconnected%20the%20on-premise%20infrastructure.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20adequate%20licenses%20for%20short-term%20co-existence%20of%20the%20two%20domains.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1430246%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1430437%22%20slang%3D%22en-US%22%3ERe%3A%20merging%20on%20prem%20domain%20with%20cloud%20domain%20azure%20ad%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1430437%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F230300%22%20target%3D%22_blank%22%3E%40Jacob%20John%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%20SMTP%20matching%20is%20probably%20going%20to%20be%20your%20best%20option%20here.%20%26nbsp%3BTake%20a%20look%20at%20the%20following%20articles%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F2641663%2Fuse-smtp-matching-to-match-on-premises-user-accounts-to-office-365%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-gb%2Fhelp%2F2641663%2Fuse-smtp-matching-to-match-on-premises-user-accounts-to-office-365%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fazure%2Factive-directory%2Fhybrid%2Fhow-to-connect-install-existing-tenant%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fazure%2Factive-directory%2Fhybrid%2Fhow-to-connect-install-existing-tenant%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1432417%22%20slang%3D%22en-US%22%3ERe%3A%20merging%20on%20prem%20domain%20with%20cloud%20domain%20azure%20ad%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1432417%22%20slang%3D%22en-US%22%3E%3CP%3EThansk%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F616707%22%20target%3D%22_blank%22%3E%40PeterRising%3C%2FA%3E.%20I%20accidentally%20created%20a%20second%20thread%20on%20the%20same%20issue.%20My%20concern%20was%20that%20once%20I%20do%20a%20soft-match%20it%20might%20mean%20I%20cannot%20pass%20the%20source%20of%20authority%20back%20to%20azure%20ad%20when%20I%20want%20to%20pack%20up%20the%20on-prem%20infrastructure.%20It%20might%20not%20be%20the%20case%20but%20I%20couldn't%20afford%20to%20find%20out%20in%20hindsight!%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

We created a cloud only domain for using Microsoft Teams ( managed in azure ad) college.edu but have another domain college.ac which is our primary on-premise domain managed in AD. We did this because we were not ready to migrate our mailboxes to the cloud or use our AD to manage cloud users at that point. So each user has an edu and an ac upn one for the cloud and the other on-premise

Now we have decided to migrate our on premise accounts to the cloud using an express migration procedure and then manage all users in Azure AD. Once we do this, we would like to merge the two accounts for each individual retaining the "ac" (previously on-prem) domain as the upn. 

We could discard the edu address but that will mean recreating over a 1000 groups and mailboxes on cloud would be lost. (losing the mailbox on cloud is a compromise that is acceptable, if there is no way of merging the two upns in the cloud. Please note we do not want maintain a long-term hybrid co-existence and this merge needs to be done only after we have disconnected the on-premise infrastructure. 

We have adequate licenses for short-term co-existence of the two domains. 

2 Replies
Highlighted

Thansk @PeterRising. I accidentally created a second thread on the same issue. My concern was that once I do a soft-match it might mean I cannot pass the source of authority back to azure ad when I want to pack up the on-prem infrastructure. It might not be the case but I couldn't afford to find out in hindsight! 

Thanks again