Zero-touch
42 TopicsNeed Help with QR Enrollment for Multiple Devices in Educational Environment – Is External MDM Required?
Hi everyone, I'm managing a large number of Android tablets in an educational environment. I'm trying to enroll the devices using Android Enterprise with QR code enrollment, but I'm having trouble getting the QR method to appear. So far, only Zero-Touch shows as an option, but most of our devices were not purchased through Zero-Touch resellers, so we can't use that method. My main question is: Is it strictly necessary to use an external MDM (like Miradore, Intune, etc.) to generate the QR code, or is there a way to create and use it directly from the Google Admin console or natively through Android Enterprise? We want to deploy the tablets efficiently and avoid entering accounts manually. Ideally, each device would automatically enroll with our managed Google Play account by scanning a QR code after a factory reset. This is especially important in a school context, where we have many students and limited time for configuration. We are already registered in Google Workspace, and the tablets are in a dedicated organizational unit for students. The admin account is managed, and we are using the Android Enterprise platform linked to our domain. For reference, here are two YouTube videos showing the configuration steps I followed (which reflect our current setup): https://www.youtube.com/watch?v=jI-C_y1u8jE https://www.youtube.com/watch?v=h__pvfp559Q Any advice or clarification would be greatly appreciated. Especially if there’s a native way to enable QR enrollment without needing a full external MDM platform. Thanks in advance!15Views0likes0CommentsZero Touch Portal - Error Message
Hi Team, I have created a new configuration item and linked it to Microsoft Intune token. Then I have decided to remove the Intune token configuration before removing the configuration file from Zero touch (which I dont think it should matter). Then I went to remove the configuration item from Zero touch and was getting a strange error message, see below. Now I'm left with a configuration item in Zero touch that I can't remove. Can someone please help or reach out, that would be great. Also, let me know if there is anything else you require from my end.46Views0likes5CommentsDefault configuration not apply
Hello, We're having trouble assigning the default configuration when resellers add phones to our Zero-Touch account. We've successfully linked Intune to the Zero-Touch account. In Intune, there is a fully managed profile. I used this token to create a profile that works, no problem. However, when resellers add new devices, they don't retrieve our default configuration, which is called PROD_INTUNE_FullyManaged, but retrieve a default profile that we haven't configured. It's quite annoying to have to systematically reassign the correct default profile. Thank you for your help on this issue. *Post updated 27 May, 2025 - translated from French to English75Views0likes5CommentsMigration from Airwatch to Android Management API
One of our customers is currently onboarded to Airwatch to manage their devices, but they want to move to our Android Management API (AMA) based device management solution. Is there any support available to silently migrate these devices? Or is the only way to wipe the devices and onboard AMA. I see there is support if we own the custom DPC application. But in this case since its owned by Airwatch its out of our control.68Views0likes2CommentsRequest to become Zero-Touch Reseller – Option not available in Partner Portal
I'm currently registered in the Android Enterprise Partner Portal (https://www.androidenterprise.dev/s/) and would like to apply to become a Zero-Touch Reseller. However, I am not seeing any option or link in the portal to start the Zero-Touch Reseller application process. Could someone please advise on the correct steps or prerequisites for enabling this feature? Is there a specific approval or account level required before this option becomes available? Thanks in advance for your help!30Views0likes1CommentWhat happned if the device used for personal usage although it is in zero touch portal and emm bind? Is it illigal based on google policy?
I have some customer who uses my EMM console integrated with Zero touch services. Some of his previous used device added in zero touch portal but not activate the device as enterprise device that means not enroll in emm portal. Rather using the devices as personal.Is it violate the google zero touch policy?Solved61Views0likes5CommentsZero Touch Customer API Feature Request
{written in Gemini ;) who literally wrote this out perfectly} I'm requesting an enhancement to the Android Device Provisioning API (Zero Touch) to include filtering capabilities, specifically the ability to filter devices by serial number (and other relevant fields) in the initial API call. Current Situation: Currently, the API lacks direct filtering. As demonstrated in the code below, to find a device by its serial number, we must: Make a call to list all devices for a customer. Iterate through the entire list of devices in the response to find the specific device. Iterate through any following pages if not found on the first page. This is inefficient, especially for customers with a large number of provisioned devices. const listDevicesUrl = `https://androidprovisioning.googleapis.com/v1/customers/${customerId}/devices`; // ... const listResponse = await fetch(listDevicesUrl, { ... }); const listData = await listResponse.json(); let foundDevice = null; if (listData && listData.devices) { foundDevice = listData.devices.find(device => device.deviceMetadata && device.deviceMetadata.serialNumber === serialNumber); } Desired Feature: I propose adding a filter parameter to the device listing API, allowing us to directly query for devices based on specific criteria, such as serial number, manufacturer, model, and IMEI. For example, the API call could look like this: https://androidprovisioning.googleapis.com/v1/customers/{customerId}/devices?filter=serialNumber={serialNumber} This would significantly improve the efficiency of device management and reduce the amount of data that needs to be transferred and processed. Benefits: Improved Efficiency: Reduces the number of API calls and the amount of data transferred. Faster Processing: Speeds up device identification and management operations. Reduced Load: Decreases the load on Google's API servers and client applications. Simplified Development: Makes it easier for developers to integrate with the API. I believe that adding filtering capabilities to the Android Device Provisioning API would be a valuable improvement and would greatly benefit the Android Enterprise community. Thank you for considering our request.18Views0likes0CommentsHi, I try to enroll an andorid 12 aosp (raw and also with a shell, two versions). currently during provision, it is always stuck with the intune client screen(fetching intune authentic information) after scan QR code(generated for userless enrollment). MS is also help troubleshooting but it seems the broadcasting command was consumed somewhere and no trace on my device side(which they said it is weird). Anyone has experience with aosp Intune side can help? With compensation.
86Views0likes2CommentsEmergency: My zero touch customer account is terminated and I am not able to unclaim or reassign my devices.
Hello team, Right now i am in a huge trouble as my zero touch account is terminated and i am not able to unclaim the registered devices. Android enterprises team had sent us the mail on 27th of feb 2025 and they mentioned about the termination of zt customer account will be effective from 12th of may 2025. But they did not mention that the imei number will not be unclaimed after that. Kindly help me in this regard. Because the reseller account is also being terminated with this. So we have nothing to unclaim the devices. Kindly help us to recover our customer account as we are in trouble.65Views0likes1CommentSetup using another device wizard screen removal
Is there a way to skip the "setup using another device" wizard screen? We don't see the benefit of showing up this option, on company environment, having MDM managed devices with Zero touch enrollment setup. That screen is specifically, the 3rd screen, when setting up a new device, after selecting the language and the insert SIM card instrucctions screens. As those screens are right before the Network setup screen the device won't be able to connect with Google services to get MDM server and the custom profile, so not sure how to disable it? ThanksSolved72Views0likes5Comments