Forum Discussion
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.
Hello rpnexa
I hope you're well!
I've checked with our tech team and they have confirmed that this is expected behaviour for new Google Cloud Projects and is not a technical bug in your code.
Google applies a default "Safety Quota" of zero for Device Owner enrolments on new, unverified projects to prevent abuse. This is why you see the error even with no devices enrolled.
Here's how to fix it:
Go to your Google Cloud Console > IAM & Admin > Quotas.
Filter for Android Management API.
Request an increase for the Enrolment or Device quota.I hope this is helpful; could you let us know if the fix provided helped?
Thanks in advance,
Emilie
11 Replies
Hello rpnexa
I've found a similar query that was asked over the summer in the community, and another one that was asked just a month ago - it seems you need to increase your quota and this can be done
I hope the above threads will be helpful.
As this community is aimed at Customers using Android Enterprise and you're a potential partner, I would recommend you contacting our Partner team directly at ae-community@google.com.
Many thanks and best of luck,
Emilie
Hey Emilie_B I tried applying for the partner program but got this response
We would like to let you know that your application to join the EMM Community has been declined.
On reviewing the information that you have submitted in your application, your organization does not meet the requirements to enter the community.
Best regards,
Android Enterprise community team
Hey rpnexa
I'm sorry to hear your application has been declined.
The Partner team (ae-community@google.com) is the only team that can provide you with more detail as to why your application was not successful so, if you haven't already, I suggest reaching out to them to know more.
Wishing you luck for what comes next!
Emilie
Have you filled out the form to request a quota? Here's the link:
https://developers.google.com/android/management/permissible-usage
This is separate from the partner application, so you may have more luck.We are getting the same rejection email. Any luck?
Hello rpnexa
I hope you're well!
I've checked with our tech team and they have confirmed that this is expected behaviour for new Google Cloud Projects and is not a technical bug in your code.
Google applies a default "Safety Quota" of zero for Device Owner enrolments on new, unverified projects to prevent abuse. This is why you see the error even with no devices enrolled.
Here's how to fix it:
Go to your Google Cloud Console > IAM & Admin > Quotas.
Filter for Android Management API.
Request an increase for the Enrolment or Device quota.I hope this is helpful; could you let us know if the fix provided helped?
Thanks in advance,
Emilie
Hello,
I'm trying to solve the same problem for 0 Devices on enrolment process;
why i can't find Enrolment or Device quota under Google Cloud Console > IAM & Admin > Quotas filtered by Android Management API?
Thanks,
Salvatore
