I'm trying to change the primary domain for a Google Workspace account. The organization previously had ChromeOS devices enrolled, so I contacted Google support. They told me to deprovision the devices and remove the related licenses, which has now been done.
However, the Admin console still shows that changing the primary domain isn't available because of one or more excluded account or product conditions, including domain purchases during signup, Google Domains purchases, education or reseller accounts, trials, and various Chrome or kiosk licenses.
I don't know whether the Chrome licenses were the only blocking condition or whether something else is preventing the change. Support has told me to wait 24 hours, try again, and open another ticket if a different error appears. They also said the Chrome upgrades were causing the problem, but I'm confused about why other possible blockers can't be checked or resolved at the same time.
Is there a reliable way to identify every condition preventing the primary-domain change, or is this something Google support must process manually?
2 Answers
There are two separate things here: changing the primary domain in the Admin console and having Google perform the change on the backend. In some cases, the original primary domain remains effectively locked after setup, even though the console displays an option for changing it. You may be able to add the new domain as a secondary domain and move users to it, but the actual primary-domain change might still require Workspace support.
A support team may need to verify ownership and process the change manually. It can take a few business days, and the old domain may also remain undeletable for a waiting period after the change.
I’d ask for the case to be escalated to a team that handles Workspace account and domain changes. The most suspicious items are the way the Workspace subscription was originally created and whether the domain was purchased through Google, rather than the devices themselves. Removing Chrome licenses may clear one blocker, but it doesn’t necessarily prove that the account is eligible for a primary-domain change.
I’ve already been transferred through several supposed escalation paths. If the account was created or purchased in one of the excluded ways, does that mean changing the primary domain is permanently unavailable?
That’s what confuses me—the Admin console exposes an option to change the domain. It seems odd for the option to be present if the account still requires a manual change.