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(182.40000000000003, 32%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAB%3C/text%3E%3C/svg%3E)
Hi,
We have Azure AD joined machines, and we have enrolled them with Endpoint Manager.
What is the best way to also change these to AutoPilot devices without running a wipe ?
Do I manually need to get the hardware ID from them ?
There is no local AD, all cloud.
/R
Andy
See https://learn.microsoft.com/en-us/mem/autopilot/automatic-registration
Not exactly sure what you mean by "change these to Autopilot" though. Simply registering a device with Autopilot, whether done manually or automatically never requires a wipe, however, registering a device with AUtopilot has no value unless you reset the device kick off the Autopilot process (which can only be done on a device that is in a reset state).
![](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(233.6, 30%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
@andreas bright , Agree with Jason, to convert existing windows 10 devices which are not registered as an Autopilot device, we can create an Autopilot deployment profile, set "Convert all targeted devices to AutoPilot" to Yes. Assign this profile to the device group which include the devices we want to convert. After some time, check the "Assigned devices" under the profile to see if they are visible there. If yes, it means these devices are Autopilot ready. We can reset the device to do Autopilot. Here is an article with detailed steps for the reference:
https://www.robinhobo.com/automatic-add-existing-windows-10-devices-to-windows-autopilot/
Note: Non-Microsoft link, just for the reference.
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.
![](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(284.8, 67%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGA%3C/text%3E%3C/svg%3E)
When you convert existing devices, wipe them, and then send them through Autopilot there are two Azure AD objects as a result. We'll call them $OriginalDevice and $ConvertedDevice. The AAD object of $OriginalDevice is labeled with the Autopilot icon in Azure AD, When looking at the device in the Autopilot devices within Intune, you can see that serial has an associated Azure AD object of $OriginalDevice and an associated Intune device of $ConvertedDevice.
When searching Azure AD for $ConvertedDevice, there is a second Azure AD object that was created. It says it is managed by Intune. However, if you have a dynamic device group for your Autopilot devices (i.e. [(device.devicePhysicalIDs -any (_ -contains "[ZTDId]"))]), the second Azure AD object with a name of $ConvertedDevice does not show in that group.
This makes it very, very confusing when trying to use this feature. Are there any limitations to this feature like Windows version?
@Greg Arnold , For the two Azure AD records, are they both Azure AD joined? Did one record occurs when we wipe the device to convert the device into Autopilot? Please help to confirm the information. Thanks!
The original Azure AD object, which is also the associated device with the Autopilot device in Windows Enrollment --> Devices, is still listed as Hybrid AD Join. When you click on Manage for this device it throws an error.
The newly created Azure AD object is Azure AD Join. When you click Manage on this AAD device, it takes it to the correct Intune device page.
The original device has the Autopilot icon next to it, but the new one does not. Both say managed by Intune.
Below is a log of when the device is created after the second wipe during Autopilot.
Activity
Date
6/3/2021, 11:36 PM
Activity Type
Add device
Correlation ID
*UID
Category
Device
Status
failure
Status reason
Microsoft.Online.Workflows.ObjectAlreadyExistsException
Initiated by (actor)
Type
Application
Display Name
Device Registration Service
App ID
Service Principal ID
*UID
Service Principal Name
Additional Details
User-Agent
Microsoft ADO.NET Data Services
@Greg Arnold , Thanks for the reply. For Windows Autopilot and user driver Hybrid Azure AD join deployment, based on my test before, it will create two records in Azure AD by default. Here is a blog for the reference:
https://oofhours.com/2020/01/20/the-first-day-in-the-life-of-a-hybrid-azure-ad-joined-device/
Note: Non-Microsoft link, just for the reference.
Also, find a similar issue in Intune user voice: We can vote here to see if the records will be combined in the future:
https://microsoftintune.uservoice.com/forums/291681-ideas/suggestions/41994496-merge-aad-and-hybrid-ad-objects-autopilot
Thanks for the understanding and have a nice day!
The original device wasn’t provisioned with Autopilot. It was imaged traditionally with a third party imaging solution. Later enrolled into Intune via group policy to be managed and migrate workloads away from on-prem infra. And then reset for Autopilot, user driven AAD join, cloud only management.
Every time the device is reset, the associated AAD object stays as the Hybrid join AAD object.
@Greg Arnold , Thanks for the reply. I will prepare one GPO enrolled device and do the Autopilot reset to test. It may take some days. If there's any update, I will post back.
@Greg Arnold , I have deployed a new windows machine in my on-premise domain. But find it not be Hybrid Azure AD joined. I am troubleshooting in my environment. For our issue, to get more help, we suggest to open case to work on this. here is a link about opening case:
https://learn.microsoft.com/en-us/mem/get-support
Thanks for the understanding.
Hi Crystal,
Did anything come of this? We ended up creating a Flow to import our existing devices as a workaround.
Hi @Jason Sandys ,
It may be that I am mistaking something here... let me try to explain.
In Intune today under Devices>Windows we have many devices, but none of these are Autopilot, so they Autopilot icon is grey. And I guess if we do a wipe of the device it will not get the Autopilot profile since it is not registered as an Autopilot device.
So do I have to login manually to each device and get the hardware ID and uploaded the csv file ?
/R
Andy
No. See the document I linked to above. This will automatically register Intune enrolled devices in Autopilot.
There is a new feature, that when you deploy Autopilot profile to a group, you can make existing device to get under Autopilot devices, I think it is automatic hardware hash collection of somekind. In my case, I have enabled this feature and I have dynamic ZT group and also assigned group which contains existing machines from a hybrid - they will transfer to Autopilot devices. But this covers only the automated provess of hardware hashes, nothing more.
Yes this I am aware of and is what I tried to explain where the flaw in the feature is, at least in what I’ve experienced.
The issue with this, at least in our environment, is we are targeting a lot of apps and config profiles to this dynamic group. So the deployment is incomplete when the device gets wiped/reset any time after the first one.