Unanswered questions

Hi all,I'm running a self-hosted Fleet MDM instance for personal/homelab use and I'm trying to enroll my own Android phone using a work profile. I've hit the "your organization has reached its usage limits" error during enrollment, despite having zero devices enrolled.Setup details:- Created a brand new Managed Google Play Accounts Enterprise via the "Sign up for Android only" path- Enterprise was created successfully- Enrollment token generated successfully- 0 devices currently enrolled- Enrollment proceeds normally — gets all the way through the work profile setup and hangs on "Updating phone" — then fails with "Your device can't be set up because your organization has exceeded its usage limits"  My use case is purely personal — I'm a hobbyist running Fleet MDM at home to manage my own devices, not building a commercial EMM product.   Is there any way to get this quota lifted for a single personal device? Is the AE Compliance team the right contact, and if so, how do I reach them?Tha

Does Cameyo support applications that are in the Microsoft MSIX format?

Hello Android Enterprise Community,​I am looking for some guidance regarding app publication for our organization. We have developed a custom/line-of-business (LOB) Android app that we need to deploy internally to our managed devices, but I want to make sure we follow the proper procedures.​Could anyone share the recommended workflow or best practices for this? Specifically:​Is it better to publish the private app directly through our EMM console (using the Managed Google Play iframe) or via the standard Google Play Console? ​What are the key things to keep in mind regarding Organization IDs to ensure only our targeted devices can see and download the app? ​How long does the initial publishing/approval process typically take for enterprise private apps?​For context, we are currently using [Insert your EMM provider here, e.g., Microsoft Intune, VMware Workspace ONE, Ivanti] to manage our fleet.​Any advice, documentation links, or tips from your own deployment experiences would be highly

Hello,We implemented an EMM solution using the Android Management API prior to 2024 and were able to successfully test it in our staging environment.As we are now preparing for a production deployment in 2026, we attempted to create a new EMM enrollment token/EMM instance but encountered a "device quota exceeded" message.We are unsure about the current quota policies, and the process for obtaining additional quota or creating a new EMM instance for production use. Could anyone please advise on the next steps or point us to the appropriate documentation or support channel?Any guidance would be greatly appreciated. Thank you in advance.

Hi there,is there any way to distribute Paid Apps in Micrsoft Intune through Managed Google Play Store. It really sucks having the “Buy” Button disabled since there is no alternative App to use. I have also not found any workaround. Is there something I’m missing?  

Hi everyone,We are currently facing many difficulties setting up managed Google accounts using the AMAPI library with our Custom DPC.At the beginning, we were doing everything from a single Activity: calling prepareEnvironment() and then starting the managed Google account setup flow. However, we encountered many reliability issues with this approach.We then changed the implementation to use a chain of Workers: one Worker calls prepareEnvironment(); another Worker starts an Activity responsible for performing the account setup. Each Worker can retry up to 3 times when needed. This improved the success rate, but we still have many failures with different types of errors.The most frequent one is:ApiException: 13Most of the time, this one eventually succeeds after the Worker retries.However, depending on the device, and sometimes randomly on the same device, we also get other errors, such as: AndroidDevicePolicyInstallOrUpdateUnrecoverableException SecurityException — this one happens

