Home
%3CLINGO-SUB%20id%3D%22lingo-sub-575002%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20Using%20Corporate%20Device%20Identifiers%20for%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-575002%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone%2C%20today%20we%20have%20a%20post%20from%20Intune%20Support%20Escalation%20Engineer%20%3CSTRONG%3EMatt%20Butcher%3C%2FSTRONG%3E.%20In%20this%20post%2C%20Matt%20talks%20about%20the%20use%20of%20corporate%20device%20identifiers%20and%20how%20they%20can%20be%20used%20to%20control%20the%20enrollment%20of%20your%20Android%20Enterprise%20devices.%20If%20you%E2%80%99re%20tasked%20with%20managing%20Android%20devices%2C%20you%E2%80%99ll%20want%20to%20give%20this%20one%20a%20quick%20read.%E2%80%AF%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3D%3D%3D%3D%3D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20way%20you%20use%20corporate%20device%20identifiers%20is%20going%20to%20vary%20based%20on%20device%20type%20and%20the%20scenarios%20you%20have%20in%20your%20environment.%20We%20get%20a%20number%20of%20questions%20from%20customers%20on%20this%20topic%2C%20and%20we%20understand%20it%20can%20be%20tricky%20as%20there%E2%80%99s%20device%20admin%20(legacy)%2C%20Android%20Enterprise%2C%20fully%20managed%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FIntune-Customer-Success%2FMicrosoft-Intune-announces-Preview-2-for-Android-Enterprise%2Fba-p%2F472324%22%20target%3D%22_blank%22%3Ein%20Preview%202%3C%2FA%3E)%2C%20and%20dedicated.%20A%20good%20overview%20of%20Android%20device%20management%20is%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FEnterprise-Mobility-Security%2FHow-does-Microsoft-Intune-transform-Android-enterprise%2Fba-p%2F299289%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FEnterprise-Mobility-Security%2FHow-does-Microsoft-Intune-transform-Android-enterprise%2Fba-p%2F299289%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%3CSTRONG%3E%3CFONT%20size%3D%224%22%3EWhat%20are%20Corporate%20Device%20Identifiers%20for%3F%3C%2FFONT%3E%3C%2FSTRONG%3E%3CBR%20%2F%3E%3C%2FSPAN%3EWhen%20people%20ask%20about%20corporate%20device%20identifiers%2C%20they%20typically%20want%20to%20block%20personal%20devices%20and%20only%20allow%20corporate%20devices%20into%20their%20environment.%20In%20this%20scenario%2C%20we%20can%20use%20corporate%20device%20identifiers%20we%20can%20predeclare%20(whitelist)%20devices%20based%20on%20either%20IMEI%20or%20serial%20number%2C%20so%20that%20if%20a%20user%20with%20an%20Intune%20license%20attempts%20to%20enroll%20their%20personal%20(BYOD)%20device%20they%20will%20be%20blocked.%20However%2C%20if%20that%20same%20user%20attempts%20enrollment%20of%20a%20device%20that%20has%20had%20its%20serial%20number%20or%20IMEI%20predeclared%20using%20the%20corporate%20device%20identifiers%20feature%20in%20Intune%2C%20it%20will%20successfully%20enroll%20and%20be%20marked%20as%20a%20corporate%20device.%20You%20can%20read%20more%20about%20this%20feature%20here%3A%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fcorporate-identifiers-add%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fcorporate-identifiers-add%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%224%22%3EHow%20does%20this%20work%20for%20the%20various%20Android%20scenarios%3F%3C%2FFONT%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EFor%20the%20Device%20Admin%20(legacy)%20scenario%2C%20this%20is%20a%20perfectly%20suitable%20way%20to%20prevent%20personal%20devices%20from%20enrolling%20into%20the%20Intune%20service%2C%20however%20for%20Android%20Enterprise%20there%20are%20a%20few%20other%20considerations%20to%20take%20into%20account.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAndroid%20Work%20Profile%20is%20intended%20for%20personal%20devices%20enrollments%20as%20management%20is%20only%20achieved%20within%20the%20work%20profile.%26nbsp%3B%20The%20Personal%20side%20of%20the%20device%20remains%20personal.%26nbsp%3B%20IT%20admins%20and%20the%20Intune%20service%20only%20are%20granted%20authority%20over%20the%20Work%20Profile%20by%20the%20Android%20OS.%26nbsp%3B%20With%20this%20method%2C%20there%20are%20intended%20management%20limitations%20and%20that%20may%20be%20new%20to%20IT%20admins%2C%20most%20notably%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ENo%20factory%20reset%3C%2FLI%3E%0A%3CLI%3ENo%20application%20inventory%20from%20personal%20profile%3C%2FLI%3E%0A%3CLI%3ENo%20device%20level%20passcode%20reset%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EIf%20your%20scenario%20includes%20corporate%20issued%20devices%20that%20are%20intended%20to%20be%20used%20as%20%3CU%3Eboth%3C%2FU%3E%20a%20personal%20device%20to%20access%20social%20media%2C%20for%20personal%20calling%20and%20texting%2C%20etc.%2C%20but%20also%20for%20accessing%20company%20resources%20like%20email%20and%20Office%20365%2C%20then%20using%20corporate%20device%20identifiers%20to%20only%20allow%20these%20devices%20to%20enroll%20via%20Android%20Enterprise%20Work%20Profile%20is%20a%20recommended%20solution.%20If%2C%20however%2C%20the%20scenario%20is%20that%20the%26nbsp%3Bcorporate%20issued%20devices%20are%20meant%20only%20%E2%80%9Cfor%20work%2C%20at%20work%E2%80%9D%20then%20it%20is%20not%20recommended%20to%20use%20Android%20Work%20Profile%20due%20to%20the%20limitations%20mentioned%20above%2C%20and%20instead%20we%20would%20recommend%20using%20either%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fandroid-kiosk-enroll%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EDedicated%20%3C%2FA%3Eor%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fintune%2Fandroid-fully-managed-enroll%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EFully%20Managed%3C%2FA%3E.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%224%22%3ESo%20how%20does%20a%20Corporate%20Device%20Identifier%20impact%20the%20device%20owner%20scenarios%20of%20Dedicated%20and%20Fully%20Managed%3F%3C%2FFONT%3E%3C%2FSTRONG%3E%3CBR%20%2F%3EThe%20short%20answer%20is%20it%20doesn%E2%80%99t%2C%20for%20two%20main%20reasons.%20First%2C%20the%20device%20owner%20scenarios%20are%20automatically%20marked%20as%20corporate%2C%20so%20predeclaring%20these%20devices%20will%20not%20be%20necessary.%20Second%2C%20corporate%20device%20identifiers%20are%20only%20evaluated%20on%20Android%20scenarios%20when%20the%20Company%20Portal%20App%20is%20used%20for%20enrollment%20using%20Work%20Profiles%20or%20Device%20Admin%20(Legacy).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3E%3CFONT%20size%3D%224%22%3EWhat%20is%20this%20Android%20Enterprise%3F%3C%2FFONT%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EAndroid%20Enterprise%20is%20Google%E2%80%99s%20methods%20of%20modern%20management%20of%20Android%20devices%20that%20started%20with%20Android%205%20(Lollipop)%20and%20in%20future%20releases%20will%20be%20the%20only%20method%20of%20management%20as%20share%20in%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FEnterprise-Mobility-Security%2FHow-does-Microsoft-Intune-transform-Android-enterprise%2Fba-p%2F299289%22%20target%3D%22_blank%22%3Ehere%3C%2FA%3E%3A%3C%2FP%3E%0A%3CP%3E%E2%80%9CMicrosoft%20supports%20the%20Google%20recommendation%20that%20all%20partners%20and%20customers%20move%20off%20of%20device%20admin%26nbsp%3Bmanagement%2C%20since%20Google%20has%20announced%20that%20they%20will%20be%20removing%20device%20admin%20capabilities%20in%20the%20near%20future.%E2%80%9D%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EMatt%20Butcher%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EIntune%20Support%20Escalation%20Engineer%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3EMicrosoft%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-575002%22%20slang%3D%22en-US%22%3E%3CP%3EIntune%20Support%20Escalation%20Engineer%20Matt%20Butcher%20talks%20about%20using%20corporate%20device%20IDs%20to%20control%20enrollment%20of%20Android%20Enterprise%20devices.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-576278%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Using%20Corporate%20Device%20Identifiers%20for%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-576278%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Matt.%20Great%20stuff.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-666751%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Using%20Corporate%20Device%20Identifiers%20for%20Android%20Enterprise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-666751%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGood%20article.%26nbsp%3B%20However%2C%20I%20have%20one%20quick%20question.%26nbsp%3B%20We%20are%20currently%20trialing%20the%20the%20'%3CSPAN%3ECorporate-owned%2C%20fully%20managed%20user%20devices%20(Preview)'%20part%20of%20Intune%20and%20we%20would%20like%20to%20only%20allow%20corporately%20issued%20devices%20to%20be%20fully%20enrolled.%26nbsp%3B%20I%20was%20hoping%20to%20use%20the%20'Corporately%26nbsp%3Bdevice%20identifiers'%20feature%20to%20enforce%26nbsp%3Bthis%26nbsp%3Bbut%20after%20speaking%20to%20Microsoft%20and%20reading%20this%20article%20this%20it%20would%20seem%20this%20will%20not%20be%20possible.%26nbsp%3B%20%26nbsp%3BCurrently%20our%20work%20around%20is%20only%20approved%26nbsp%3Badmins%20can%20enrol%20devices%20but%20going%20forward%20we%20would%20like%20to%20offer%20a%20'self-service'%20style%20enrolment%26nbsp%3Boption%20for%20our%20end%20users.%26nbsp%3B%20In%20other%20words%20the%20phone%20gets%20sent%20out%20directly%20from%20our%20mobile%20provide%20and%20then%20the%20users%20follows%20some%20basic%20instructions%20to%20enrol%20their%20corporately%26nbsp%3Bissued%20device.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

