Google has officially acknowledged a widespread bug blocking developers from adding new Google Cloud service accounts to Google Search Console and Google Analytics 4. 

This glitch seems to have popped up around April 23 and is effectively freezing new API integrations. It is pretty bad for digital agencies trying to onboard clients right now, with sprint deadlines actively slipping as teams lose access to crucial data routing tools.

The failure happens at the very last step. Anyone pasting a fresh service account email into the permissions tab is hitting a hard block. The system simply spits back an error reading: “Failed to add user: email not found.”

Early on, users flooded a Google Analytics Community thread looking for a workaround.

google-cloud-not-allowed-complaint-thread

A product expert there initially suggested standard troubleshooting steps to clear the hurdle. According to his early replies, users just needed to ensure they copied the email address without any hidden spaces and correctly verified the IAM setup in Google Cloud.

But as the days dragged on, it became glaringly obvious that user error was not the culprit. Developers were waiting well over 48 hours, hoping for normal DNS or IAM propagation delays. They verified site ownership via HTML upload, confirmed the GSC API was active, and checked their JSON keys.

The keys validate perfectly and grab OAuth tokens without issue. The Google user interface just outright refuses to recognize the generated email addresses.

When one frustrated developer pressed for an update nearly a week after the initial thread opened, the product expert said that there were no updates, confirming that the only thing they know is that Google is looking into it.

google-search-console-issue-being-looked-into

To stem the flood of duplicate complaints, Product Experts finally escalated the problem into a single pinned tracking thread.

search-console-email-address-not-found-escalated

They made it clear to users that tweaking settings will not help. The failure is completely out of their hands. It is a recognized bug on Google’s end.

At the time of this writing, there is no timeline for a fix. We’ll keep an eye out for any further developments and will update the article accordingly.

Featured image generated with AI

We stand out from the tech-media crowd because we break news stories; we mainly bring you stuff that you won’t find anywhere in the mainstream tech media. Our stories have been picked up by some of the world’s most popular websites and media outlets—more info is available here.

Dwayne Cubbins
2826 Posts

I cover fast-moving stories across apps, online platforms, and everyday tech — phones, wearables, consoles, and whatever else people are fighting with this week. Bugs, rollouts, scams, policy enforcement, and the occasional internet-culture rabbit hole are all fair game. My goal is simple — make confusing tech news readable. When I'm not working, I'm working out or chilling with my dog. Got a tip? You can find me on X @dcubbins.

Next article View Article

Android 17 QPR1 Beta 3 breaks Microsoft Teams and Outlook for Pixel users [U: Fix]

Update (May 21, 2026): A fix for the issue is currently live with the Intune beta app. Multiple users have confirmed that installing version 5.0.6983.0, currently...
May 20, 2026 2 Min Read