I have a batch of chromebooks that an organization donated to my robotics team. The organization is still operating, but they had an enterprise set up for these chromebooks, and they were locked to that enterprise. The enterprise no longer exists (they aren't paying for it). I have complete permission to repurpose these chromebooks, but neither us nor the donor has any idea how to remove the lock on that organization! We can't even log in because it requires a login domain that no longer exists. How can we deprovision these chromebooks? I've tried the "Super Powerwash", including disconnecting the battery and discharging the system. Nothing has worked, it keeps coming up with a requirement to log in with a defunct account. Any pointers to who we might contact at google, I have full cooperation from the actual owners of these devices! Maybe there is a way to temporarily reactivate the enterprise to decommission them?

Hello,we are currently adding EMM functionality to our system, and I wanted to test it first with our own devices. So I requested the initial quota (<500 devices) via the form, but I omitted the fact that we do plan to offer this feature as a paid service in the future.So the current situation is that our application has been denied, and I wanted to ask what the correct way to reapply would be - since the reply said "this decision is final". We already have most of the code ready for testing, but of course I can’t :(Does anybody know how to proceed further the right way? kind regardsStefan

"I am trying to set up Android Management API (AMAPI) for enterprise device management. My organization uses Google Workspace (G Suite). The managed Google Play signup flow at enterprise.google.com/signup rejects G Suite accounts. How can I create an AMAPI enterprise using my Google Workspace domain without a personal Gmail account? 

Hey! We recently noticed that a banner is displayed on https://play.google.com/work/apps . According to this, /work will be terminated on April 15. I am aware that the page is generally somewhat outdated and is intended for deprecated EMM APIs. (e.g. https://developers.google.com/android/work/play/emm-api/v1/products/approve ) /work has always been useful for us when it comes to getting a first impression of an app. By replacing /store with /work in the store URL, you could see immediately whether the app was available for Managed Play and offered an AppConfig.https://play.google.com/store/apps/details?id=com.google.android.apps.tachyonhttps://play.google.com/work/apps/details?id=com.google.android.apps.tachyon Will the pages be discontinued without replacement, or is there an alternative? (I mean, yes, you can see everything in the iFrame, but the hurdle for /work was very low and therefore very practical).

Hi Chrome Community,I am facing a technical issue where a specific website (https://cloudstream.pk) is failing to open or load correctly on the Google Chrome browser. The site either encounters a continuous loading loop, or the layout breaks completely upon opening, whereas it seems to work fine on alternative browsers. I have already tried clearing the Chrome browser cache and cookies, and also checked in Incognito mode, but the issue persists. Could this be related to Chrome's recent security updates regarding SSL/HTTPS enforcement or JavaScript handling? Please suggest what browser settings or site configurations I should look into to resolve this compatibility issue on Chrome.Thank you!

Hi Community Team,I am facing an issue where my website (https://cloudstream.pk) 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!

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

So I have been going round and round in circles trying to understand how the Helper App works and triggers for End Point Verification and official documentation aswell as Gemini seem to say that in order for the Helper App to trigger a prompt for an end user to install it, you first need a rule in place that requires the visibility of signals only the helper app can see. I have been trying AV requirements in  rules etc but nothing seems to trigger the Helper installation. For context, this is required for BYOD extensions and so deploying the app is not possible. 

Helloi try to upgrade our intune<>google Android Enterprise Connection from a unmanaged gmail account to an entra account (https://techcommunity.microsoft.com/blog/intunecustomersuccess/new-onboarding-flow-to-managing-android-enterprise-devices-with-microsoft-intune/4206602)Unfortunally i get this error screen at the end of the wizard: Any idea whats going wrong here? Microsoft support cant help, since its a google issue. they told me to ask here for help. can someone assist here?Thanksvt

For the Work profile on company owned device mode, when I used iccid to delete esim, my device refused due to permission issues. Is there any solution

We report the version numbers of certain apps on managed devices. I've noticed an unusual update pattern with some apps for some time now.Although we use a payload for Managed Google Play to automatically update public apps, and the affected devices are actively in use, some apps are still running old versions. Updates for some apps simply aren't being performed. The adoption rate for current versions then continues to decline over time. The cause seems to be an Android feature. Unused apps are disabled after a certain amount of time. For example, on Samsung devices, the affected apps are listed under "Deep sleeping apps" in the device's battery settings. In the app settings and in the Play Store, the apps are shown as disabled. It seems that Deep Sleep is preventing updates in Managed Google Play. The affected apps must be launched or enabled manually. In general, I think it’s fine to save device resources by turning off unused apps. But in an enterprise environment, we do want to mai

Hello,I am integrating Android Management API (AMAPI) for dedicated kiosk devices and I am currently blocked during device enrollment.EnvironmentNew Google Cloud project Android Management API enabled Billing enabled and linked to the project New service account New Android Enterprise created EMM successfully linked in Google Workspace Admin Enrollment tokens successfully created through the API Enterprise accessible through API (HTTP 200)Observed behaviorEnrollment token is generated successfully. QR code provisioning starts correctly. During provisioning, Android displays the following error:Can't set up device. Since your organization reached its usage limits, this device can't be set up.The device never appears in Android Management API. Device inventory always remains empty. No policy is attached to the enrollment token. The issue occurs on multiple devices from different manufacturers.DiagnosticsEnterprise accessible: YES Enrollment token creation: YES Access token generation: YE

Hello everyone,I’m currently trying to onboard a Zebra CC6000 device into our Android Enterprise environment, but I’ve run into an issue.When attempting to add the device using the serial number in the portal, the CC6000 model is not available for selection. Because of this, I’m unable to register or assign the device properly via SN-based enrollment.From what I understand, Zebra devices can typically be enrolled using different methods (e.g., QR code / enrollment token or staging tools like StageNow for dedicated devices), but in this case I’m specifically trying to use serial number-based onboarding.Could you please advise:Is the Zebra CC6000 officially supported for serial number (SN) enrollment? Are there any limitations for kiosk-type / dedicated devices like this model? What would be the recommended onboarding method in this scenario? Would it be correct (or supported) to register the device under a different/similar model in the portal?Any guidance or best practices would be gre

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

As far as we have been able to determine Microsoft is not providing APK files of its applications to customers. We have a need to manage MS Edge on some devices located in China and therefore cannot use the Google Play Store or associated MDM tooling. We want to distribute the APK instead as a side-loaded app. Is there a APK provide (APK Mirror or other) that is considered ‘trustworthy’ and/or are people aware of a way to get a trusted APK of MS Edge for distribution via a MDM? 

hi allWe already have purchased these handsets from a Phone reseller.NOT a google zero touch / enterprise partner.is there any way we can get them onto GZT?please help 

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

I know that some new Google Play Console accounts are able to publish apps without completing the testing requirement. However, I don't know exactly how they are doing it. I would like to understand the process and the conditions under which a new Play Console account can publish an app directly to production without going through the testing phase. in individual account

I am using Android Management API to build my own device management system. I am not an Android partner, but I integrated Android Management API into my platform.I successfully enrolled a device, and on the device side it shows as enrolled correctly. Also, in the enrollment history/logs, I can see that the device enrollment was successful.However, the problem is that the device does not appear in the active devices list/system dashboard after enrollment.So currently: The device shows as enrolled on the physical device Enrollment history/logs show successful enrollment But the device is missing from the active/managed devices list Could you please help me understand why this happens and how to resolve it?