Windows IoT Enrollment into Intune

%3CLINGO-SUB%20id%3D%22lingo-sub-369393%22%20slang%3D%22en-US%22%3EWindows%20IoT%20Enrollment%20into%20Intune%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369393%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20all%2C%20I%20could%20do%20with%20a%20little%20clarification%20from%20the%20community%20on%20how%2Fwhat%20to%20expect%20when%20enrolling%20a%20Windows%20IoT%20device%20into%20Intune.%20I%20have%20followed%20the%20steps%20on%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fiot-core%2Fmanage-your-device%2Fintunedeviceenrollment%23next-steps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fiot-core%2Fmanage-your-device%2Fintunedeviceenrollment%23next-steps%3C%2FA%3E%26nbsp%3Band%20I%20am%20seeing%20the%20device%20in%20question%20now%20as%20an%20AzureADJoined%20machine%20however%20I%20would%20have%20expected%20this%20device%20to%20come%20under%20the%20management%20of%20Intune%20and%20thus%20appearing%20in%20the%20devices%20console%20of%20the%20Intune%20blade.%20Am%20I%20being%20stupid%3F%20I%20notice%20a%20cloud%20based%20account%20gets%20created%20in%20AzureAD%20with%20a%20%22package_%22%20naming%20convention%20for%20every%20Windows%20IoT%20device%20I%20enroll%20(using%20a%20provisioning%20package)%2C%20I%20assigned%20that%20account%20an%20EMS%20E3%20license%20and%20I'm%20still%20not%20seeing%20the%20device%20as%20enrolled.%20Any%20thoughts%20or%20ideas%20would%20be%20appreciated.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-369393%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
Highlighted
Occasional Contributor

Hey all, I could do with a little clarification from the community on how/what to expect when enrolling a Windows IoT device into Intune. I have followed the steps on https://docs.microsoft.com/en-us/windows/iot-core/manage-your-device/intunedeviceenrollment#next-ste... and I am seeing the device in question now as an AzureADJoined machine however I would have expected this device to come under the management of Intune and thus appearing in the devices console of the Intune blade. Am I being stupid? I notice a cloud based account gets created in AzureAD with a "package_" naming convention for every Windows IoT device I enroll (using a provisioning package), I assigned that account an EMS E3 license and I'm still not seeing the device as enrolled. Any thoughts or ideas would be appreciated. 

0 Replies