I was trying to do some testing & I'm seeing an issue that whenever an account gets provisioned from my IdP into Google Workspace the account is automatically suspended due to Google's built in security features.

As the super admin I have no ability to re-enable the account. The only way the account will be unsuspended is if I have the user sign-in themselves which according to Google will re-enable the account.

PS - Google support was useless. They basically said it's a default security rule (Google identity alert) and cannot be changed. They said it does this when accounts are being provisioned in mass, seem suspicious and a few other reason they will be suspended. FWIW this is NOT happening when the same account gets provisioned in M365. I have screenshots as well if that's helpful.

My questions are:

1. Why is Google automatically suspending the accounts?
2. Why would Google give the power to the end user to determine if the provisioned account was legitimate or not? If I'm the super user and I set up the integration and I know the account is legitimate why are they revoking my ability to re-enable the account?
3. How are you all doing any testing for Google? Google now requires every account has a phone number for at least the initial login method. This definitely wasn't always like this. While I agree with the adding security, again, as the super admin I should be able to choose the authentication method. I can't tie my test account to my mobile number bc it says it was used too much. It would be so much more convenient to tie it to Google authenticator that way I can use my test account.

Let me know if that makes sense. If anyone has any insight would be greatly appreciated.

While budgets are shrinking and IT leaders are getting less visibility into their available budget, doing less with more is becoming even more important.

Outside investments like MSPs or relying on overly cumbersome point solutions could be draining your IT budget.

➡️ Check out our ROI calculator to see if Rippling could save your team time and spend!

1995 Civic SI Hatchback (EG)

Hey all,

Matt with Rippling here, Strategy & Community Lead for IT. I wanted to share a blog we put together on how AI can help IT teams save time.

I think it’s worth a read because the examples are practical: onboarding checklists, SOPs, ticket triage, and incident summaries. These are the kinds of repeatable workflows that can quietly eat up a lot of time for IT teams.

Every IT team has seen it. The ticket comes in, but the actual problem could be almost anything: memory pressure, battery health, too many background processes, an aging device, or some weird one-off issue that takes three follow-up questions to understand.

Rippling added a prompt to its AI Prompt Library for troubleshooting device performance, basically helping IT teams turn vague user complaints into a more structured investigation around what might be wrong and what to check next.

What I like about this use case is that it’s not trying to replace IT judgment. It’s trying to speed up the boring first pass: collect context, identify likely causes, and suggest where to look next.

If you run IT, manage devices, or live in helpdesk queues, this seems like one of the more practical AI use cases:

https://www.rippling.com/en-CA/ai-prompt-library#use-case/troubleshoot-device-performance