'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix Google Workspace to Microsoft 365 Mail Migration Provisioning Error
Question details
The administrator needs to resolve a provisioning failure preventing the successful migration of user mailboxes from Google Workspace to Microsoft 365.
- Product
- Microsoft 365 / Exchange Online
- Device & OS
- not provided
- Scenario
- Migrating email data from Google Workspace to Microsoft 365 using a configured migration batch and endpoint.
- Observed behavior
- The migration batch fails with a provisioning error despite the endpoint and prerequisites being configured, often due to unlicensed users, invalid SMTP addresses, or incorrect CSV configurations.
Ensure you have global administrator or Exchange administrator privileges in your Microsoft 365 tenant and that you have access to Exchange Online PowerShell.
Verify User Licenses and Mailbox Provisioning
Use this solution to ensure the target user has the necessary licenses assigned, which is required for Microsoft 365 to provision the mailbox.
A common cause for provisioning errors is that the target Microsoft 365 account has not been assigned a license that includes Exchange Online. Without this license, the mailbox cannot be created to receive the migrated data.
Navigate to the Microsoft 365 admin center and log in with your administrator credentials.
Go to 'Users' > 'Active users' in the left-hand navigation pane and search for the user who failed the migration.
Click on the user's display name, go to the 'Licenses and apps' tab, and ensure a license containing Exchange Online (e.g., Microsoft 365 Business Basic, E3) is checked. Save any changes.
Wait a few minutes for the mailbox to finish provisioning in the background, then retry the migration batch.
Correct the Migration CSV File and SMTP Addresses
Check your migration batch mapping file to ensure the EmailAddress identifiers exactly match the Microsoft 365 tenant data.
Investigate Errors with Exchange Online PowerShell
Use PowerShell commands to pull detailed diagnostics on the affected user and the specific migration batch.
Looking for a Lightweight Alternative to Microsoft 365?
Enterprise cloud migrations and tenant administration can be complex. If you or your users simply need reliable, powerful office software without the heavy administration overhead, WPS Office provides a fully featured desktop suite that is highly compatible with Microsoft formats.
Frequently Asked Questions
Why does my migration batch say 'ProvisioningFailed'?
This status typically occurs when the target Microsoft 365 user lacks a valid Exchange Online license, the CSV mapping file contains an incorrect email address, or the target mailbox has not finished being created in the tenant.
Do I have to license users before migrating from Google Workspace?
Yes. Microsoft 365 requires the target user account to exist and be assigned a valid license that includes Exchange Online services before it can provision the mailbox to receive migrated emails.
How can I view the exact error message for a failed migration user?
You can view detailed error messages by navigating to the Exchange admin center, clicking on your migration batch, and selecting 'View details' under the user status. Alternatively, use the 'Get-MigrationUserStatistics' cmdlet in Exchange Online PowerShell.
