Device Update for IoT Hub limits
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.
General Availability limits
The following tables describe the limits for the Device Update for IoT Hub service for the Standard as well as the Free tier.
When a given resource or operation doesn't have adjustable limits, the default and the maximum limits are the same. When the limit can be adjusted, the following table includes both the default limit and maximum limit. The limit can be raised above the default limit but not above the maximum limit. Limits can only be adjusted for the Standard SKU. Limit adjustment requests are not accepted for Free SKU. Limit adjustment requests are evaluated on a case-by-case basis and approvals are not guaranteed. Additionally, Free SKU instances cannot be upgraded to Standard SKU instances.
If you want to raise the limit or quota above the default limit, open an online customer support request.
This table provides 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|
This table provides the various limits associated with the operations within Device Update for IoT Hub:
|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 (includes 1 reserved deployment for Cancels)||5 (includes 1 reserved deployment for Cancels)||Yes|
|Number of total deployments per instance||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|
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.
The following table shows the enforced throttles for operations that are available in all Device Update for IoT Hub tiers. Values refer to an individual Device Update instance.
|Device Update service API||Throttling Rate|
|GetBestUpdates per group||30/min|
|GetUpdateCompliance per group||30/min|
|Get Operation Status||510/min*|
|List Operation Statuses||50/min|
* = the number of calls per minute is shared across all the listed operations
Additionally, the number of concurrent asynchronous import and/or delete operations is limited to 10 total operation jobs.