This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(57.599999999999994, 9%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKT%3C/text%3E%3C/svg%3E)
Hello!
Our organization has enabled the MDM autoenrollment function when joining Azure AD (if a user in the group).
I connected the Windows mobile device to Azure AD, but the user was not in the group for auto enrollment and now he is joined to Azure AD, but the device is not added to the Intune.
Please tell me what are the ways to add this device to the Intune?
If its just one or a few devices, the simplest way is to manually turn on the local group policy referenced here :
If you have a lot of devices its a bit tricky but I wrote a blog post on how it can be done using a provisioning package:
Hope this helps,
@Timmy Andersson thanks for the answer.
in my case, there were few devices and it was easier to do it manually. screenshot in a separate comment
@Konstantin Terekhin From your description, my understanding is that this device has been added to Azure AD, but it hasn't enrolled in intune. If there is any problem with my understanding, please let me know.
To clarify our issue, could you check the following information:
However, if the above requirement are all met, we can go to Microsoft Endpoint Manager admin center->Troubleshooting+support, select the user and check if there’s enrollment failures .
Please check the above information and if there’s anything unclear, feel free to let us know.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
@Konstantin Terekhin I am currently standing by for further update from you and would like to know how things are going. If you have any questions or concerns on the recent information I've provided you, please don't hesitate to let me know.
@Lu Dai-MSFT thanks for the answer.
The root cause is that we use autoenrollment for a specific parameter (the presence of a user in a specific group), but some users were not in this group and were not enrolled.
added in settings (screenshot in comments)
@Konstantin Terekhin I am glad to hear that you have found the root cause. If you have any problem in the future, you can post in our Q&A.
Thanks for your posting and have a nice day.
Just made in manually in Settings