AMAPI application rejected – looking for guidance on Android Enterprise EMM requirements

Hi everyone,

We are building Acadhub, an education-focused Android device management solution for schools and educational institutions.

Our current solution is a custom Android Device Owner / DPC-based MDM. We manage institution-owned student tablets and have built our own device-management backend and DPC.

We are now trying to move toward the Android Enterprise / AMAPI ecosystem so that our solution can integrate with Google's Android Enterprise management APIs and operate as an EMM solution.

We submitted an application for Android Enterprise / AMAPI access, but the application was rejected with the following reason:

“Business use case not compatible with permissible usage policies.”

We are trying to understand what specifically about our use case may not meet Google's requirements.

Our current use case

• B2B device management for schools and educational institutions
• Institution-owned Android tablets
• Student devices managed as fully managed / dedicated devices
• Device Owner provisioning
• Application installation and management
• Kiosk / dedicated-device management
• Device restrictions and policies
• Remote device management
• Backend-based device administration

We already have our own Custom DPC and MDM backend. However, we currently do not have Android Enterprise EMM / AMAPI access.

What we would like to understand

For people who have experience implementing Android Enterprise EMM solutions and going through the AMAPI onboarding process:

1. What are the minimum product and business requirements Google expects before granting AMAPI access?
2. Is an education/student-device management use case supported for an EMM provider?
3. Does having a working Custom DPC/MDM implementation help demonstrate the business use case, or are there other prerequisites we should have first?
4. Could the way we described our business use case in the application have caused this rejection?
5. What kind of documentation or information should be included in an AMAPI application to clearly demonstrate a legitimate EMM use case?
6. Are there specific Android Enterprise capabilities that we should implement before submitting another application?

Thank you.