Android Enterprise Customer Community
Recently active
Hey everyone!Following our recent updates to the Solutions Directory, we want to make sure the browsing experience best supports how you and your team evaluate enterprise hardware.Plus, this is a great opportunity to highlight it as a resource for those of you currently unaware of its existence.Currently, devices default to sorting by recently added. We’d love to know whether that serves your workflow best, or if a different view would save you time?Please drop your vote below, and share any thoughts or suggestions in the comments you may have. We’d love to hear about any specific filters or sorting options that would make things easier. ⬇️Cheers,Kirk
This blog post says it's now generally available but I'm not seeing it live in my tenant yet: What’s new in Microsoft Intune – MayFor those that don't know, Microsoft has been using Company Portal as their custom DPC but is now transitioning to Google’s Device Policy app to get in line with Google’s mandates. This means (among other things), enrollment will happen at http://aka.ms/enrollymyandroid instead of through the Company Portal app.If they've rolled it out to your tenant, it will look like the first image in this other blog post when you go to Devices > Android > Enrollment > Personally-owned work profile.I am curious if this is live for anyone else. Methinks Microsoft has a weird interpretation of "generally available".
Hi All, One of our customers has a number of device deployed in Azerbaijan, these are deployed via WS1 and have a number of GMWA set as required. At the start of October they stopped being able to install any of the GMWA on new enrolments. When they attempt to manually download them from managed play they receive error - unavailable in your country These GMWAs have been working fine for over a year and continue to work on existing device however new enrolments are no longer able to download any GMWA. Is anyone experiencing a similar issue in Azerbaijan?@Google are you aware of any changes preventing GMWA in Azerbaijan? Thanks Tim
Hi everyone rolling out a big amount of A57 as a replacement for older A53 devices.We are facing issues that the COPE OOBE setup is failing on a large number of devices on the step “Updating device” after the user sign in. Users have to wait about 4-5 minutes on this screen and the result is an error message “Try again later”You can then either hit “Try again” or “Reset to factory”. Devices are shipped with Android 17, SMR September 2026. Any suggestions or other people facing this issue? Any idea of how to grab any protocol files during OOBE?
Hi,does anyone know if there's a possibility to place a feature request to Google regarding Zero-Touch-Portal?I wanted to ask if there's plaanned at any point to provide possibility to implement AD authentication to the portal.
Hi everyone,We have configured Microsoft Authenticator as a passkey provider on a personal Android device. However, when attempting to sign in to native Android apps such as Google Drive and Google Sheets, the Android system does not display Microsoft Authenticator as an available option for passkey authentication.Microsoft Authenticator is already configured as a passkey provider in the Android settings.Interestingly, this issue is limited to native Android apps. Passkey authentication through Microsoft Authenticator works as expected in:Web browsers on Android. Other third-party Android applications. Native apps on iOS devices.We have also contacted the Google Workspace support team, and they advised that the issue appears to be related to the Android operating system and falls outside their scope of support.Has anyone experienced a similar issue?Is there a known Android limitation or configuration that prevents native Android apps from accessing passkeys stored in Microsoft Authenti
Hi,We use the Android Management API to provision tablets in dedicated-device (kiosk) mode that ship with our product to customers. Since at least August 2026, new tablets fail to enroll with:"Since your organization reached its usage limits, this device can't be set up."Details:- Our enterprise has 982 enrolled devices (all in ACTIVE state) across 9 policies. We suspect a limit of about 1,000 devices but cannot confirm it.- In the Cloud Console, the API quota (600 requests per minute) is at 0% usage, so this looks like a device quota applied at the enterprise/project level.- We submitted the Android Enterprise quota request form (goo.gle/android-enterprise-response) around August 2026. We did not receive a reference number and have not received a response.- We deleted test policies and unenrolled test devices to try to free quota. This did not free any allocation, and enrollment still fails.Impact: we cannot provision new kiosk tablets, which blocks shipping to new customers and repl
Hello, On October 16, 2026, I submitted an initial quota request for a new Android Management API project through the Android Enterprise Response Form (goo.gle/android-enterprise-response). The Reason for Response was "Apply for initial quota on new AM API project code". The form says the review takes 14 business days. That period has passed, and as of November 9, 2026, I have not received any reply. I also did not receive an acknowledgement email when I submitted the form. Device enrollment is still blocked. Fully managed enrollment with a QR code fails with "Your organization has reached its usage limits." I retried on October 16, November 4 and November 9, with the same result each time. The Android Management API is enabled on the project, and I could not find a device quota entry in the Cloud Console. Could you tell me whether the request is still under review, or whether you need any additional information from us? I can share the project number and enterprise ID privately if tha
I manage our devices with Intune and I'm also the developer of the app, so I can see both ends of this.Our app (com.nikosoft.nikokeyboardpro) has shipped app_restrictions.xml in every production release since 22 September. No EMM offers a configuration section for it. In Intune the app config policy comes up with nothing to fill in.It isn't Intune. Querying Google directly, from a new enterprise that has never been bound to any EMM:GET /v1/enterprises/{enterprise}/applications/com.nikosoft.nikokeyboardpromanagedProperties isn't in the response at all. Chrome returns 243 properties, Edge 229, Outlook 47 and Teams 5 on the same call. Our record is current: updateTime 2026-10-24, appVersions showing only the latest release, recentChanges with that release's notes. So Play read the release and produced nothing from it.The schema isn't the cause. The build in production right now deliberately ships a cut-down version to test exactly that: three restrictions, two string and one bool, no choi
Hi everyone,I'm an independent developer working on an Android MDM project called OmniMDM.I can create enterprises and generate enrollment QR codes, but when I scan the QR code, I get an error saying my organization has reached its usage limit.I don't have a registered company or a D-U-N-S number.Is there any way for independent developers to get an initial device quota?Thanks!
We develop a custom DPC for organization-owned tablets used by Mexican municipal public safety agencies (fully managed, device owner via QR). On Samsung Galaxy Tab SM-X300 (Android 16, BP4A.251205.006) and SM-X133 (Android 16, October 2025 patch), QR provisioning downloads the DPC APK (HTTP 200), shows “Preparing your work space”, then fails with a generic “An error occurred / If you have questions, contact your IT admin” screen. There is no Play Protect or “App blocked” message.We isolated it on the same SM-X300:QR payload Result Google Test DPC (official download, official signature) Provisions fine Same Test DPC APK, only re-signed with a debug key An error occurred Minimal DPC (two provisioning activities, INTERNET only), our package and release key An error occurred Same minimal DPC, different package, debug key An error occurred Our production DPC An error occurred In every failing case the DPC never ran: a network beacon in Application.onCreate and in the provi
We're experiencing an intermittent issue with Managed App Configuration on Android Enterprise devices and are looking to understand whether others have seen similar behaviour.Environment:Android Enterprise Dedicated/Fully Managed devices Honeywell devices (CT32 and EDA series) MDM: Hexnode Application: UKG Pro Mobile App configuration deployed via Managed App Configuration through Android EnterpriseIssue:From time to time, and without any obvious trigger, the UKG application appears to lose its managed configuration (tenant URL and related settings). Users are then unable to access the application as expected.What we've observed:The device remains enrolled and managed. The policy is still present within Hexnode. Other device management functions continue to work normally. Re-syncing the policy from Hexnode immediately restores the configuration and resolves the issue.The behaviour appears random, and we have not yet been able to identify a clear pattern related to device model, Android
Hello,We are setting up private Android app distribution for our organization usingGoogle endpoint management. In the Google Admin console, Apps > Web and mobileapps > Add app only contains "Search apps" and "Add custom SAML app"."Add private Android app" is missing. The Settings menu only contains SAMLcertificates.Configuration checked on November 5, 2026:- Our primary corporate domain is verified.- Cloud Identity Free and Android Enterprise subscriptions are active, free plans.- Basic mobile management is selected.- The current corporate account is an assigned Super Admin for all organizational units. Its privileges include private app upload management for Managed Google Play and Mobile Device Management.- Google Play and Google Play Console services are ON for everyone.- Third-party Android mobile management is NOT enabled.- https://play.google.com/work/adminsettings displays our organization's name and ID.- No devices have been enrolled and no private app has yet been publ
We identified a reproducible issue affecting all users in our organization when using Gmail for Android with Exchange ActiveSync.EnvironmentGmail client: Android-Mail/2026.09.14.986636867.Release Android Enterprise Motorola Edge 50 Neo Motorola G71 Exchange Server Subscription Edition (latest updates) Ivanti EPMM 12.7.0.0 Ivanti Sentry 10.7.3Issue After device reboot or disable work profile:Existing Exchange contacts remain on device. Gmail starts a new ActiveSync contact synchronization. Another complete copy of the same contacts is created. Contact count continuously grows.Example:Initial sync: ~450 contactsAfter reboot #1: ~900 contactsAfter reboot #2: ~1350 contactsAfter reboot #3: ~1800 contacts Investigation resultsOutlook and Exchange mailbox do not contain duplicate contacts. Duplicates exist only on Android devices. Email and Calendar synchronization work correctly. Same DeviceId is used before and after reboot. Exchange returns HTTP 200 and successful ActiveSync responses. Ex
We use Microsoft Intune to manage devices. For the devices which have upgraded to Android 15, the end users can no longer select Microsoft Authenticator as their default application for auto filling passwords. I cannot find any settings in Intune to allow it. All devices are fully managed corporate owned devices. The devices are all Google Pixel 8 or 8a devices. Is this a bug in 15 or am I missing something?
I wanted to ask what are the plans for Googlebook Enterprise support. We build for the public sector and seeing the Android app support could be a strong avenue to see customers use our apps on their desktop devices. When is the timeline on that end?
Basic set up: Managed Google Play + Intune Devices all set up as "Corporate-owned, fully managed user devices" Policies are set to allow all apps from store and to allow other accounts to be installed on devices. GSuite individual Google accounts with corporate email addresses signed in to all devices to allow for things like Photos backup. Problem: When migrating a user to a new device, some apps cannot be installed. When a user is signed into Google Play with their Google Account, any app that is already linked to their Google Account from their previous device (for example: WhatsApp, Samsung Notes, Translate), cannot be installed with the error "Your administrator has not given you access to this item". If I sign the user out from their Google account, install the app and then sign them in again, it all works fine, but this should not be necessary. It seems like the problem is stemming from the Play Store not liking the fact that th
No text available
We're selling android phones and we want DLC Integration but the Already Appoved System Integrators ? Trustonic and Globetech is not responding ?
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!
Hello!Looking at the announced contacts changes, coming with 18, could the Android Enterprise team clarify the deployment path for enterprise contacts sync apps?My contacts app generator, like other enterprise directory tools, supports background synchronisation into a dedicated enterprise account. The intended deployment is straightforward: IT deploys and configures the app through EMM, grants the required permissions, and contacts become available without the user needing to configure anything.The announcement recognises enterprise background sync as a use case for MANAGE_CONTACTS, which is helpful. However, eligibility to use the permission and actually granting it on managed devices are two distinct steps, the latter unclarified.If users must manually enable access through Settings > Special app access, that introduces a dependency on user action into an otherwise unattended deployment. Even with Play approval, the directory cannot be populated until that step is completed.We al
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
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.