Add the ability to push updates based on tags

[Werewolfkiss]

As far as I can find now, you can only deploy updates based on the 1 ADUGroup tag and the device compatibilities.
For our use case it would be very helpful if we could send an update based on all the device tags.

Our use case is:
One IOT edge device, receiving updates for other inbuilt components, each device can have different components in it, and we tag the device to show which components it has.
For instance:
tags:
“Subsystem1” : “Manufacturer A”
“Subsystem2”: “Manufacturer B”
“Subsystem3”: “Manufacturer A”

Then if we have a new update from manufacturer A subsystem 1 we want to push that to all devices that have the tag.

[Nox-MSFT]

Include @andrewbrownmsft & @alancshi for input.

[andrewbrownmsft]

I actually think this would be @vimeht.

[Berveglieri]

We are facing the same limitation in our implementation, we have the plan to deploy 30000 devices but we are not sure how we gonna by pass this limitation with the tags in the device groups.
We have a very specific business logic to handle the updates that we could easily control with tags but ADUGroup only allows one what makes impossible for us to group the updates based on the business rules.
I have found this, can we bypass this limitation using this Device class subgroup described here? I couldn't find a way to inject my own value or retrieve any value from this call.
https://learn.microsoft.com/en-us/rest/api/deviceupdate/2022-10-01/device-management/get-deployment-for-device-class-subgroup?tabs=HTTP

[josephmsft]

Device Class subgroups are a service-defined grouping based on compatibility properties. Customers define grouping based on a ADUGroup tag value, but the service further creates a subgroup automatically based on compatibility properties (this is translated into a device class Id which is also used as the subgroup Id). This ensures that all devices within the group that share identical compatibility are identified so when an update is deployed to a group the service can rapidly identify which devices should get the update and be able to provide deployment status at the subgroup level.

Unfortunately this means there is no way for an API caller to alter the definition of a subgroup or create one.

[Berveglieri]

@josephmsft thank you very much for the clarification.
In this case we are stuck with the limitation of not being able to manage the updates based on multiple tags.
Is it in the roadmap? it would be a game changer for us, because without this ability we are considering look for another solution out of Azure and we would like to have everything in one place.

[josephmsft]

That's a question better answered by @vimeht