Hello everyone, today we have a post from Intune Support Escalation Engineer Matt Butcher. In this post, Matt talks about the use of corporate device identifiers and how they can be used to control the enrollment of your Android Enterprise devices. If you’re tasked with managing Android devices, you’ll want to give this one a quick read. 

 

=====

 

The way you use corporate device identifiers is going to vary based on device type and the scenarios you have in your environment. We get a number of questions from customers on this topic, and we understand it can be tricky as there’s device admin (legacy), Android Enterprise, fully managed (in Preview 2), and dedicated. A good overview of Android device management is here: https://techcommunity.microsoft.com/t5/Enterprise-Mobility-Security/How-does-Microsoft-Intune-transf....

 

What are Corporate Device Identifiers for?
When people ask about corporate device identifiers, they typically want to block personal devices and only allow corporate devices into their environment. In this scenario, we can use corporate device identifiers we can predeclare (whitelist) devices based on either IMEI or serial number, so that if a user with an Intune license attempts to enroll their personal (BYOD) device they will be blocked. However, if that same user attempts enrollment of a device that has had its serial number or IMEI predeclared using the corporate device identifiers feature in Intune, it will successfully enroll and be marked as a corporate device. You can read more about this feature here: https://docs.microsoft.com/en-us/intune/corporate-identifiers-add.

 

