SOLVED
Home

Effect on existing device when enabling Android Enterprise

%3CLINGO-SUB%20id%3D%22lingo-sub-579485%22%20slang%3D%22en-US%22%3EEffect%20on%20existing%20device%20when%20enabling%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-579485%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%2C%20we%20enrolled%20our%20corporate%20Android%20devices%20to%20Intune%20and%20created%20%22Android%20(platform)%22%20compliance%20policies%20and%20configuration%20profiles.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20would%20like%20to%20look%20at%20using%20Android%20Enterprise%20compliance%20policies%20and%20configuration%20profiles%2C%20by%20connecting%20to%20a%20managed%20Google%20account.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20guess%20is%20it%20should%20be%20okay%20but%20will%20that%20create%20any%20issues%20with%20devices%20which%20were%20enrolled%20on%20non-Android%20Enterprise%20profiles%2Fpolicies%20please%3F%20Will%20they%20require%20immediate%20re-enrollment%20please%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3CBR%20%2F%3E%3CBR%20%2F%3EEdmond.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-579485%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%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-614674%22%20slang%3D%22en-US%22%3ERe%3A%20Effect%20on%20existing%20device%20when%20enabling%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-614674%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F250007%22%20target%3D%22_blank%22%3E%40cake765%3C%2FA%3E%26nbsp%3Boverall%20it%20won't%20mess%20with%20existing%20devices%2C%20because%20you%20have%20to%20have%20separate%20profiles%20for%20Android(Device%20Admin%20or%20legacy%20model)%20and%20Android%20Enterprise.%20So%20it%20won't%20affect%20current%20devices.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsing%20Enrollment%20restrictions%20you%20can%20limit%20group%20of%20users%20who%20can%20enroll%20Android%20Enterprise%20devices%20and%20i%20do%20recommend%20to%20do%20that%20for%20proper%20testing%2Fpolicies%20creation%20prior%20to%20enabling%20that%20for%20everyone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJust%20be%20aware%20about%20one%20more%20thing%20(at%20least%20i%20saw%20that%20during%20my%20tests).%20If%20you%20have%20both%20Android%20and%20Android%20Enterprise%20enabled%20for%20user%2C%20all%20new%20enrollments%20will%20go%20through%20Android%20Enterprise.%20User%20has%20no%20option%20to%20choose%20the%20mode.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615422%22%20slang%3D%22en-US%22%3ERe%3A%20Effect%20on%20existing%20device%20when%20enabling%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615422%22%20slang%3D%22en-US%22%3ELike%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F144823%22%20target%3D%22_blank%22%3E%40Alexander%20Vanyurikhin%3C%2FA%3E%20says%20use%20groups%20to%20target%20enrollment%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20experienced%20one%20thing%20that%20is%20a%20pain%20for%20users.%20Devices%20enrolled%20with%20device%20admin%20and%20gets%20targeted%20with%20Android%20enterprise%20starts%20to%20enroll%20for%20enterprise.%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-621611%22%20slang%3D%22en-US%22%3ERe%3A%20Effect%20on%20existing%20device%20when%20enabling%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-621611%22%20slang%3D%22en-US%22%3EThanks%20so%20much%20Alexander.%20Appreciated.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-621612%22%20slang%3D%22en-US%22%3ERe%3A%20Effect%20on%20existing%20device%20when%20enabling%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-621612%22%20slang%3D%22en-US%22%3EThanks%20Anders%3C%2FLINGO-BODY%3E
cake765
Occasional Contributor

Hi there,

 

Currently, we enrolled our corporate Android devices to Intune and created "Android (platform)" compliance policies and configuration profiles. 

 

We would like to look at using Android Enterprise compliance policies and configuration profiles, by connecting to a managed Google account.

 

My guess is it should be okay but will that create any issues with devices which were enrolled on non-Android Enterprise profiles/policies please? Will they require immediate re-enrollment please?

 

Thanks,

Edmond.

4 Replies
Solution

@cake765 overall it won't mess with existing devices, because you have to have separate profiles for Android(Device Admin or legacy model) and Android Enterprise. So it won't affect current devices.

 

Using Enrollment restrictions you can limit group of users who can enroll Android Enterprise devices and i do recommend to do that for proper testing/policies creation prior to enabling that for everyone.

 

Just be aware about one more thing (at least i saw that during my tests). If you have both Android and Android Enterprise enabled for user, all new enrollments will go through Android Enterprise. User has no option to choose the mode.

Like @Alexander Vanyurikhin says use groups to target enrollment

I have experienced one thing that is a pain for users. Devices enrolled with device admin and gets targeted with Android enterprise starts to enroll for enterprise.
Highlighted
Thanks so much Alexander. Appreciated.
Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
30 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies