Migrating your Google Workspace (GWS) domain name and configuring it within JumpCloud requires a series of carefully executed steps to ensure continuity and prevent user disruption. This article outlines the detailed process for changing the GWS domain name and configuring the new domain in JumpCloud.
Changing the GWS Domain Name and Configuring JumpCloud
- Temporarily Remove the GWS Integration:
- Deactivate the GWS Sync from the JumpCloud Admin Portal
- Important: Deactivating the Sync does NOT impact the users
- Do NOT remove the users from the directory sync as this action will suspend their Google accounts
- Deactivate the GWS Sync from the JumpCloud Admin Portal
- Map the New Domain in GWS
- Set the new domain as the primary domain for your users’ email addresses in the Google Workspace console
- Ensure that the new domain is correctly set as primary to prevent sync issues between JumpCloud and GWS
- Modify User Email Addresses in JumpCloud
- Update each user’s email address in JumpCloud to reflect the new domain
- This can be automated using the JumpCloud PowerShell module and the command given below:
- Or you can update email addresses via CSV upload, follow Update Users from a CSV File for detailed instructions
- Update each user’s email address in JumpCloud to reflect the new domain
- Reauthorise the GWS connection in the JumpCloud Admin Portal to ensure that the integration with the new domain is fully active.
- Users must sign into the User Portal again to sync their passwords to re-establish the sync between JumpCloud and Google Workspace with the new domain.
Best practices during Domain Migration
- MFA:
- MFA configured in JumpCloud Protect App will continue to work with the old domain
- However for best practices and to avoid confusion, it is recommended to delete the old domain entry in the Protect app and re-enroll with the new domain
- SSO Applications
- If JumpCloud is managing SSO applications, update the domain references within those applications
- This may involve updating fields or recreating the SSO configurations
- If Google is managing the SSO apps, no further action is required
- If JumpCloud is managing SSO applications, update the domain references within those applications
Conclusion
Following these steps ensures a smooth transition when migrating your Google Workspace domain name and configuring the new domain within JumpCloud. Always double-check each step to avoid sync issues and maintain user account integrity. If you encounter any issues or have further questions, please refer to the relevant Help Center Articles or contact JumpCloud Support directly.