Enable-OrganizationCustomization command can take a very long time to run and will likely display an error saying that the tenant is already enabled.
New-ManagementRoleAssignment -Name "App Impersonation" -Role "ApplicationImpersonation" -User You will be asked to enter some credentials, enter the Global Admin from the source tenant first.
Search for Windows PowerShell (PowerShell should already be installed).Note: these are recommended steps to avoid asking all passwords from your end-users. Step 6 - Enable SSI (Source-Side Impersonation) on GoDaddy Important: make sure that the Global Account is licensed too!.Make sure to save it locally on Notepad.
Sign-Out for the Azure Portal and open a new browser session and login to with the New Global Admin Account During the first sign-in, reset the password and set a new password.You will get a temporary Password, Copy the temp password as well as the username into Notepad.Look for an Admin account that looks like Select this user account and click on Reset Password at the Top Navigation pane > Reset Password.Once on the Azure portal, select Azure Active Directory.Use the GoDaddy credential from one of the users with Admin privileges.Go to A zure AD Portal (in private mode).Make sure to replace in the last PowerShell command above with the global admin account used for migration.Enable-OrganizationCustomization command can take few minutes to run.New-ManagementRoleAssignment -Name "App Impersonation" -Role "ApplicationImpersonation" -User You will be asked to enter some credentials, enter the Global Admin from the target tenant first. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic -AllowRedirection Run the following PowerShell commands (one at a time):.Start PowerShellunder an administrator context (right-click -> run as administrator).Search for Windows PowerShell(PowerShell should already be installed).Step 4 - Enable SSI (Source-Side Impersonation) on the Target Office 365 Tenant The Global Admin account needs to be licensed as well. They must have at least Exchange Online Plan 1 assigned. Note: all end-users included in the email migration must be licensed.Provision all the necessary Microsoft 365 licenses from BEMO, your CSP (Cloud Solution Provider) ?.Create all end-users accounts using the.Make sure you are a Global Administrator on the target tenant.Log on the target Microsoft 365 admin portal.If you are not using GoDaddy DNS, make sure to follow the steps from your provider Step 3 - Preparation Steps on the Target Office 365 Tenant Save the file locally so you can restore the DNS to its original state if something were to happen.Under the Advanced Feature section in the bottom of the page, click on Export Zone File (Windows).Select the domain you will be working on.Step 2 - Backup Client GoDaddy DNS settings Validate that you can still connect to the DNS on GoDaddy (or whatever DNS provider you are using).Let's start! The entire process should only take about 60 to 75 minutes!