Android 500 device limit on enrollment
What
Google's Permissible Usage page has updated from no explicit maximum number of devices per project (it was a soft 1000 prior, referenced below) to now topping out at 500 devices. In addition, the Android Enterprise features list (requirements) has additionally been updated from the prior 1000 devices to reflect the updated quota.
When/Why
In the past this quota was not automatically enforced, and the number of devices in the documented limit for an unverified AMAPI solution was 1000 although not ever seen to be enforced. FileWave is a validated partner however as you can see: https://androidenterprisepartners.withgoogle.com/provider/#!/5163783169245184 It was discovered on December 16, 2024 that there is a 500 device limit being enforced suddenly.
The AMAPI API now enforces this quota, which wasn't the case before. The addition of two new events returned to project administrators via a UsageLogEvent, which is a collection of various events logged on devices from the use of ADB to power on/off, external media mounting, and so on, suggest the API itself has the limits baked right in:
"MAX_DEVICES_REGISTRATION_QUOTA_WARNING",
"MAX_DEVICES_REGISTRATION_QUOTA_EXHAUSTED"
How
Despite the addition of these new, actively enforced quotas, it remains possible to request a higher limit on a case by case basis. Google now provide a form to - amongst other things - "respond to a quota limit":
You can get to the form here: https://goo.gle/android-enterprise-response and request that the limit be raised by Google as a short term solution. FileWave is investigating what the longer term solution is for this with Google. Google is aware that FileWave is a validated partner ( https://androidenterprisepartners.withgoogle.com/provider/#!/5163783169245184 ) so this issue appears on the surface to be an error on Google's part that they are enforcing a lower limit, but we are investigating.