Cutover migration with already setup Azure AD and SSO

%3CLINGO-SUB%20id%3D%22lingo-sub-1558445%22%20slang%3D%22en-US%22%3ECutover%20migration%20with%20already%20setup%20Azure%20AD%20and%20SSO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1558445%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20looking%20at%20doing%20a%20cutover%20migration%20with%20our%20current%20Exchange%202013%20DAG%20setup%20to%20exchange%20online.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20about%20112%20users%20to%20move%20so%20going%20with%20the%20cutover.%20We're%20going%20that%20way%20also%20to%20remove%20the%20ned%20of%20having%20an%20onsite%20exchange%20presents.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20thing%20that's%20I've%20been%20reading%20about%20is%20that%20you%20need%20to%20disable%20DirSync%20to%20perform%20the%20cutover%20migration.%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20question(s)%20are%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Will%20disabling%20DirSync%20(which%20will%20move%20all%20users%20into%20the%20deleted%20users)%20stop%20SSO%20access%20to%20our%20over%20products%20we%20use%20day%20in%20and%20day%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2.%20Does%20having%20an%20already%20synced%20Azure%20AD%20impact%20on%20the%20migration%2C%20IE%20will%20it%20duplicate%20users%2Fmailboxes%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3.%20Does%20having%20no%20exchange%20presences%20onsite%20with%20DirSync%20enabled%20(After%20migration)%20cause%20issues%3F%20we%20have%20no%20plan%20on%20moving%20back%20to%20onsite.%20We%20do%20plan%20on%20keeping%20users%20onsite%20and%20in%20azure%20with%20the%20Sync%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20a%20bunch%2C%20I%20cant%20find%20any%20documentation%20that%20covers%20our%20specific%20scenario%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1558445%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ecutover%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESSO%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Occasional Visitor

Hi All,

 

 

We are looking at doing a cutover migration with our current Exchange 2010 DAG setup to exchange online.

 

We have about 112 users to move so going with the cutover. We're going that way also to remove the ned of having an onsite exchange presents.

 

Only thing that's I've been reading about is that you need to disable DirSync to perform the cutover migration. 

My question(s) are

 

1. Will disabling DirSync (which will move all users into the deleted users) stop SSO access to our over products we use day in and day out.

 

2. Does having an already synced Azure AD impact on the migration, IE will it duplicate users/mailboxes

 

3. Does having no exchange presences onsite with DirSync enabled (After migration) cause issues? we have no plan on moving back to onsite. We do plan on keeping users onsite and in azure with the Sync

 

Thanks a bunch, I cant find any documentation that covers our specific scenario 

1 Reply
Highlighted

Hey @JakeJoint ,

 

There are a few challenges here, to answer your questions first:

 

1. Disabling Dirsync will not delete the users, the users will be converted to in cloud with same password. However, if you are planning to perform a cutover migration, having users with same domain in office 365 would cause issues. Cutover migration process basically creates the users on its own in office 365, if the same users are present in office 365 cutover migration will fail.

 

2. Cutover migration requires dirsync to be disabled and there should not be any users present in office 365, so you will have to disable dirsync and delete in-cloud the users from office 365 ( if they are provisioned with same upn).

 

3. It is not a requirement to have exchange server on-premises after migration, you manage user attributes in a synced environment using active directory users and computers.

 

All things considered is there any specific reason you are opting for cutover migration  ? a hybrid migration will be best with your current environment.