How does this work for the various Android scenarios?
For the Device Admin (legacy) scenario, this is a perfectly suitable way to prevent personal devices from enrolling into the Intune service, however for Android Enterprise there are a few other considerations to take into account.

 

Android Work Profile is intended for personal devices enrollments as management is only achieved within the work profile.  The Personal side of the device remains personal.  IT admins and the Intune service only are granted authority over the Work Profile by the Android OS.  With this method, there are intended management limitations and that may be new to IT admins, most notably:

  • No factory reset
  • No application inventory from personal profile
  • No device level passcode reset

If your scenario includes corporate issued devices that are intended to be used as both a personal device to access social media, for personal calling and texting, etc., but also for accessing company resources like email and Office 365, then using corporate device identifiers to only allow these devices to enroll via Android Enterprise Work Profile is a recommended solution. If, however, the scenario is that the corporate issued devices are meant only “for work, at work” then it is not recommended to use Android Work Profile due to the limitations mentioned above, and instead we would recommend using either Dedicated or Fully Managed.

So how does a Corporate Device Identifier impact the device owner scenarios of Dedicated and Fully Managed?
The short answer is it doesn’t, for two main reasons. First, the device owner scenarios are automatically marked as corporate, so predeclaring these devices will not be necessary. Second, corporate device identifiers are only evaluated on Android scenarios when the Company Portal App is used for enrollment using Work Profiles or Device Admin (Legacy).

 

What is this Android Enterprise?

Android Enterprise is Google’s methods of modern management of Android devices that started with Android 5 (Lollipop) and in future releases will be the only method of management as share in here:

“Microsoft supports the Google recommendation that all partners and customers move off of device admin management, since Google has announced that they will be removing device admin capabilities in the near future.”

 

Matt Butcher

Intune Support Escalation Engineer

Microsoft

 

 

 

2 Comments
Microsoft

Thanks Matt. Great stuff. 

Occasional Visitor

Hi,

 

Good article.  However, I have one quick question.  We are currently trialing the the 'Corporate-owned, fully managed user devices (Preview)' part of Intune and we would like to only allow corporately issued devices to be fully enrolled.  I was hoping to use the 'Corporately device identifiers' feature to enforce this but after speaking to Microsoft and reading this article this it would seem this will not be possible.   Currently our work around is only approved admins can enrol devices but going forward we would like to offer a 'self-service' style enrolment option for our end users.  In other words the phone gets sent out directly from our mobile provide and then the users follows some basic instructions to enrol their corporately issued device.