Device Owner Enrollment Error: “Organization Has Reached Its Usage Limits” Even With Zero Devices

Hi everyone,

I’m trying to enroll a fully managed Android device using the Android Management API. I generate an enrollment token, create the QR code, factory reset the device, and start the QR-based provisioning process. Everything works until the Android Device Policy step, where I get the following error:

“Since your organization has reached its usage limits, this device can’t be set up.”

I am unable to get past this point.

Here is what I have already checked:

Listing devices through the API returns an empty list. There are no enrolled devices at all.
Billing is active on the cloud project and the Android Management API is enabled.
Enterprise creation works, policies return correctly, and I can generate enrollment tokens without any issues.
The device is correctly factory reset and the QR scan is working as expected.
I tested with both a Workspace-based enterprise and a Gmail-based enterprise. The same limit error appears on both, even though both enterprises have zero devices.
I moved the cloud project under my organization in Google Cloud to avoid any project-level quota problems.

Based on everything I have checked, it appears that the enterprise (or account) has been automatically restricted to a device quota of zero, and the restriction has not lifted even after several days.

I would like to understand the following:

Is this quota lock normal for new enterprises, and how long does it usually take to lift?
Is this quota tied to AMAPI commercial approval?
Is it expected that zero devices can be enrolled before approval?
Is there any way to request a quota review so that at least one test device can be enrolled?

I am building a commercial EMM solution and simply need to test device-owner provisioning on a physical device, but I am currently blocked by this limit.

Any guidance from the community or anyone who has dealt with the same situation would be greatly appreciated.

Thank you.