Something seems to have happened with new service accounts around the week starting 20th of April.
Service Accounts created after this date can’t be added to services that treat it as a Google Account, the two services I know are having issues with this are Search Console and GA4.
Attempting to add the email of a service account created past that date leads to an error: Search Console:
It seems like whatever process happens to create whatever is needed for these services to see a service account as a Google Account has stopped happening.
Given it’s happening in two different services, it seems an issue with cloud.
A service account created before this date can be added without issue.
The new service accounts do seem to work otherwise, i.e. accessing big query using the JSON key etc, so it doesn’t seem service accounts are broken full-stop.
Is this a bug? Or is there something that now needs to be done with a service account so it can be treated as a Google Account for these things?
Seeing this again as of mid-September. A service account created Sep 4 was successfully added to three GA4 properties that same day, so it was working then. As of Sep 14 the same address is rejected by the Add users dialog on new properties, both on my own GA account and on a client’s, with two different admins. A regular gmail.com address is accepted normally in the same dialog. A second service account in a separate Cloud project is also rejected, so it doesn’t appear project-specific.