Android Enterprise General Discussions

Hello,I took over an IT department with numerous company owned phones.  The previous IT department did not use an MDM and did not keep track of login information for the phones.  They would create a new gmail account for each phone and allow the end user to create their own PIN.  I need to access these phones and put them on the MDM. Thank You, Jason

Hello everyone, did you encounter any issues with the switch to AMAPI through Intune ? Any devices running through AMAPI is not able to connect to our dedicated SSID through a configuration profile (certificate) We get an error from Intune’s report and nothing is applied on the device ! Sadly it was working before ! Thank you for your help Best Regards

Dear Team,While signing up in android enterprise partner portal got below error.Can you please help us ? how to resolve this. 

Hello,we would like to ask whether other customers using Samsung devices with Android 16 / One UI 8.5 have observed similar behavior. Environment- Samsung Galaxy tablets e.g. X816B- Android 16 / One UI 8.5- Android Enterprise (COPE) & Intune- Screen Pinning / App Pinning used for dedicated business applications After upgrading affected devices to One UI 8.5, notifications and certain system UI elements can appear while an application is pinned. In our environment, this behavior was not observed before the Android 16 / One UI 8.5 update and appears to be related to a change in the interaction between Screen Pinning and notification handling. This issue represents a significant operational risk for our environment. Prior to Android 16 / One UI 8.5, notifications were effectively suppressed while an application was running in Screen Pinning mode. Since the identified Android framework change, certain notifications can appear despite active Screen Pinning, impacting the intended behavi

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: Can a new EMM provider currently have its own custom DPC verified and added to the Android Enterprise approved/allowlisted DPCs? If yes, what is the current process for submitting a custom DPC for Android Enterprise verification and approval? Is there a separate registration or approval process for the custom DPC, or is

My Google Pixel is showing “This device is managed” and says Google LLC has configured this device to be fully managed. I am the current owner/user of the device and do not have access to the organization that enrolled it. The device is scheduled to automatically reset. How can I get this device removed from organization/zero-touch enrollment.

Hello,I'm trying to configure a corporate Wi-Fi network with certificate-based authentication.The connection works fine on an Android smartphone enrolled in Intune in COPE mode, but I can't get it to work on a smartphone enrolled in BYOD mode.I have a fleet of Samsung smartphones, both COPE and BYOD.The certificate is installed on the BYOD smartphones via an Intune PKCS profile, and I followed the recommendations (user-type certificate, Subject name = CN={{UserPrincipalName}}, and adding the SAN: User principal name (UPN) = {{UserPrincipalName}}, I published the CA that issued the certificate).The certificate is correctly installed on the BYOD smartphone and visible in the work profile, but the Wi-Fi connection fails.When I check the Wi-Fi configuration on the BYOD smartphone, there's no client certificate, which can explain the connection failure.Has anyone successfully configured a corporate Wi-Fi network with certificate authentication on a smartphone enrolled in BYOD mode on Intune

Hi Google TeamMy name is Fernando from Kueski Pay. We're currently expanding our mobile phone financing business in MexicoIn the past, we used Android DPC for device management. Recently, Springdel approached us with a solution based on the Android Management APIBefore moving forward, we’d like to confirm whether their implementation complies with Google’s policies and licensing requirements for our use case.Thanks in advance for your supportBest regardsFernandoKueski Pay

I keep getting this error while trying to register, I had ae-community@google.com, but I got a reply saying “Thank you for your interest. Unfortunately, we don't provide specific feedback or details regarding application decisions.”.  I need guidance as to what the next steps are? Is there any issue with my DUNS number?

i got stuck with one situation and need your guidance in solving it. We have our own .apk file for android devices, these are custom in-house developed applications, i want to deploy the application to Android Fully Managed devices (Since the device belongs to company). I did it before with publishing them to google play store as a private app but now the size is the problem as it exceed 200MB, so i cannot use this option. I tried with deploying them as Line of Business application but its been 2 days nothing shows on device and even in intune portal it neither failed or success.  Question: How to deploy your custom .apk files to android fully managed devices if the file size se more than 200MB?

