O365 Tenant to Tenant Migration | Cross Tenant Mailbox Migration | Move Mailboxes Between Tenants

we are going to start a process from the destination 10 and where we are going to set up the necessary application ID and permission necessary the application ID will be shared with the source tenant where the global adminary Source will accept the invitation another generated into the attendant under the Enterprise application take note of the application ID by copying and pasting it into notepad or whatever you like next we are going to Grand over 6.5 exchange online graph API permission the permission in this case is mailbox migration on the application permission and that's all you need let's get the global address consent or do it yourself if you are the global admin next we are going to set up the clients that creates which will be needed when setting up the migration endpoint later on I recommend to set it to three months unless you feel like the migration will be taking longer than that RP declining secrets and save it somewhere save because you're going to need it later on thank you the next piece is critical this is where we are going to form the URL which will be sent to the source tenant admin the admin will have to accept the permission baked into the URL in order to create corresponding up ID in their tenant with necessary permission note that the source tenant orback domain is what is required in red and also the app ID we created early on once you've replaced the highlighted red with the proper Source Turner fallback domain and Clan ID send it to the admin via email and have them go through the prompt to accept the app to be printed in their tenant a mission required here is the same as the one we created in the destination tenant once the source standard admin accept the app that we created it can be found under Enterprise apps in Azure ID as you can see this is the same mailbox the migration application access we granted to the app by the destination tenant as well the next step is to log on to the destination tenant and set up the migration endpoint using it up ID and the secret key that we created earlier foreign key as a credential to create the migration endpoint and also specify the source data as our remote tenants because this is where the mailbox is currently reside and that's where we are trying to hold the mailbox forehead and run the script it looks like you created the migration endpoints successfully by the way if you are wondering what line 0.5 is all about this is a piece of code that checks if your tenant is dehydrated this simply means some organizational level functions are locked away and you need to run the enable organization customization commandlet in order to unlock them this is a brick amount for new tenants by the way next step is to create organizational relationship while we are still in the Target tenant Powershell session so this is just to specify that you are about to remove mailboxes between these two tenant so you're going to specify the source tenant ID again using the All Back Microsoft on microsoft.com domain and you need to specify that this is a mailbox move and the error you just saw right now is also what I was talking about earlier if your tenant is dehydrated that you need to run the enable organization customization in order for you to access some of these organizational level commands so it looks like it's done now so we're going to log out on a out of this tenant we're going to log back in into the sourced in it to continue the process thank you The Source tenant a security group is actually needed to be created in order to scope or restrict the mailbox migration they'll only have access to more content from the specific mailbox list so this list usually comes with all the mailboxes you would like to move using this process and that is what we're doing right now creating the security group this cannot be a distribution rule it has to be a security somebody saw standards using this Powershell script so we are going to specify the tenant ID or the like a tenant our app ID from the Enterprise app in Azure and security with name we just created has stopped so this book will also check if you already have organization relationship with the target domain and if you do if we make changes to that by enabling the mailbox most feature if not it will create a new one while that is running I'm going to populate the group by created with all the members these are the mailboxes we are going to move you can do this however you like manually or with script or from Azure bulk operation feature or using a specific process you have in your organization to manage group membership Next Step here could have been done way before starting the migration setup we are going to use a script to pull mailbox reports from the source statement you can have the admin of the tenant do this void if they'll have access you want to make sure you have the display name the primary SMTP address and also the exchange grid and the proxy addresses that they report The Exchange would be very very important because this is how Microsoft knows that this is the mailbox that this is the object that I'm supposed to move that mailbox into so we're going to take that report and use it to create mail users in the Target payment my script here I'm also using the Legacy action DN attribute to stamp the mail user object with ADD 500 addresses this will take care of issues with ndr when sending from hash object in Outlook and also setting the exchange grid as well once you are done with this process you must license them with either F1 F3 E3 E5 license depending on the requirement I recommend E3 if you have mailboxes with over 50 gigabyte in size in them will not create a mailbox for them it will only put them in a staging mode which will be released once the migration is completed the next level now is to go ahead and create our migration back from the new exchange admin Center processes are pretty straightforward and I will not go through the in-depth explanation for this you just pretty much select the migration type you specify your migration you select the endpoint you created and you aim for the csb that you also prepared to migrate the mailboxes and then you simulate your target delivery domain and you schedule the batch however you want it and that's pretty much the end of the process now if you want me to create a separate video on how to pre-migration batches all the things that you might want to consider using that then I will create a separate video if you have any specific question about this process hit me up if you like the video and learn it you know too please drop it like comment share it and subscribe for Content related to office first to buy talk to you guys later

Channel: Tunde T.

Views: 9,454

Keywords: EXO, EXOMigration, Exchange, ExchangeMigration, ExchangeOnline, ExchangeOnlineMigration, M365, Mailbox, Migration, O365, Office365, Tenant2Tenant, TenantToTenant, Tenants

Id: -hLaqhLhxj8

Length: 9min 49sec (589 seconds)

Published: Sun Jan 01 2023