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(124.80000000000001, 35%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
Hi,
I have 500 existing azure ad registered and disconnected devices that I need to join in AAD.
I can't take autopilot as it overwrites everything.
Manually I can join all devices in AAD without problems via "System Settings / Account / Connect / Connect to Azure AD" with the device enrollment manager.
But this is not possible with this amount of devices
I have tried the "Bulk Enrolment for Windows Devices" via the Windows Configuration Designer.
The device can be renamed via the .ppkg and also a local Admin User can be created. Unfortunately, however, it does not include the computer in AAD joined.
The operating system is the latest windows 10 enterprise Version.
What could be the cause ? What have I not seen ?
thank you for the support
https://learn.microsoft.com/en-us/mem/intune/enrollment/windows-bulk-enroll
@Stefan Adorjan Thanks for posting in our Q&A.
From your description, did you mean that the devices that have joined to Azure AD didn't change their device name after bulk enrollment? If there is anything misunderstanding, please correct me.
Based on my understanding, bulk enrollment is needed to do in devices that are not already joined to Azure AD, because devices will be joined to Azure AD and enrolled to intune during this bulk enrollment process.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
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.
Hello Lu Dai-MSFT, thank you for the answer.
On the local device, renaming device and creating a local user works very well.
However, the computers are not included in Azure AD.
The bulk enrollment is needed to do in 500 devices that are not already joined to Azure AD.
The picture above shows the status of a local test device.
Hello Lu Dai-MSFT, thank you for the answer.
On the local device, renaming device and creating a local user works very well.
However, the computers are not included in Azure AD.
The picture above shows the status of a local test device.
The bulk enrollment is needed to do in 500 devices that are not already joined to Azure AD.
@Stefan Adorjan It seems something wrong in Azure AD. It is suggested to create an Azure AD support ticket to get more accurate help. Here is the support link:
https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/how-to-get-support