Forum Discussion
MDM Scope enrollement : Users or device groupe ?
Oktay Sari, thanks for stepping in. Just a quick clarification (as you request the output of dsregcmd /status😞
I've already confirmed the device exists in Intune (I think 
). The device is visible in Azure AD and shows a "Manage" button and that button actually redirects to the device in Intune).
Zied_Berrima says he can can't find it when using the search and actually only sees two devices (and I assume he expects many more to be visible).
dear gentlemen, thank you for your reactivity and your answers.
Like any functionality in the Microsoft cloud world, it requires a wait of time for propagation, a huge latency which leads to doubt: maybe I on my side I misconfigured the thing 😞
you have to wait a time which could be up to 12 hours.
Today in the morning , I was able to see the devices in the intune portal.
Oktay Sari for the configuration profiles : imagine that you have devices in Azure AD ( Joined or hybride or registred) you can put them in a security group, so you can mention this group in the "assignement" step when you create a configuation profil.
Hi Zied_Berrima , good to hear things worked out eventually . Sounds like you had a huge delay in devices showing up in Intune. Thx for the update.
- what do you think about the configuration profil assignement for devices aren't enrolled to intune ? it seams weired but that's work fine ..
Hi Zied_Berrima, Did you had a chance to have a look at your configuration? There are some things that might apply to Windows 10 devices that are not enrolled with Intune, but the only thing I can think of is Windows Information Protection without enrollment. And yes, compliance policies (combined with conditional access) might hit unmanaged devices, requiring users to take action.
I'm curious to know what's causing the configuration assignment for unmanaged devices??
