Android Enterprise 500-Device Enrollment Quota
ThisCurrent articlestatus: willGoogle bestill updateddocuments asa we500-device findquota outfor morestandard information.Android AsManagement ofAPI nowprojects. thisFileWave issuehas isan resolved.established support path for customers who reach it. Open a FileWave Technical Support case before changing your Android Enterprise enrollment configuration. Last updated:reviewed: AprilJuly 11,23, 20252026.
What
Google's Android Management API Permissible Usage pageguidance hasrequires updateda frombusiness nojustification explicitfor maximuman numberinitial quota of devices per project (it was a soft 1000 prior, referenced below)up to now topping out at 500 devices.devices Inand addition,an theAndroid Enterprise request to exceed 500. The Android Enterprise featuresfeature list (requirements)requirements hasalso additionallyreference beenthis updatedquota.
When the priorquota 1000affects devicesenrollment
This reflectmatters thewhen updatednew Android Enterprise enrollments fail as a project approaches its 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 isfirst aobserved validatedunexpected partner500-device however as you can see: https://androidenterprisepartners.withgoogle.com/provider/#!/5163783169245184 It was discoveredenforcement on December 16, 20242024. that thereFileWave is an Android Enterprise validated partner, but a 500project devicestill limitneeds beingan enforcedapproved suddenly.quota increase to exceed Google's documented limit.
The AMAPIAndroid Management API nowcan enforcesreport thisthat quota,a whichproject wasn'tis approaching or has reached the caselimit before.through The addition of two new events returned to project administrators via athese 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:values:
"MAX_DEVICES_REGISTRATION_QUOTA_WARNING",
"MAX_DEVICES_REGISTRATION_QUOTA_EXHAUSTED"
HowWhat to do
DespiteIf theenrollment additionis ofblocked thesenear new,500 activelydevices enforcedor 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 aeither quota limit":
Updatedappears, Dec 18, 2024: You can createopen a support case with CustomerFileWave Technical Support. Include the approximate Android device count, the time of the failed enrollment, and thenany wequota willevent askor Googleerror toshown. adjustFileWave can confirm the limit.cause FileWaveand is investigating whatcoordinate the longerquota term solution is for thisrequest with Google.
Google isalso awareprovides thatan Android Enterprise response form for quota-limit requests. FileWave iscustomers ashould validatedstart partnerwith (Technical https://androidenterprisepartners.withgoogle.com/provider/#!/5163783169245184 )Support so thisthe issuerequest appearscan onbe tied to the surfacecorrect toFileWave beproject anand errorenrollment on Google's part that they are enforcing a lower limit, but we are investigating.context.
UpdatedFileWave Aprilsupport 11,status: 2025:FileWave Weestablished havea metworkaround and escalation route with Google andin haveApril both2025. The public 500-device quota still exists, so "resolved" means FileWave has a workaroundpath into placehandle asaffected wellcustomer as an open line of communication. This shouldprojects, not bethat anGoogle issueremoved movingthe forward. quota.