Resolved – Unable to assign group tags with the WindowsAutopilotIntune PowerShell script

Posted by

This post has been republished via RSS; it originally appeared at: Intune Customer Success articles.

3/24 Update: This issue is now resolved! The next time you run "Install-Module -Name WindowsAutoPilotIntune" it should download the latest version 5.0 of the Autopilot Module.

 

We were recently alerted to a scenario where customers using version 4.8 of the WindowsAutopilotIntune PowerShell script are no longer able to assign group tags to Intune managed Windows devices.

 

During investigation, we discovered that due to a recent change in promoting the Intune GraphAPI from beta to v1.0, the “orderIdentifier” property used with the “$groupTag” value has been renamed to "groupTag".

 

Example screenshot of the "$groupTag" property in the WindowsAutoPilotIntune script.Example screenshot of the "$groupTag" property in the WindowsAutoPilotIntune script.

To align with this recent change, the WindowsAutopilotIntune PowerShell script has been updated to use “groupTag” in place of the “orderIdentifier” property instead. We recently updated the script to align with these changes and the new version (v5.0) of the script can be found here: PowerShell Gallery | WindowsAutoPilotIntune 5.0.

 

We'd also like to share that you can manually set the group tag for Windows Autopilot devices by using the following steps:

  1. Login to the Microsoft Endpoint Manager admin center.
  2. Select Devices > Windows > Windows enrollment > Devices (under Windows Autopilot Deployment Program).
  3. Select the device you wish to assign a group tag to, enter in an attribute that can be used to identify a group of devices > Click Save.

See: Edit Autopilot device attributes for more info.

 

Note: You can also add Windows Autopilot devices by importing the CSV file to set a group tag. See: Manually register devices with Windows Autopilot | Add devices to learn more.

 

Additional considerations

A part of the recent improvements and changes to the windowsAutopilotDeviceIdentity resource types, we also wanted to let you know that in an upcoming Intune service release, the “azureActiveDirectoryDeviceId” property will soon be renamed to “AzureAdDeviceId”.

 

While the “AzureAdDeviceId” property is currently available, if you have any scenarios or scripts using the “azureActiveDirectoryDeviceId” property, you will soon have to update to use “AzureAdDeviceId” instead.

 

More info and feedback

For further resources on this subject, please see the links below.

 

Let us know if you have any additional questions by replying to this post or reaching out to @IntuneSuppTeam on Twitter.

 

Blog Post Updates:

3/24: This issue has been resolved with version (v5.0) of the script!

This articles are republished, there may be more discussion at the original link. But if you found this helpful, you're more than welcome to let us know!

This site uses Akismet to reduce spam. Learn how your comment data is processed.