Azure AD Bulk Enrollment of Devices

Question

Hello everyone,

I was just experimenting some feature of enrollment of windows 10 devices. In particular, the ability to join multiple devices to Azure AD using the windows configuration designer to create a provisioning package to do the work for me.

I've noticed that when the job is done, the provisioning process create automatically an Azure AD user to which is assigned the device just enrolled. Here's an example (edit: I can't add images since i'mnew to this forum and my account isn't verified)

I can't find any references about that so i've decided to ask here in the forum to see if anyone have noticed the same thing and have some suggestion to avoid this behavior

Thank you all for the answers,

Sincerely,

Raffaele

Answer 1

anonymous user, For the Bulk enrollment for Windows devices by creating a provisioning package with the Windows Configuration Designer (WCD) app, the join type will be Azure AD joined and the owner is like package_xxxxxx. Under Intune portal, the Primary user is none for this device, Here is the result in my lab. This is by design.

Device in Azure AD.

Device in Intune

Fro this device, we can login with any Azure AD account in our environment. If this is not we want, we can consider other enrollment method. Here is the link for the reference:
https://learn.microsoft.com/en-us/mem/intune/enrollment/device-enrollment#windows-enrollment-methods

Hope it can help.

---

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.

Answer 2

Is there a reason for wanting to use a provisioning package? Have you looked at Autopilot to join to Azure AD and either use user-driven or self-driven profiles?