Hi everyone,I need assistance regarding access to the Google Zero-Touch Portal for our organization.The Issue: When attempting to sign in at [partner.android.com/zerotouch](https://partner.android.com/zerotouch), I consistently receive the following error message: 403 - The account doesn't have permission to see this pageCurrent Setup & Troubleshooting Completed: Google Account: A standard Google Account has been created and verified using our custom company domain email address. Reseller Assignment: Our reseller (A1) confirmed that our Customer ID has been set up and that our business email address was added as an Administrator in their reseller portal. Isolation Testing: Login attempts were conducted using an Incognito / Private browser window to eliminate multi-account session conflicts or caching issues. Reseller Feedback: The reseller states that all configurations on their end are correct and that they cannot troubleshoot account or permission issues further within the Go

Allow my device to install other apps and allowed to access Bluetooth 

Hello everyone,We recently hosted a session on Android Desktop Windowing for our CAFÉ & Insiders members! It was fantastic to hear directly from you about how your organizations are approaching connected display experiences.If you weren't able to attend (or are not currently part of either of these groups), please see the brief overview below. If you're interested in reading the full recap please join Insiders and let us know that you would like to be part of this project (or comment below). Existing Desktop insiders members can view the extended recap here.   What We Talked About:During the session, the Desktop Windowing team discussed the evolution of Android's connected display experience following its official General Availability launch in the Q1 2026 Android release. They went over the four product focus areas for their team, some upcoming features and areas of exploration for future versions of desktop mode. What We Heard:We got great feedback during the live Q&A session

Hi,I had requested for increasing device quota of my Android EMM account. I had filled in the google form under developers.google.com/android/management/permissible-usage#quotas_and_restrictions. Was expecting a response in 14 business days, but even after 20 days there is no response. I do I reach out to the right team for help? Soumik

Hi,Is it possible to use a DPC for the following use case:The DaaS provider leases managed devices to the Business Customer (BC) The BC uses devices for their business purposes (for example, gives managed tablets to their field employees) and pays monthly fee for leasing managed devices If a BC stops paying, the DPC installed by the DaaS provider locks devices and requires to payI have reviewed the DPC permissible usage policy and it looks like it restricts Device Financing solutions for B2C/Retail scenarios.Can you please clarify whether Device-As-a-Service (which may include device financing for B2B) is an officially permitted DPC use case?

Hello,I hope you’re doing well.I would like to know how we can obtain Android Zero-touch reseller status.I couldn’t find any companies in my country (Kazakhstan) that are able to register devices in Android Zero-touch.Could you please let me know if it is possible for our company to become an authorized reseller so that we can register devices ourselves?Thank you in advance for your assistance.

Hey, I’m trying to better understand this AMAPI release (May 2026), we currently have issues with our corporate owned personally enabled devices where if a users personal gmail account is added to the personal profile of the device if the device is reset via recovery mode the users pin / personal gmail account is required.We started using EFRP admin emails to bypass this so we could get back into our own devices, we’re a large organisation so users generally don’t reset devices before handing them back or hand them back to their manager who is unaware of our process.What I’d like to understand is what the below change did as after testing this it still seems to be the same that when setting the FRP admin emails setting to be not configured a recovery mode wipe still triggers consumer FRP.AMAPI improves Factory Reset Protection (FRP) policy handling on COPE devices by explicitly disabling FRP and clearing account lists when no admin emails are configured, preventing unexpected lockouts

Hello Android Enterprise Community Team,We are developing an enterprise Device Policy Controller (DPC) application for managing company-owned devices via Android Enterprise dedicated device management.Issue Summary:- Our DPC app is hosted on our secure HTTPS enterprise server and provisioned via standard 6-tap QR code onboarding on factory-reset devices.- During provisioning, Google Play Protect blocks the application with the message: "App blocked to protect your device".- The DPC app is strictly used for enterprise device management (Device Owner mode, kiosk enforcement, remote lock/unlock, system restrictions) and does NOT harvest sensitive personal user data (contacts, call logs, SMS, and media are completely disabled).Actions Taken:1. We have verified our DPC APK package name, manifest provisioning activities, and public signing certificate SHA-256 checksums match the QR code bundle contract.2. We have submitted the official Google Play Protect Appeal Form (under Android Enterpris

Hi all, hope you’re well. I was wondering are there any ways to add devices to Google ZTE (Zero-Touch Enrollment) if the vendor can't / refused to do it? Q. Why do the vendor refused to do it?A. Some vendors like Officeworks in Australia does not appear in the Google ZTE resellers list. Q. Why don’t you tell the vendor they need to do the right thing / register with Google?A. Good luck with that……(thank you for your feedback, you won’t hear back from us anytime soon……) We also have other none Samsung Android devices purchased from retailers that’s not in the Google ZTE reseller list. With Samsung devices, we use KME (Knox Mobile Enrolment) and it works well. But for non-Samsung devices, we don’t have many options as far as I know. I’m happy to be proven wrong though 😂 Q. Have you tried to ask other vendors (in the reseller list) to add the device to Google ZTE for you?A. Yes I  have tried and it does work, but we don’t want to do this as it’s not their responsibility. Q. Maybe you sho

Hi there,I'm a new developer building an EMM solution on the Android Management API, currently in early integration/testing.Environment:- Android Management API enabled, billing active- New service account created with Android Management User role- New Android Enterprise created via signupUrls/enterprises.create (Gmail-based, not Workspace)- Policy created successfully- Enrollment token and QR code generated successfully with no errorsIssue:When scanning the enrollment QR code on a physical test device (Samsung Galaxy A10e, Android 11), provisioning fails immediately with:"Can't set up device. Since your organization reached its usage limits, this device can't be set up."The device never appears in the Android Management API device list — inventory remains empty. I have zero enrolled devices currently, so this appears to be the known default "Safety Quota" of zero applied to new/unverified projects rather than an actual usage limit being hit.I don't see this quota exposed under IAM &am

Hello, WhenI’m trying to add an Admin to the reseller protal of Zero Touch I’m getting an error message“Unexpected error occurs, please retry later”.Can someone help us in this?  Many thanks 

Hello Team, We have checked in various post available in Android Community. It seems we are not able to enroll devices because of initial quota is 0.We have filled and submitted the form to increase or lift the safety quota. Its been 15 days since, we don’t have any feedback and not able to enroll device. What to do in this scenario? Whom to contact to grant us initial quota?

Hi everyone, I’m trying to enroll a fully managed Android device using the Android Management API. I generate an enrollment token, create the QR code, factory reset the device, and start the QR-based provisioning process. Everything works until the Android Device Policy step, where I get the following error: “Since your organization has reached its usage limits, this device can’t be set up.” I am unable to get past this point. Here is what I have already checked:Listing devices through the API returns an empty list. There are no enrolled devices at all.Billing is active on the cloud project and the Android Management API is enabled.Enterprise creation works, policies return correctly, and I can generate enrollment tokens without any issues.The device is correctly factory reset and the QR scan is working as expected.I tested with both a Workspace-based enterprise and a Gmail-based enterprise. The same limit error appears on both, even though both enterprises have zer

Hi everyone,I submitted a quota request over two weeks ago via the Google Form (link: https://docs.google.com/forms/d/e/1FAIpQLSf4VCzblf27V6jx1_iFt7lD1WjyCDpSDzQcxunTbQdbkEGG4Q/viewform). Submission Date: 2026/07/06 However, the request is still pending approval, and I haven't received any update yet.Could someone please help check: Whether my request was submitted successfully. The estimated timeline or current status for the approval process. Any guidance or advice on how to follow up would be greatly appreciated.Thanks in advance!

Hi Community Team,I am facing an issue where my website (*Link hidden) is not opening properly on the Google Chrome browser (specifically on mobile devices/Android Enterprise managed devices). The site either fails to load completely, shows a connection error, or displays layout breaking issues, whereas it seems to work differently on some other networks or browsers. Could this be related to Chrome's built-in security settings (like HTTPS/SSL enforcement), Android WebView updates, or regional DNS blocking? Please guide me on how to troubleshoot this so that our users can access the website smoothly on Chrome without any errors. Thank you!