Sharepoint online and Exchange online dependency

%3CLINGO-SUB%20id%3D%22lingo-sub-203644%22%20slang%3D%22en-US%22%3ESharepoint%20online%20and%20Exchange%20online%20dependency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203644%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Folks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20had%20a%20doubt%20on%20the%20dependency%20between%20migration%20of%20sharepoint%20and%20exchange%20online.%3C%2FP%3E%3CP%3EWe%20have%20a%20scenario%20where%20on%20of%20the%20business%20units%20in%20an%20existing%20company%20is%20going%20to%20move%20to%20a%20o365%20tenant%20of%20its%20own.%3C%2FP%3E%3CP%3ESo%20in%20terms%20of%20migration%20itself%2C%20can%20the%20users%20be%20created%20on%20AAD%20with%20licenses%20assigned%20and%20move%20the%20sharepoint%20data%20first%20followed%20by%20exchange%20later%20or%20is%20the%20presence%20of%20the%20mailbox%20for%20the%20user%20on%20the%20new%20tenant%20mandatory%20before%20the%20sharepoint%20data%20is%20migrated%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ERamana%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-203644%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203754%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20online%20and%20Exchange%20online%20dependency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203754%22%20slang%3D%22en-US%22%3ESo%20you%20are%20not%20doing%20any%20kind%20of%20hybrid%20%2F%20adsync%20for%20the%20new%20tenant%3F%20if%20not%20then%20when%20you%20migrate%20your%20SharePoint%20content%20you'll%20have%20to%20use%20something%20like%20Sharegate%20etc.%20to%20map%20to%20new%20user%20accounts%20so%20you%20don't%20lose%20that%20meta%20data%2C%20but%20you%20will%20also%20have%20to%20as%20Juan%20said%20have%20your%20new%20mailbox%20setup%20via%20outlook%20or%20access%20via%20web%20to%20get%20the%20e-mails%20sent%20from%20SharePoint%20since%20the%20users%20it'll%20have%20mapped%20etc.%20will%20be%20the%20new%20e-mail%20in%20O365.%3CBR%20%2F%3E%3CBR%20%2F%3ENot%20doing%20Hybrid%20will%20make%20it%20a%20little%20bit%20more%20complicated.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203666%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20online%20and%20Exchange%20online%20dependency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203666%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Juan%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIm%20not%20sure%20if%20I%20understood%20the%20business%20domain%20part%20correctly.%3C%2FP%3E%3CP%3EThere%20will%20be%20a%20new%20domain%20(newdomain.sharepoint.xom)%20of%20course%20and%20the%20there%20will%20be%20a%20new%20email%20address%20for%20each%20of%20the%20users%20as%20well.%20So%20exchange%20mailboxes%20will%20be%20migrated%20to%20a%20new%20domain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ERamana%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203661%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20online%20and%20Exchange%20online%20dependency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203661%22%20slang%3D%22en-US%22%3EYes%2C%3CBR%20%2F%3ESome%20of%20them%20that%20come%20to%20my%20memory%3A%3CBR%20%2F%3E(1)%20Teams%20required%20Exchange%20Online%20enabled%20for%20users%2C%20so%20you%20will%20have%20to%20disable%20Teams%20until%20you%20are%20fully%20operational%20in%20the%20new%20tenant%3CBR%20%2F%3E(2)%20Notifications%20sent%20by%20SPO%20are%20not%20going%20to%20work%20since%20each%20user%20that%20is%20accessing%20to%20SPO%20does%20not%20have%20an%20e-mail%20assigned.%3CBR%20%2F%3E%3CBR%20%2F%3EBy%20the%20way%2C%20since%20you%20are%20not%20adding%20the%20domain%20of%20that%20Business%20Unit%2C%20I%20don't%20see%20a%20problem%20on%20enabling%20EXO%20for%20the%20users...of%20course%2C%20it%20depends%20on%20the%20strategy%20%2F%20approach%20you%20are%20going%20to%20follow%20to%20make%20a%20T2T%20migration%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203659%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20online%20and%20Exchange%20online%20dependency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203659%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Juan%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnderstood%2C%20we%20will%20have%20the%20users%20created%20and%20license%20assigned%20and%20perform%20the%20sharepoint%20migration%20first.%20In%20the%20source%20tenant%2C%20there%20are%20no%20Teams%20%26amp%3B%20groups%20but%20there%20is%20a%20plan%20to%20use%20them%20on%20new%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20it%20be%20possible%20to%20know%20what%20would%20be%20the%20impact%20of%20not%20having%20the%20exchange%20mailbox%20in%20the%20target%20tenant%20enabled%20during%20go-live%3F%20Would%20any%20of%20the%20functionalities%20be%20impacted%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ERamana%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-203654%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20online%20and%20Exchange%20online%20dependency%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-203654%22%20slang%3D%22en-US%22%3EMy%20two%20cents%20here%3A%3CBR%20%2F%3EYou%20can%20do%20the%20SharePoint%20migration%20first%20with%20any%20problems%2C%20but%20in%20order%20to%20keep%20metadata%20such%20as%20the%20user%20who%20created%20a%20document%20or%20the%20user%20who%20modified%20a%20document%2C%20you%20should%20at%20least%20have%20your%20users%20provisioned%20int%20he%20target%20tenant%20so%20when%20you%20do%20the%20migration%20you%20can%20make%20the%20required%20mappings%3C%2FLINGO-BODY%3E
Frequent Contributor

Hi Folks,

 

I had a doubt on the dependency between migration of sharepoint and exchange online.

We have a scenario where on of the business units in an existing company is going to move to a o365 tenant of its own.

So in terms of migration itself, can the users be created on AAD with licenses assigned and move the sharepoint data first followed by exchange later or is the presence of the mailbox for the user on the new tenant mandatory before the sharepoint data is migrated?

 

Regards,

Ramana

5 Replies
My two cents here:
You can do the SharePoint migration first with any problems, but in order to keep metadata such as the user who created a document or the user who modified a document, you should at least have your users provisioned int he target tenant so when you do the migration you can make the required mappings

Thanks Juan,

 

Understood, we will have the users created and license assigned and perform the sharepoint migration first. In the source tenant, there are no Teams & groups but there is a plan to use them on new tenant.

 

Would it be possible to know what would be the impact of not having the exchange mailbox in the target tenant enabled during go-live? Would any of the functionalities be impacted?

 

Regards,

Ramana

Yes,
Some of them that come to my memory:
(1) Teams required Exchange Online enabled for users, so you will have to disable Teams until you are fully operational in the new tenant
(2) Notifications sent by SPO are not going to work since each user that is accessing to SPO does not have an e-mail assigned.

By the way, since you are not adding the domain of that Business Unit, I don't see a problem on enabling EXO for the users...of course, it depends on the strategy / approach you are going to follow to make a T2T migration

Thanks Juan,

 

Im not sure if I understood the business domain part correctly.

There will be a new domain (newdomain.sharepoint.xom) of course and the there will be a new email address for each of the users as well. So exchange mailboxes will be migrated to a new domain.

 

Regards,

Ramana

So you are not doing any kind of hybrid / adsync for the new tenant? if not then when you migrate your SharePoint content you'll have to use something like Sharegate etc. to map to new user accounts so you don't lose that meta data, but you will also have to as Juan said have your new mailbox setup via outlook or access via web to get the e-mails sent from SharePoint since the users it'll have mapped etc. will be the new e-mail in O365.

Not doing Hybrid will make it a little bit more complicated.