Blog Post

Intune Customer Success
2 MIN READ

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

Intune_Support_Team's avatar
Intune_Support_Team
Silver Contributor
Mar 24, 2021

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.

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!

Updated Dec 19, 2023
Version 9.0

3 Comments

Comments have been turned off for this post
  • joel_grangier, thank you for the feedback! There are a few different ways on how you can stay up to date on Intune new features, service changes, and service health, to learn more see our post here: Staying up to date on Intune new features, service changes, and service health. You can also stay tuned to our Intune Customer Success blog (this one!) to stay up to date on any current known issues and support tips.

     

    To stay updated on when changes to the Microsoft Graph are made, see: Changelog - Microsoft Graph to learn more.

    Note: You can also subscribe to this page’s RSS feed to receive notifications when there are any new changes to this page.

  • joel_grangier's avatar
    joel_grangier
    Brass Contributor

    I really think that MSFT should inform us in an other official way. Currently, I don't know how or where, but how can we be prepared to such changes, when they are nowhere described?

    In that special case, you've created a blog entry concerning the issue caused by the replacement of the property orderIdentifier by groupTag. (and we can see that Michael Niehaus is really missing @ MSFT, because no one is maintaining his scripts ;-P)...

    ... And in the same blog, you are informing about the replacement of the property azureActiveDirectoryDeviceId by AzureAdDeviceId. How do you think that people can find this important information?