This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 0%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHB%3C/text%3E%3C/svg%3E)
Hello, I have a problem when trying to enroll in intune with a fully managed profile on the Redmi Note 14 PRO.
My procedure that I follow and it works for other devices except Xiaomi with HyperOS:
Using 6 taps on screen to enroll Scanning QR code Logging in with microsoft account Then it shows <Setting up device> for a few seconds and jumps back into account selection screen. It shows my account as logged in, I can press on it again, it shows <Setting up device> for a few seconds again and jumps back to account selection screen again. And its stuck on this loop.
I tried, starting the device normally, without google account, and manually updating to the latest available update, and resetting it from factory to try again, but the problem is still the same.
Anyone experienced this before and managed to solve?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 25%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMA%3C/text%3E%3C/svg%3E)
Hi, this is a platform limitation, not a tenant bug. HyperOS is not yet certified for Android Enterprise, so devices like Redmi Note 14 and 14 Pro are not in the Android Enterprise Recommended directory. As a result, Intune cannot complete Device Owner provisioning, causing the usual "Pick an account" loop. Microsoft has confirmed there’s no fix expected before 60-90 days. For now, you can either use MAM-only or BYOD work profiles (which don’t require Device Owner), delay the purchase and choose AER-certified devices, escalate to Xiaomi/Google for AER inclusion (long process), or simply wait for broader compatibility, likely in summer 2025. Until then, fully managed enrollment won’t work on HyperOS, so the only viable option is to stay with work profile or MAM-only modes.