Event details

Curious if Windows Autopilot can help simplify your new device deployment process? What about repurposing existing devices? Have questions about pre-provisioned deployment, user-driven Hybrid Azure A...
Heather_Poulsen
Updated Jul 21, 2021
AMA
Sam Chow's avatar
Sam Chow
Occasional Reader
Jul 21, 2021
In our environment, we are converting ConfigMgr imaged laptops to Autopilot. After reset and went through the Autopilot progress, the device record in "Enroll device - Windows Autopilot devices" is referencing to two device ID between "Associated Intune device" and "Associated Azure AD device". Due to the Autopilot process, we are using a new naming convention for Autopilot deployed device. Associated Intune device has the up-to-date device name, and Associated Azure AD device is still referencing to the legacy device name (ConfigMgr imaged). When we have a dynamic query AzureAD group that looks for "Group Tag" of this device, it didn't capture the "Associated Intune device" name, and the device fell off from the AzureAD group. Is this an expected behavior for converting?
Nandhini_Prasad's avatar
Nandhini_Prasad
Icon for Microsoft rankMicrosoft
Jul 21, 2021
Thanks for the question. May I ask if this is a Hybrid AAD joined device?
  • Sam Chow's avatar
    Sam Chow
    Occasional Reader
    Jul 21, 2021
    Before Autopilot reset, yes. ConfigMgr imaged devices are all Hybrid AAD joined. After Autopilot, it's AAD joined only.
    • Nandhini_Prasad's avatar
      Nandhini_Prasad
      Icon for Microsoft rankMicrosoft
      Jul 21, 2021
      Could you please file a support ticket with us? Do include more details like SerialNumber of impact devices, expected GroupTag value, the dymanic grouping rule used, expected AAD security group, profile expected to be assigned. Thanks!