General discussions
Recently active
Hello, We are building a commercial EMM solution in the cybersecurity field. We’ve applied for the initial 500 quota for EMM enrollment, we have been approved and the message said a quota will be allocated in 3-5 working days, but that was over 6-7 working days ago. Is there something else we must do to get the quota enablement? We’re not in a hurry, but we’re worried that maybe there’s something we need to do and we’re not aware of it :)Another question, related to this, is: from what we’ve read in the documentation, it’s bad practice to enroll client’s devices in our own account and we should bind our EMM integration with their own Google accounts on a per-company basis and only enroll our company’s own devices directly in our account. We have a centralised console from where we manage security endpoints (currently only workstations and servers) on behalf of our customers so we’re still learning what is the correct way of providing EMM services for mobile devices.Thanks a lot!
Hi everyone,We are developing a dedicated kiosk attendance application that runs on company-owned tablets. We are using Android Enterprise QR code enrollment during the factory-reset out-of-the-box setup wizard to provision our app as a fully managed Device Owner (DO).What We Are Doing: We host our signed release APK on an HTTPS server and generate a standard Android Enterprise provisioning QR code with the following payload structure:{"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "com.ciphus.biometric/com.ciphus.attendance.receiver.AttendanceDeviceAdminReceiver","android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "https://our-domain.com/app_release.apk","android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM": "<URL_SAFE_BASE64_SHA256_WITHOUT_PADDING>","android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": true}Where the Failure Happens & Device Discrepancy: Xiaomi & Vivo Devices (Android 14/15): The QR enrollment succe
Hi AE Folks,Our Entra account configured in Intune as the Managed Google Play linked account has been disabled due to ToS violations and the appeal unsuccessful. I need some help untying this knot: why was the account disabled, how can we get it re-instated, how can we add a backup account to avoid this single point of failure, and how can we avoid this problem in the future?I read that we should open a ticket with our EMM: the Intune specialist I spoke to wasn’t aware of a backline Google Enterprise Support channel. Is there a specific group where I should route the ticket?Any and all help would be most appreciated.--BP
Hello Android Enterprise Community!I am a bit stuck.Currently, we have a fleet of 1000+ devices that have been enrolled as Fully managed Samsung devices within Microsoft Intune. We are in the process of offering Google Pixels (Zero touch) as alternative fully managed devices for our team members. Previously we have been able to migrate Samsung to Samsung (Fully Managed) with the help of Samsung’s Smart switch and the managed configurations available. I cannot currently offer a similar seamless service for users wanting to migrate from Samsung to Pixel. Due to the following reasons:Smart switch is not available for pixel devices Android switch both Wi-Fi and Cable (5 times press on screen) is blocked Either I'm unaware of how or Microsoft Intune doesn’t offer the newly released AMAPI: setBackupServiceEnabled()Has anyone been able to offer a migration or have any ideas of how I can handle this at scale, I'm actively trying to avoid the ol, sync everything individually, Thanks for any
I'm researching Google's official Factory Reset Protection (FRP) policies for lawfully acquired secondhand Android devices. Google's Android Management API documentation confirms that authorized enterprise administrators can manage FRP data on enrolled devices, including through supported device-wipe operations. However, my question concerns a different situation: a lawfully acquired secondhand Android device that is already FRP-locked and was never enrolled in enterprise management. I would appreciate clarification on three questions: 1. Does Google or an authorized device manufacturer provide an official process to review proof of purchase, an invoice, an IMEI, or a serial number for FRP resolution?2. If no such procedure exists, is the limitation technical, related to support or administrator authorization, or based on a manufacturer security policy?3. Is there published documentation or an official escalation channel addressing ownership verification when the previously associated
Hello,We are blocked at 0 devices and have received no response to our initial quota request for the Android Management API.Background:- We are a private security company in Ecuador, not an EMM vendor.- We built an internal device management console on top of AMAPI for our own corporate-owned phones assigned to security guards (around 340 devices).- Internal use only, no monetization, no third-party customers.Our integration works end to end: the enterprise is created, policies are published successfully and enrollment tokens are generated through the API. Enrollment fails on the first device with "your organization has reached its usage limits", since the project device quota is still 0.Timeline:- 28 September 2026: submitted the Android Enterprise Response Form, option "Apply for initial quota on new AM API project code", with full business justification, a valid DUNS number, company website and supporting screenshots.- No acknowledgment, approval, rejection or request for fu
Hi,We manage Android 14 devices (Grandstream GXV3480, Android Enterprise work-managed, enrolled in Workspace ONE UEM) behind a Palo Alto firewall with a URL allowlist.In our firewall logs, one device repeatedly requests http://www.google.cn/generate_204 (and https://www.google.cn), about 76 times in 4 hours, and the firewall blocks every attempt. At the same time, the other connectivity probes pass: https://www.google.com/generate_204, connectivitycheck.gstatic.com, and play.googleapis.com/generate_204.Google's Android Enterprise Network Requirements lists connectivitycheck.android.com, connectivitycheck.gstatic.com and www.google.com/generate_204 for the connectivity check. It does not mention google.cn anywhere.Questions1. Is www.google.cn (or *.google.cn) required to be reachable for Android Enterprise management, Google Play, Android Device Policy, or Google Play Services to work correctly?2. If it is not required, can the block be left in place without affecting policy enforcement
What is a Managed Google Domain? In Android Enterprise land, a Managed Google Domain refers to using a Google-managed organisation (like Cloud Identity or Google Workspace) to create and manage the connection to an EMM (the bind), it sits in contrast with Managed Google Play accounts, which uses a “personal” Gmail account to manage enterprise devices and apps. In practical terms, it means Android management is tied to an organisation’s work domain (e.g. @company.com), managed through the Google Admin console, rather than being tied to a single @gmail.com account. This approach unifies Android management with other Google services (Workspace, Chrome, etc.) under one organisational account, and is not only the default approach for all newly-binding organisations, but recommended by Google as an upgrade for all existing managed Google Play accounts enterprises due to the benefits it provides to IT admins and employees. Historically, organisa
Hi Team, Been banging my head against the wall for weeks trying to figure this out Does @Android have a hardware partnership program for manufacturers building Android XR audio glasses?Alternatively, can a manufacturer build audio-only smart glasses on AOSP and get Google’s approval for CDD compatibility and GMS licensing?Any pointers to the right team or documentation would be greatly appreciated!
I need someone willing to help me figure out what is going on with my devices I been hacked and pretty sure it's cause of emm
Hello everyone,I am developing a mobile application using React Native for Android, and I need to retrieve the device's IMEI number for device identification and management purposes.I understand that Android 10 and above restrict access to hardware identifiers such as IMEI and that normal applications cannot access them using the standard TelephonyManager APIs.However, I would like to understand whether this restriction can be addressed through Android Enterprise device management (MDM).My questions are: Device Owner / Fully Managed Devices: If our application is deployed on company-owned devices enrolled as fully managed devices through Android Enterprise, can it access the IMEI? Required Permissions: Is granting READ_PHONE_STATE sufficient for a properly configured Device Owner application, or are additional permissions or system-level privileges required? React Native Integration: Since the application is built using React Native, can we implement this functionality through a cu
We have a shared account we use just for the enterprise app store. we are a microsoft company so it is not a "work" account in the traditional sense that its a gsuite email. I have it logged in on a spare tablet, and I set up Google Authenticator and my cell as backups. We do not have to access often as we only need to when we need to add approved apps to the store. We use on handheld scanners in the stores, skorpio x5s. I tried to access this week on my computer I have used in the past. Google is saying it does not recognize the device, then wants me to hit the code on skorpio x5. I have no clue which one as we have 14 in each of our 6 locations. I tried to access on the tablet again, does not recognize the device. It never once has asked me for texted code, or for the authenticator. I went to one location and checked all the skorpio x5s, and not a single one was logged into a google account. We do have it connected to our sureMDM account to allow for selecting the approved apps. How
Hello Google Support Team,we are experiencing an issue with our Sauter GmbH Managed Google Play environment and would appreciate your assistance.Organization DetailsOrganization Name: Sauter GmbH Managed Google Play Organization ID: (**CM - updated to remove personal information) Issue DescriptionOur Managed Google Play organization is successfully connected to Microsoft Intune. The connector status is reported as successful and synchronization between Intune and Managed Google Play is working without errors. Existing approved applications remain visible and available within Intune. [learn.microsoft.com], [learn.microsoft.com]However, we are no longer able to approve new applications for our organization.SymptomsManaged Google Play connector status: Successful Synchronization status: Successful Previously approved applications are visible and functional New applications cannot be approved Accessing Welcome to the Android Enterprise and Chrome Customer Community | Community returns HTT
Hello everyone, we are in Education.We have a Google instance and an Intune instance.We have successfully managed Android devices in Intune, but they are not zero-touch.I understand we can leverage Google as the registrar, then push that device to Intune as the MDM?Is this possible?
Our corporate domain is locked by an unknown legacy Android Enterprise binding, and we need to free it to link to Microsoft Intune. We are unable to register and setup a managed google playstore binding in our new intune instance that we are now starting to leverage, as our company domain (bmc.com) is already in use. We know it was a previous IT employee who created the binding, but we have no way to break it / reregister with a new bmc email address (current one ends with .gmail). We found a support article that lead us here to “submit a support request”, but that does not appear to be an option, only posting discussions. Any assistance is greatly appreciated.
Since 19 Sep 2026, QR (6-tap) provisioning of Test DPC on a factory-reset device fails. After "Getting ready for work", Play Protect shows "App blocked to protect your device - Test DPC" with only an OK button, so provisioning cannot continue. The same flow worked before that date and nothing changed on our side.Setup: provisioning QR with PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME com.afwsamples.testdpc/com.afwsamples.testdpc.DeviceAdminReceiver, an HTTPS download location for the APK, and the signature checksum.APK: com.afwsamples.testdpc 9.0.12 (versionCode 9012), unmodified, signed by CN=testdpc, O=Google Inc. Signing certificate SHA-256: 8090f6630b4e8962479123249087cb4658feaae36a1b57dbeafd74d109b333dc. File SHA-256: aad38c1f608b1c7289405c4e866977f5d231502643ce2e2401a7c305808f9c00 (on VirusTotal, 1/67, a generic AdLibrary heuristic).I found the approved-DPC allowlist page (https://support.google.com/work/android/answer/16694822) and other threads about custom DPCs being blocked, but
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?
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 caseB2B device management for schools and educational institutions Institution-owned Android tablets Student devices managed as fully managed / dedicated devices Device Owner provisioning Applicat
've noticed that the OnePlus 13 is not included in the Android Enterprise Recommended (AER) devices list, which can be found here: https://androidenterprisepartners.withgoogle.com/devices/#!?search=Oneplus. Could someone provide insight into whether the OnePlus 10R will be added to the AER list in the near future? Your guidance would be greatly appreciated.
Hello,We use QR code provisioning to install our custom Device Policy Controller (DPC) app from a custom download URL (not Google Play).The exact same APK + QR configuration:Works on:Samsung Galaxy S20 — Android 13 / One UI 5.0Blocked on:Samsung Galaxy S21 — Android 14 / One UI 6.1Play Protect stops installation with the message:"App blocked to protect your device. This app can request access to sensitive data. This can increase the risk of identity theft or financial fraud."Provisioning QR:{"android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME": "<DeviceAdmin component>","android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_CHECKSUM": "<Package checksum>","android.app.extra.PROVISIONING_DEVICE_ADMIN_PACKAGE_DOWNLOAD_LOCATION": "<S3 bucket url>","android.app.extra.PROVISIONING_LOCALE": "en_US","android.app.extra.PROVISIONING_TIME_ZONE": "Europe/Helsinki","android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": false,"android.app.extra.PROVISIONING_DEVICE_A
Device: Honeywell EDA52 (Android 11/13, build TKQ1.230420.001)Browser: Reproduced on both Chrome (151.0.7922.139) and Microsoft Edge, same symptom on bothNot affected: Honeywell CT32 devices on the same network/site; EDA52 devices in other locations running the same MDM profileProblemOn a subset of our Android 11/13 handheld scanners, the browser randomly stops accepting any text input, both from the physical/on-screen keyboard and from an attached barcode scanner that injects input as keystrokes. This happens intermittently during normal use of a web-based app (not site-specific, happens on any input field in any website, including a plain Google search box).Symptoms when it occurs:Tapping a key on the on-screen keyboard shows the normal "key press" visual highlight, but no character appears in the field. A connected barcode scanner still fires (beep and aiming light activate normally), but again nothing populates the field. Copy/paste into the same field still works, so the field its
Hi all, We have a customer who is trying to enable a preloaded app on our tablet running Android 16 (basic notes taking app). The tablets are enrolled in Intune in COBO or COSU mode. The package name is correct and added in the app enablement list on Intune, but they see the app stuck on “pending install” state, while it works for other apps such as our camera app. We are unsure what’s causing this, does anyone experienced a similar case and has any advice please? Thanks!
I’m trying to determine whether the https://developers.google.com/android/management/reference/rest/v1/enterprises.policies#assistcontentpolicyis available for BYOD devices?I’m unable to determine what management types it’s available for, usually most settings state they are only available for Corporate Owned work profile devices or fully managed devices for example. I’m trying to get support from Microsoft (Who are insistent it’s not available for BYOD) to ensure this is available for BYOD devices as we currently have an issue where privileged apps (Assistant apps i.e. Gemini) can grab the screen content from a work profile device.Thanks for your help!
We have a google account where it broke our intune connection this week. We tried to unbind then rebind and we cannot because the domain already exists and the primary account was the only admin account. That account was removed as the only admin with out our knowledge. We cannot seem to get any support on this issue and this a last ditch effort for help. Please help us!!
Hi,We run a retail fleet of Android Enterprise dedicated (COSU) devices managed by Intune, with Entra shared device mode and no Managed Home Screen. Devices are Samsung Galaxy XCover6 Pro (SM-G736B), Android 15, build G736BXXSAFYJ3, enrolled via KME, with KSP Premium, KAI and E-FOTA. All our apps are on the KSP battery optimization allowlist.This is the same environment as these two earlier threads, but the symptoms this time are different, so I'm posting it separately:"Disabled apps" (Feb 2025): https://www.androidenterprise.community/android-enterprise-general-discussions-3/disabled-apps-1156 "Intune app disabled" (May 2026): https://www.androidenterprise.community/android-enterprise-general-discussions-3/intune-app-disabled-2570What happened this time (Aug 31, ~12:00 UTC+2, one device so far):Every Intune-managed app was disabled simultaneously: Intune app, Authenticator, Remote Help, Knox Remote Help, Knox Asset Intelligence, our POS app, our own settings app. Icons were greyed out
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.