Android Fully managed with work profile enrollment issue

%3CLINGO-SUB%20id%3D%22lingo-sub-1806660%22%20slang%3D%22en-US%22%3EAndroid%20Fully%20managed%20with%20work%20profile%20enrollment%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1806660%22%20slang%3D%22en-US%22%3E%3CP%3EAndroid%20Fully%20managed%20with%20work%20profile%20do%20not%20get%20enrolled%20in%20Intune%20as%20expected.%20The%20behavior%20started%20in%20the%20past%20couple%20of%20days%20when%20I%20tried%20creating%20a%20new%20Android%20corporate-owned%20fully%20managed%20devices%20with%20a%20work-profile%20after%20creating%20a%20new%20token.%20Using%20a%20QR%20code%20or%20entering%20a%20token%20manually%20enrolls%20the%20device%20in%20Intune%20but%20as%20Android%20fully%20managed%20instead%20of%20Android%20corporate-owned%20fully%20managed%20with%20a%20work-profile.%20Is%20this%20an%20expected%20behavior%3F%20If%20not%2C%20am%20I%20missing%20anything%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1806660%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Application%20Management%20(MAM)%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMobile%20Device%20Management%20(MDM)%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1810835%22%20slang%3D%22en-US%22%3ERe%3A%20Android%20Fully%20managed%20with%20work%20profile%20enrollment%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1810835%22%20slang%3D%22en-US%22%3EExpected.%20You%20need%20to%20create%20restriction%20rule%20(vice%20versa)%20in%20place%20and%20assign%20it%20to%20change%20the%20behavior.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20this%20helps!%3CBR%20%2F%3EMoe%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.inthecloud247.com%2Fhow-to-start-with-android-enterprise-corporate-owned-fully-managed-user-devices%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.inthecloud247.com%2Fhow-to-start-with-android-enterprise-corporate-owned-fully-managed-user-devices%2F%3C%2FA%3E%3C%2FLINGO-BODY%3E
New Contributor

Android Fully managed with work profile do not get enrolled in Intune as expected. The behavior started in the past couple of days when I tried creating a new Android corporate-owned fully managed devices with a work-profile after creating a new token. Using a QR code or entering a token manually enrolls the device in Intune but as Android fully managed instead of Android corporate-owned fully managed with a work-profile. Is this an expected behavior? If not, am I missing anything? 

2 Replies
Expected. You need to create restriction rule (vice versa) in place and assign it to change the behavior.

Hope this helps!
Moe

https://www.inthecloud247.com/how-to-start-with-android-enterprise-corporate-owned-fully-managed-use...

@Moe_Kinani Thank you for your suggestion. Since the device was an Android 11 device, scanning the QR code helped me enroll the device successfully. Not sure why entering the token manually doesn't work as expected for this enrollment method though.