Forum Discussion
Nayuta
Aug 06, 2019Copper Contributor
Autopilot profile is not assigned if a device already registered Azure AD
When import device information for Autopilot, if the devices already registered to Azure AD, the profile status in Windows Autopilot devices have not changed from ”Not Assigned”. After deleting t...
Moe_Kinani
Jun 06, 2020Bronze Contributor
Hi Nayuta,
This is normal behavior, if you importing the devices using csv file, you need to make sure that the devices do not exist in Azure AD at all. If you have existing devices and you want to apply Auto Enrollment Deployment Profile, you just need hit yes on ‘Convert all Targeted device to Auto Pilot’.
Hope I’m understanding your scenario correctly!
Moe
https://www.google.com/amp/s/secureinfra.blog/2019/10/31/convert-all-targeted-devices-to-autopilot/amp/
This is normal behavior, if you importing the devices using csv file, you need to make sure that the devices do not exist in Azure AD at all. If you have existing devices and you want to apply Auto Enrollment Deployment Profile, you just need hit yes on ‘Convert all Targeted device to Auto Pilot’.
Hope I’m understanding your scenario correctly!
Moe
https://www.google.com/amp/s/secureinfra.blog/2019/10/31/convert-all-targeted-devices-to-autopilot/amp/
LurkingMedal140
Jun 06, 2020Copper Contributor
In my instance, the property 'Convert all targeted devices to Autopilot' is already configured to yes.
However, Devices registered for autopilot are not pulling a profile.
Thanks
- Moe_KinaniJun 09, 2020Bronze Contributor
Could you add the PCs to regular Security group and assign them to the deployment profile? It might be the dynamic group somehow dropping the PCs.
Moe
- LurkingMedal140Jun 09, 2020Copper Contributor
So I have raised this as an MS Support Ticket, they have informed me that currently there is various region issues with profile deployment using Windows Auto-Enrollment. These are backend issues and are currently being resolved.
Although I have not seen any public comms from MS for this.
- ITluchoOct 19, 2020Copper ContributorDid you manage to resolve this?