Hello,I am integrating Android Management API (AMAPI) for dedicated kiosk devices and I am currently blocked during device enrollment.EnvironmentNew 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 behaviorEnrollment token is generated successfully. QR code provisioning starts correctly. 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.The device never appears in Android Management API. Device inventory always remains empty. No policy is attached to the enrollment token. The issue occurs on multiple devices from different manufacturers.DiagnosticsEnterprise 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: 0Additional testing already performedTo 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 tokensThe result remains exactly the same.We also tested on multiple Android devices and always receive the same "usage limits" error during provisioning.Key observationThe 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.QuestionIs 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.

New Member

Question

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

Forum|Forum|8 hours ago
June 8, 2026
3 replies
24 views

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

Enrollment token is generated successfully.
QR code provisioning starts correctly.
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.

The device never appears in Android Management API.
Device inventory always remains empty.
No policy is attached to the enrollment token.
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.

Moombas

Level 4.4: KitKat

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.