update limits

Author: v-thepet

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

@@ -1,34 +1,33 @@
 ---
-title: Understand Device Update for IoT Hub limits | Microsoft Docs
-description: Key limits for Device Update for IoT Hub.
+title: Azure Device Update for IoT Hub limits | Microsoft Docs
+description: Understand key limits for Azure Device Update for IoT Hub.
 author: vimeht
 ms.author: vimeht
-ms.date: 9/23/2022
+ms.date: 01/10/2025
 ms.topic: conceptual
 ms.service: azure-iot-hub
 ms.subservice: device-update
 ---
 
-# Device Update for IoT Hub limits
+# Azure 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.
+This article provides an overview of the various limits imposed on the Azure Device Update for IoT Hub resource and its associated operations. The article also indicates whether the Standard SKU limits are adjustable by contacting Microsoft Support, and the default and maximum values for adjustable limits.
 
-## General Availability limits
+## 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. 
+The following tables describe the limits for the Device Update service for the Standard and Free tiers. 
 
 [!INCLUDE [device-update-for-iot-hub-limits](../../includes/device-update-for-iot-hub-limits.md)]
 
-### 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.  
+## Requirements for large-file downloads
 
-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.
+To deploy large-file packages with file size larger than 100 MB, it's best to use byte range requests for reliable download performance. Device Update uses Content Delivery Networks (CDNs) that work optimally with range requests of 1 MB in size. Range requests larger than 100 MB aren't supported.
 
 ## Throttling limits
 
-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.
+The following table shows the enforced throttles for operations in all Device Update tiers. Values apply to each individual Device Update instance.
 
-|Device Update service API | Throttling Rate |
+|Device Update service API | Throttling rate |
 |-------------------------|------------------|
 |GetGroups |30/min|
 |GetGroupDetails| 30/min|
@@ -52,12 +51,11 @@ The following table shows the enforced throttles for operations that are availab
 |List Versions| 510/min*|
 |List Operation Statuses| 50/min|
 
+\* The number of calls per minute is shared across all the listed operations.
 
-\* = the number of calls per minute is shared across all the listed operations
+Also, the number of concurrent asynchronous import and/or delete operations is limited to 10 total operation jobs.
 
-Additionally, the number of concurrent asynchronous import and/or delete operations is limited to 10 total operation jobs. 
+## Related content
 
-## Next steps
-
-- [Create a Device Update for IoT Hub account](create-device-update-account.md)
-- [Troubleshoot common Device Update for IoT Hub issues](troubleshoot-device-update.md)
+- [Create a Device Update account](create-device-update-account.md)
+- [Troubleshoot common Device Update issues](troubleshoot-device-update.md)

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

@@ -1,35 +1,36 @@
 ---
 author: vimeht
 ms.author: vimeht
-ms.date: 9/14/2023
+ms.date: 01/10/2024
 ms.topic: include
 ms.service: azure-iot-hub
 ms.subservice: device-update
 ---
 
-> [!NOTE]
-> 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](https://azure.microsoft.com/support/options/).
+If a given resource or operation doesn't have adjustable limits, the default and the maximum limits are the same. For adjustable limits, the following tables show both the default and maximum limits. The limits can be raised above the default limit but not above the maximum limit.
+
+Limits can be adjusted only for the Standard SKU. Free SKU limit adjustment requests aren't accepted, and Free SKU instances can't be upgraded to Standard SKU instances.
+
+To raise a limit or quota above the default limit, open an [online customer support request](https://azure.microsoft.com/support/options/). Limit adjustment requests are evaluated on a case-by-case basis, and approvals aren't guaranteed.
 
-This table provides the limits for the Device Update for IoT Hub resource in Azure Resource Manager:
+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? |
+| 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:
+The following table shows the limits associated with various Device Update operations.
 
-| Operation | Standard SKU Limit | Free SKU Limit | Adjustable for Standard SKU? |
+| 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 (includes all active, inactive and cancelled deployments that are not deleted) | 100 | 20 | No |
+| Number of active deployments per instance | 50, including one reserved deployment for cancellations | 5, including one reserved deployment for cancellations) | Yes |
+| Number of total deployments per instance, including all active, inactive, and cancelled 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 |
@@ -40,4 +41,4 @@ This table provides the various limits associated with the operations within Dev
 | Total data storage included per instance | 100 GB | 5 GB | No |
 
 > [!NOTE]
-> Cancelled or Inactive deployments count towards your total deployment limit. Please ensure that these deployments are periodically cleaned up, so that you are not prevented from creating new deployments. 
+> Cancelled 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.