Skip to content

Commit 1dfafe7

Browse files
Merge pull request #225661 from vimeht/main
Update limits and subgroup texts
2 parents ec2e833 + fad073f commit 1dfafe7

File tree

2 files changed

+11
-3
lines changed

2 files changed

+11
-3
lines changed

articles/iot-hub-device-update/device-update-groups.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -64,9 +64,17 @@ Below are the devices and the possible groups that can be created for them.
6464
| Device1 | Group1 |
6565
| Device2 | Group1 |
6666
| Device3 | Group2 |
67-
| Device4 | DefaultGroup1-(deviceClassId) |
67+
| Device4 | DefaultGroup |
6868

6969

70+
## Subgroups
71+
72+
All user-created groups as well as default groups are automatically sub-categorized into one or more subgroups to allow administrators to manage heterogeneous devices in an organized and efficient manner, by providing a way to perform updates on a set of devices that share compatibility properties. Each device class within a group maps to one subgroup. Devices are added to a subgroup based on their compatibility properties and the Device Update PnP model ID, which together comprise a device class.
73+
74+
A group can have one or more best available update, one for each subgroup it contains.
75+
76+
[Learn more](./device-update-configuration-file.md) about setting compatibility properties on the Device Update agent
77+
7078
## Next steps
7179

7280
[Create a device group](./create-update-group.md)

includes/device-update-for-iot-hub-limits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ This table provides the various limits associated with the operations within Dev
2727
| Number of devices per instance | 1 Million | 10 | Yes |
2828
| Number of device groups per instance | 100 | 10 | Yes |
2929
| Number of device classes per instance | 80 | 10 | Yes |
30-
| Number of active deployments per instance | 250 | 10 | No |
31-
| Number of total deployments per instance | 300 | 20 | No |
30+
| Number of active deployments per instance | 50 (includes 1 reserved deployment for Cancels) | 5 (includes 1 reserved deployment for Cancels) | Yes |
31+
| Number of total deployments per instance | 100 | 20 | No |
3232
| Number of update providers per instance | 25 | 2 | No |
3333
| Number of update names per provider per instance | 25 | 2 | No |
3434
| Number of update versions per update provider and name per instance | 100 | 5 | No |

0 commit comments

Comments
 (0)