Custom DPC Approval for a New Android Enterprise EMM

Hello Android Enterprise team,

We are currently developing our own Enterprise Mobility Management (EMM) solution for Android devices.

Our company develops and provides Android devices, and we are working on our own EMM platform, including an EMM console/backend and a Device Policy Controller (DPC) application.

We are currently integrating the Android Management API (AMAPI) and understand that Android Device Policy is the standard DPC approach for new EMM solutions.

However, we also have our own custom DPC application and would like to understand whether there is still a supported path for getting our custom DPC verified/approved by Android Enterprise.

Our questions are:

1. Can a new EMM provider currently have its own custom DPC verified and added to the Android Enterprise approved/allowlisted DPCs?

2. If yes, what is the current process for submitting a custom DPC for Android Enterprise verification and approval?

3. Is there a separate registration or approval process for the custom DPC, or is this handled as part of the EMM/Android Enterprise registration?

4. Can an approved custom DPC be used for fully managed company-owned devices through provisioning methods such as QR code and Zero-touch enrollment?

5. The current Zero-touch documentation mentions selecting an EMM DPC during configuration. If our custom DPC is approved, would it be possible for it to appear as the EMM DPC for our EMM?

6. For a new EMM, is it possible to support both:

   • Android Device Policy through AMAPI as the standard/default management path, and

   • our own approved custom DPC as an additional/advanced management option?

7. Are there any specific technical, security, Play Protect, or application requirements that our custom DPC must satisfy before it can be submitted for verification?

8. If custom DPC approval is still available for new EMM providers, could you please point us to the current official documentation or application process?

We are not trying to use the old Google Play EMM API registration path. We are specifically looking for the current supported process for a new EMM provider that wants to develop and obtain approval for its own DPC.

Any guidance on the correct current process would be greatly appreciated.

Thank you.