Fix a Google Workspace Migration Endpoint Connection in Microsoft 365
Question details
The administrator needs to create a Google Workspace migration endpoint in Microsoft 365 and determine which account details to provide.

- Product
- Exchange Online and Google Workspace
- Device & OS
- not provided
- Scenario
- An administrator is setting up a Google Workspace to Microsoft 365 mailbox migration.
- Observed behavior
- Endpoint creation fails with the message, “The connection to the server could not be completed.”
Have access to the Exchange admin center, the Google Admin console, and the prepared Google service account's JSON key file. Check Microsoft's current Google Workspace migration documentation for the required APIs, OAuth scopes, and account permissions.
Verify Google Workspace delegation and recreate the migration endpoint
Use this approach when Exchange Online cannot connect while creating the Google Workspace migration endpoint.
In the Google Cloud console, open IAM & Admin > Service Accounts and locate the service account prepared for the migration. Confirm that you have its JSON key file and client ID.
In the Google Admin console, go to Security > Access and data control > API controls > Manage Domain Wide Delegation. Check that the service account's client ID is authorized for the OAuth scopes required by Microsoft's migration instructions.
In the Google Cloud console, open APIs & Services > Enabled APIs & services and verify that the APIs required by Microsoft's Google Workspace migration instructions are enabled for the service account's project.
In the Exchange admin center, open Migration > Endpoints and start creating a Google Workspace migration endpoint. Upload the prepared service account JSON key when requested. If the wizard asks for a Google Workspace administrator email address, enter the administrator account specified by the wizard and Microsoft's instructions; do not assume it is the service account email.
Submit the endpoint configuration again. If the connection still fails, compare the administrator account, JSON key, delegation scopes, and API settings with Microsoft's current Google Workspace migration documentation.

Work with Office files during your migration using WPS Office
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations during a move between platforms. Its familiar interface and Microsoft Office format support make it easy to continue working with existing files. It does not create Exchange Online migration endpoints or migrate mailboxes.

Frequently Asked Questions
Which email address should I enter for the migration endpoint?
Follow the label in the Exchange admin center wizard and Microsoft's current migration instructions. If the field asks for a Google Workspace administrator email, provide the required administrator account rather than assuming it means the service account email.
Where can I check the service account's domain-wide delegation?
In the Google Admin console, go to Security > Access and data control > API controls > Manage Domain Wide Delegation. Find the service account's client ID and check its authorized OAuth scopes.
What should I check if the endpoint still cannot connect?
In Google Cloud, check the service account JSON key and enabled APIs. In the Google Admin console, verify the client ID and required delegation scopes. Then review the endpoint details in the Exchange admin center and retry.
Can WPS Office fix the Exchange Online migration endpoint?
No. The endpoint is configured in the Exchange admin center and depends on Google Workspace access settings. WPS Office can help you work with Office-compatible files, but it does not migrate mailboxes.




