Azure AD Bulk Enrollment of Devices

Question

Azure AD Bulk Enrollment of Devices

Raffaele Piccolo 26

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

Accepted answer

1 additional answer

Your answer

Answer 1

Crystal-MSFT 53,986 Microsoft External Staff

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.

Raffaele Piccolo 26 Reputation points

2020-11-24T08:21:49.057+00:00

Yes, that is exactly my situation right there and that is exactly what i needed to know! If this behavior is by design i will switch to another enrollment method. I think it will be a nice feature to have prompted a credential dialog as soon as the package is provisioned so we won't handle any unwanted user creation.
Thank you a lot for the useful answer!
Crystal-MSFT 53,986 Reputation points Microsoft External Staff

2020-11-25T06:36:19.167+00:00

anonymous user, Thanks for the response. I am glad that the information can help. To get better customer experience for intune in the future version , we suggest to feedback our thought to Intune uservoice which Product team will review.
https://microsoftintune.uservoice.com/forums/291681-ideas

Thanks and have a nice day!
Raffaele Piccolo 26 Reputation points

2020-11-25T08:15:41.387+00:00

Thank you i surely will use this feedback forum, have a nice day you too!
Crystal-MSFT 53,986 Reputation points Microsoft External Staff

2020-11-26T01:40:54.3+00:00

anonymous user,Thanks for the understanding. Hope we can have more chance to discuss Intune in our Q&A in the future.

Have a good day!

Answer 2

Nick Hogarth 3,521 Volunteer Moderator

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?

Raffaele Piccolo 26 Reputation points

2020-11-24T08:18:08.167+00:00

You're right i did know the existence of the method you mentioned but wanted to have a full vision of the capacity of a bulk enrollment method.
The information given in the answer below does let me understand that is by design and i will stick to other method to avoid an unwanted bulk creation of impersonal account.
Thanks for the advise!

Share via

Azure AD Bulk Enrollment of Devices

1 additional answer

Your answer