Skip to main content
quickorder
New Member
Jun 8, 2026 9:37 AM UTC
Question

Android Management API enrollment blocked with "Since your organization reached its usage limits"

  • 5 replies
  • 256 views
  • Translate All • Beta, powered by Gemini

Hello,

I am integrating Android Management API (AMAPI) for dedicated kiosk devices and I am currently blocked during device enrollment.

Environment

  • New Google Cloud project
  • Android Management API enabled
  • Billing enabled and linked to the project
  • New service account
  • New Android Enterprise created
  • EMM successfully linked in Google Workspace Admin
  • Enrollment tokens successfully created through the API
  • Enterprise accessible through API (HTTP 200)

Observed behavior

  1. Enrollment token is generated successfully.
  2. QR code provisioning starts correctly.
  3. During provisioning, Android displays the following error:

Can't set up device. Since your organization reached its usage limits, this device can't be set up.

  1. The device never appears in Android Management API.
  2. Device inventory always remains empty.
  3. No policy is attached to the enrollment token.
  4. The issue occurs on multiple devices from different manufacturers.

Diagnostics

  • Enterprise accessible: YES
  • Enrollment token creation: YES
  • Access token generation: YES
  • Billing enabled: YES
  • Android Enterprise active: YES
  • EMM linked: YES
  • Devices visible in enterprise: 0
  • Policies: 0

Additional testing already performed

To rule out configuration issues, we recreated the entire environment from scratch:

  • New Google Cloud project
  • New billing configuration
  • New service account
  • New Android Enterprise
  • New enrollment tokens

The result remains exactly the same.

We also tested on multiple Android devices and always receive the same "usage limits" error during provisioning.

Key observation

The enrollment token is accepted and provisioning starts, but the device is rejected before it is created in Android Management API.

The device inventory remains empty at all times.

Question

Is there any hidden enrollment quota, Android Enterprise restriction, enterprise validation requirement, Workspace limitation, or backend enrollment limit that could cause Android to reject enrollment before the device is created?

Any guidance would be greatly appreciated.

Thank you.

5 replies

Moombas
Level 4.4: KitKat
Jun 8, 2026 10:51 AM UTC

Even it might not fit 100%, i guess this comment from ​@jasonbayton here in a different but equal topic might say it best: https://www.androidenterprise.community/android-enterprise-general-discussions-3/org-usage-limits-error-no-enrolled-devices-2661?postid=9580#post9580

 

​@Lizzie and ​@Kirk as this topic raises again and again, maybe reach out internally that this might need a bit clearer communication when people try to use the system.

Translate • Beta, powered by Gemini
Android Enterprise Expert
jasonbayton
Level: 4.1: Jelly bean
Jun 8, 2026 10:55 AM UTC

Unfortunately it's not hidden, it's just not obvious enough in the right places to properly surface the requirements to new partners/orgs.

 

https://developers.google.com/android/management/permissible-usage#quotas_and_restrictions

 

 

Translate • Beta, powered by Gemini
Droider in Chief - bayton.org
Moombas
Level 4.4: KitKat
Jun 8, 2026 11:43 AM UTC

Yeah i know and that’S what i meant, it might be get better visualized in the documentation or even before step 1 or so.

Translate • Beta, powered by Gemini
Android Enterprise Expert
jasonbayton
Level: 4.1: Jelly bean
Jun 8, 2026 11:59 AM UTC

+ in the GCP console, error messages, etc. Lots can be done to make this suck less indeed.

Translate • Beta, powered by Gemini
Droider in Chief - bayton.org
Kirk
Community Manager
Jun 8, 2026 2:51 PM UTC

Thanks ​@Moombas for the ping and ​@jasonbayton for the advice.

Lizzie and I will make sure this is passed along to the appropriate people internally!

Translate • Beta, powered by Gemini