Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This document provides an overview of the various limits that are imposed on the Device Update for IoT Hub resource and its associated operations. It also indicates whether the limits are adjustable by contacting Microsoft Support or not.
Preview limits
During preview, the Device Update for IoT Hub service is provided at no cost to customers. More restrictive limits are imposed during the service's preview offering. These limits are expected to change once the service is generally available.
Limits can be adjusted only for the Standard SKU. Limit adjustment requests are evaluated on a case-by-case basis, and approvals aren't guaranteed.
Limit adjustment requests aren't accepted for the Free SKU. Also, Free SKU instances can't be upgraded to Standard SKU instances.
The following table shows the limits for the Device Update for IoT Hub resource in Azure Resource Manager.
| Resource | Standard SKU limit | Free SKU limit | Adjustable for Standard SKU? |
|---|---|---|---|
| Accounts per subscription | 50 | 1 | No |
| Instances per account | 50 | 1 | No |
| Length of account name | 3-24 characters | 3-24 characters | No |
| Length of instance name | 3-36 characters | 3-36 characters | No |
The following table shows the limits associated with various Device Update operations.
| Operation | Standard SKU limit | Free SKU limit | Adjustable for Standard SKU? |
|---|---|---|---|
| Number of devices per instance | 1 million | 10 | Yes |
| Number of device groups per instance | 100 | 10 | Yes |
| Number of device classes per instance | 80 | 10 | Yes |
| Number of active deployments per instance | 50, including one reserved for cancellations | 5, including one reserved for cancellations | Yes |
| Number of total deployments per instance, including all active, inactive, and canceled deployments that aren't deleted | 100 | 20 | No |
| Number of update providers per instance | 25 | 2 | No |
| Number of update names per provider per instance | 25 | 2 | No |
| Number of update versions per update provider and name per instance | 100 | 5 | No |
| Total number of updates per instance | 100 | 10 | No |
| Maximum single update file size | 2 GB | 2 GB | Yes |
| Maximum combined size of all files in a single import action | 2 GB | 2 GB | Yes |
| Maximum number of files in a single update | 10 | 10 | No |
| Total data storage included per instance | 100 GB | 5 GB | No |
Note
Canceled or inactive deployments count toward your total deployment limit. Make sure to clean up these deployments periodically so you aren't prevented from creating new deployments.
Requirements for large-file downloads
If you plan to deploy large-file packages, with file size larger than 100 MB, it is recommended to utilize byte range requests for a reliable download performance.
The Device Update for IoT Hub service utilizes Content Delivery Networks (CDNs) that work optimally with range requests of 1 MB in size. Range requests larger than 100 MB are not supported.