To analyze and prepare your on-premises environment for an Office 365 deployment, use the Microsoft Office 365 Deployment Readiness Tool in accordance with the Microsoft Office 365 Deployment Guide.
To get the Microsoft Office 365 Deployment Guide for Enterprises, go to http://community.office365.com/en-us/f/183/p/1541/5095.aspx. The tool can be downloaded from http://community.office365.com/en-us/f/183/p/2285/8155.aspx.
You need to add each email domain you want to migrate to Microsoft Office 365 as an accepted domain of your Microsoft Office 365 tenant. The migration service will then use the SMTP addresses of your on-premises mailboxes to create the corresponding email addresses for the new Office 365 mailboxes.
For information on adding company domains to Microsoft Office 365, read Adding domains and users to Office 365 article.
You need to create at least four separate administrative accounts which will be used during migration for one of the following tasks:
|Provisioning user accounts in Office 365||
||Refer to the Requirements for provisioning user accounts in Office 365|
||Refer to the Requirements for synchronizing mailboxes, calendars and public folders in Office 365|
|Synchronizing public folders||
The administrative account must have the Exchange administrator, User management administrator user roles and ApplicationImpersonation and Mail Recipients roles in the Microsoft Office 365 tenant. A Microsoft Exchange Online license must be issued for this administrative account. This account must have the default UPN suffix <tenant_name>.onmicrosoft.com. To create the administrative account you should perform the following:
Grant the account User management administrator and Exchange Administrator user roles:
$cred = Get-Credential
Connect-MsolService -Credential $cred
Add-MsolRoleMember -RoleName 'User Account Administrator' -RoleMemberEmailAddress <User E-mail address>
Add-MsolRoleMember -RoleName 'Exchange Service Administrator' -RoleMemberEmailAddress <User E-mail address>
$proxy = New-PSSessionOption –ProxyAccessType IEConfig
$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $cred -Authentication Basic –AllowRedirection -SessionOption $proxy
New-RoleGroup -Name 'QMMAD Accounts' -Roles 'ApplicationImpersonation', 'Mail Recipients' -Members <User>
A Microsoft Exchange Online license must be issued to these administrative accounts. These accounts must have the default UPN suffix <tenant_name>.onmicrosoft.com. Also they must have the User Management Administrator, Mail Recipients and ApplicationImpersonation roles in the Microsoft Office 365 tenant. There are two options how to grant the required roles:
Note: For speeding up migration performance, you will need to use multiple administrative accounts for calendar synchronization and mailbox migration. Using the script allows automating account creation and role assignment.
You can create the accounts via PowerShell with the minimum required permissions acceptable.
To download CreateQSGranularPermissionAdminAccountsInMSOLModule.ps1 script and see step-by step usage instructions refer to Migration Manager for Exchange Knowledge Base article: https://support.quest.com/migration-manager-for-exchange/kb/255600/how-to-create-o365-service-accounts-with-required-permissions.
Caution: The user account that you specify for the Create-QSGranularPermissionAdminAccountsInMSOL cmdlet must have the Global Administrator role in Microsoft Office 365.
The administrative accounts specified in .CSV file will be created in Microsoft Office 365 and granted the User Management Administrator, Mail Recipients, and ApplicationImpersonation user roles.
For the account you are going to use for public folder synchronization by legacy Exchange agents, the following steps are also required:
Create a new PowerShell session with Office 365:
$cred = Get-Credential
$proxy = New-PSSessionOption
$session = New-PSSession
Add the necessary account and assign it the Owner role. Select the Apply changes to this public folder and all its subfolders option and save your changes.
Caution: At this time, the account you specify in the properties of your Office 365 target organization is used for public folder synchronization. By default, this account registers Microsoft Office 365 as the migration destination.
For the account you are going to use for public folder synchronization by MAgE refer to Public Folder Synchronization (MAgE) document.
To synchronize public folders with Office 365 organization, you need to create special Outlook profiles on the agent host associated with Office 365 where you plan to install PFSA and PFTA.
For that, log on to agent host under the Agent Host Account, open Start | Control Panel | Mail (32-bit) and click Show Profiles. You must create two profiles: one named MMEX_PFSA and the other — MMEX_PFTA. To create each profile, take the following steps:
To ensure that logon to created profiles through Outlook can be performed correctly, run Outlook 2013 or Outlook 2016 32-bit version and select the MMEX_PFSA (MMEX_PFTA) profile. If no error messages, credential prompts or any other message boxes that require user response appear, then profile is created properly and therefore can be used by PFSA and PFTA to perform public folder synchronization.
NOTE: Make sure that no issues related to certificate validation occur when you run Outlook.