![]() ![]() to dig deeper I opened my impacted device and checked the Company Portal app, it was reporting not being Registered even though my device was already in Intune. Sync the device and note the change in Azure AD device listĪlthough this scenario applies to new devices it should have similarities to the existing devices, I just checked my test tenant and in there I did have a device that reported a similar state, where in Azure AD I had a N/A compliance and in Intune it was ok.After enrolment make sure that you do not get a notification under your Devices menu.If the device isn't already managed, enrol it into Intune.The potential fix may vary depending on the exact scenario (and there are more I am sure): ![]() From Azure AD > Devices, you can see a device without Compliance.Sign into the Company Portal app but do not enrol.Install Company Portal on mobile device.So to first recreate the N/A state for a device you can do the following with a new device: Read more about the Device Identity here and about Azure AD registered devices here. My take utilises credentials but the logic itself should be similar to unaffiliated devices. ![]() First Azure AD displays more states for devices than Intune and comes into play before even getting your devices enrolled - that can be the N/A state that you guys are reporting. Ok, I think I get the core of the issue now and here is my humble hunch on it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |