Forum Discussion

keyurmaru's avatar
keyurmaru
Level 1.5: Cupcake
2 months ago
Solved

How to view and remove enrolled devices, and how quotas are applied

We are developing a solution using Android Management.   While enrolling a fully managed device, provisioning now fails with: - "Can't set up device" - "Since your organization reached its usage ...
Devices
EMM
Enrolment
fully managed
Management
  • Emilie_B's avatar
    Emilie_B
    2 months ago

    Hi again keyurmaru​!

     

    I've just heard back from the team - they said that this error is caused by a quota limit on the Android Management API (AMAPI), and it is enforced per Google Cloud project.

    By default, all new Google Cloud projects using the Android Management API are given a "default" quota, which is currently set at 500 devices. It’s possible that the other two Google Cloud projects using the Android Management API, have been granted full production-level quota, so they continue to work.


    To unblock your immediate testing, you may remove old unused devices, they will free up slots allowing you to enrol new devices.


    To resolve the issue in the long term, you simply need to request a production-level quota for your new, affected project. This is a standard procedure for all developers building solutions on AMAPI.

     

    Here you can find more information regarding permissible usage:
    https://developers.google.com/android/management/permissible-usage

     

    And here you may find the form to apply to Android Enterprise and request quota increase and/or the removal of restrictions: https://goo.gle/android-enterprise-response 


    You will need to provide a business justification for the increase so the team can verify your use case. Once your request is reviewed and approved, the device limit will be lifted from your project, and your enrolments will be good to go again.

     

    I hope that this is helpful :) 

    Let us know how you get on,

     

    Emilie

  • Emilie_B's avatar
    Emilie_B
    Google Community Manager
    2 months ago

    Thanks for your help jeremy​ 🙂

     

    keyurmaru​ I'll see if I can get additional info from our team and will keep you posted as soon as I hear back! 

    • Emilie_B's avatar
      Emilie_B
      Google Community Manager
      2 months ago

      Hi again keyurmaru​!

       

      I've just heard back from the team - they said that this error is caused by a quota limit on the Android Management API (AMAPI), and it is enforced per Google Cloud project.

      By default, all new Google Cloud projects using the Android Management API are given a "default" quota, which is currently set at 500 devices. It’s possible that the other two Google Cloud projects using the Android Management API, have been granted full production-level quota, so they continue to work.


      To unblock your immediate testing, you may remove old unused devices, they will free up slots allowing you to enrol new devices.


      To resolve the issue in the long term, you simply need to request a production-level quota for your new, affected project. This is a standard procedure for all developers building solutions on AMAPI.

       

      Here you can find more information regarding permissible usage:
      https://developers.google.com/android/management/permissible-usage

       

      And here you may find the form to apply to Android Enterprise and request quota increase and/or the removal of restrictions: https://goo.gle/android-enterprise-response 


      You will need to provide a business justification for the increase so the team can verify your use case. Once your request is reviewed and approved, the device limit will be lifted from your project, and your enrolments will be good to go again.

       

      I hope that this is helpful :) 

      Let us know how you get on,

       

      Emilie