Forum Discussion
Get the Intune enrolled devices synced into Azure Active Directory and show up as devices
When you sync your devices from ABM, it will only provision Managed Devices in Intune.
A Managed Device in Intune does not necessarily require a Device in Azure AD (and vice versa). They are only loosely related entities. Managed Devices can exist just fine without any connection to a Device registered in Azure AD (joining would, of course, work as well, but that's not possible for iPhones) .
If you need these devices to be available in Azure AD, you will have to register them in a separate action during your enrollment, like deploying Company Portal or Microsoft Authenticator, as Moe_Kinani already mentions.
The devices were enrolled with a enrollement profil (with user affinity) directly at device setup, not simply assign to a MDM from ASM/ABM.
Users have the correct MS licenses.
Fiew days after, the devices simply desaperead from AAD.
The Intune device must have a related AAD object to be able to be grouped. That's all the problem.
We manage more then 2000 (Win, Mac, iOS, Android) enrolled devices with MEM and only the Apple devices seem to have this issue.
Not sure I'm completely clear on how you are enrolling your devices. So, this is probably a long shot...
I'm assuming you are using ADE/Setup assistant-method here. Are you completely finishing the setup, as in, you are following it up with Company Portal?
I'm asking because Company Portal is where the AAD-registration is actually completed, as described under "Setup Assistant with modern authentication" in https://docs.microsoft.com/en-us/mem/intune/enrollment/device-enrollment-program-enroll-ios#create-an-apple-enrollment-profile
- We use Company Portal.
LuckySlam did you manage to resolve this issue ? we are facing the same problem with apple devices. the devices show up as complaint on company portal app and endpoint portal. we registered devices under Microsoft Authenticator app , which updated registered status on Azure AD. but compliance is not synced between Endpoint Manager and Azure AD , hence devices fail with CA policies.
