problematic re-enrollment following smartphone reset under Android 15

Hey Chris,

I'm not a Google rep, just sharing based on experience, but it looks like you're hitting an issue related to how Android 15 handles factory reset and re-enrollment timing for fully managed devices.

From what you've described, it seems that after the reset, the Zero Touch or KME profile isn't kicking in before setup finishes, causing the device to default to personal setup instead of enforcing corporate enrollment via Intune.

A few thoughts:

• This issue may be tied to Android 15's tightened factory reset protection or setup flow changes, especially around managed provisioning.
• Double-check if the Zero Touch or KME profiles are still correctly assigned to the device IMEIs after reset. Sometimes they get unassigned if a factory reset is triggered unexpectedly.
• You might try reapplying the Intune profile in KME/Zero Touch before re-enrollment and make sure the device is connected to a network with unrestricted internet access at the very beginning of the setup.
• Also, check with Omnissa (formerly Workspace ONE) to confirm if Android 15 introduced a change that affects the COBO to Intune transition path.

You're right, this shouldn't be happening on a fully managed fleet. I’d recommend reporting this to both Google and the EMM providers (Intune and Omnissa) to escalate further. Android 15 is still new in some environments, and this might be a regression or provisioning timing issue.

Hope this helps point you in the right direction. Good luck with the migration.