Share your deployment experiences with Android zero-touch enrollment
Hey everyone, In ‘5 Overlooked Benefits of Android Enterprise’, we touched on Android zero-touch enrollment, and it’s something many of you are actively using to streamline your device rollouts. For those in IT, Android zero-touch can be a powerful tool - see our handy guide to learn more. It’s about getting devices to your users ready to go, automatically enrolling in your EMM and pulling down all the right policies as soon as they connect. That means less hands-on time for your team and a smoother experience for end-users. We know real-world deployments always have their nuances, but it would be great to hear about your deployment experiences using zero-touch enrollment: Did you overcome any unexpected hurdles? What was the scale of your deployment - a few devices for new joiners, or hundreds for a company-wide refresh? If you could share one key tip or best practice for someone looking to nail their next zero-touch deployment, what would it be? We’re all here to learn from each other’s stories, and your insights are super valuable. I’m looking forward to reading your stories! Chat soon, Emilie
Request for Access to Android Enterprise Partner Portal Zero-touch Reseller Login
We are from Alphatech India and recently received a notification that our application to join the Carrier & Device Reseller Partner Program was declined. However, we would like to highlight that we are actively involved in large-scale deployments of Android-based mobile devices for enterprise customers across India. Access to the Android Enterprise Partner Portal, specifically the Zero-touch enrollment feature, is critical for us to streamline device provisioning and deliver a seamless experience to our clients. We request the community's guidance on how we can meet the eligibility requirements or explore any alternative process to gain access to the Zero-touch Reseller Portal. We are fully committed to meeting the necessary standards and are ready to provide any required documentation. Your support and direction on this matter would be greatly appreciated.
FYI - Chrome is dropping support for A8 and A9 in August 2025
138 will be the last version of Chrome that will support both A8 and A9 according to this recent announcement. https://support.google.com/chrome/thread/352616098/sunsetting-chrome-support-for-android-8-0-oreo-and-android-9-0-pie?hl=en There are very small populations of these devices left in the wild but I personally still support quite a number of them. The entire Atlas family from Zebra including the TC51, MC3300, and VC80x devices all max out on A8 with no higher upgrades available. This likely will lead to forced upgrades to those devices, especially given how many modern apps are hybrid web apps dependent on the WebView and/or Chrome (Chrome is the System WebView implementation on A8).
InTune Android connection "unexpected error"
Trying to follow this doc. We want to use InTune to control our corporate owned Android devices. https://learn.microsoft.com/en-us/intune/intune-service/enrollment/connect-intune-android-enterprise At step 7, it has me click "Launch Google to connect now" and I just get "Unexpected error. Please wait for some time and try again." Tried multiple browsers, incognito, multiple accounts, etc. All same results. We have a licensed Google Workspace tenant with Enterprise Standard licenses. The account has access to all Google apps/services. My account is both an Azure Global Admin and a Google Workspace Super Admin/Owner. Sat on chat with Workspace/Android Enterprise support trying all the obvious things for 3 hours with no resolution. They finally gave up and just said "call Microsoft" which doesn't help, it's literally an error thrown by enterprise.google.com. How do I get past this error to configure the connection? (This post was edited to remove personal information, in compliance with our guidelines)
OEM Unlock toggle not available
Hi all, Recently joined the community, first time poster here. TL;DR at the bottom. Hopefully my question has a simple solution but I've looked everywhere (except here of course). I'll try to keep this as simple as possible. Everything is in UAT if that matters. The important bits: Pixel 8a Build BP1A.250505.005.B1 No SIM or eSIM Android Enterprise registered to my UAT Tenant I'm testing some scenarios for automating device compliance with Omnissa using Workspace ONE Intelligence. To test this successfully I'm going to need to flash back to an older Build and probably more than once for demo purposes. The OEM Unlock toggle is not available however, and I this is preventing me from doing my testing. I've read conflicting posts elsewhere regarding carrier unlock, SIM and/or eSIM etc. ADB is working fine but flashing older images is just not working. Any help from the community on how to get OEM unlock enabled would be greatly appreciated. TL;DR: Need to flash a pre 250505 build to my Pixel 8a. Can't toggle OEM unlock as it's greyed out.
