Request for DPS Throughput Limit Review and Quota Increase

Ankit Shrestha 0 Reputation points
2026-06-19T16:30:56.8633333+00:00

Dear Azure Support Team,

We are requesting a review of the provisioning throughput limits for our Azure Device Provisioning Service (DPS) deployment.

Environment Details:

Azure IoT Hub SKU: S1 (9 Units)

Azure DPS SKU: S1 (Capacity 1)

Active deployed devices: 25,000+

Projected device count within 12 months: 40,000+

Koili (Bitskraft Pvt. Ltd.) operates a large-scale QR Soundbox payment notification platform in Nepal. Our deployed IoT devices provide real-time payment notifications to merchants and rely on Azure DPS for device provisioning.

As our deployment volume continues to grow, we are encountering constraints associated with the current DPS provisioning throughput limit of approximately 1,000 provisioning operations per minute. We would like Microsoft to review whether higher throughput quotas are available for our DPS instance and advise on the maximum supported provisioning rate for our deployment.

Specifically, we would appreciate guidance on:

Whether DPS throughput limits can be increased through a quota review process.

Whether higher provisioning throughput is available for DPS S1 deployments.

The maximum supported provisioning rate Microsoft can provide.

Recommended architecture if our provisioning requirements exceed the documented DPS limits.

If a throughput increase is available, we would like to request consideration for increasing our DPS provisioning throughput to support future growth and large-scale provisioning events.

We are happy to provide additional telemetry, metrics, architecture diagrams, and provisioning statistics upon request.

Thank you for your assistance. Dear Azure Support Team,

We are requesting a review of the provisioning throughput limits for our Azure Device Provisioning Service (DPS) deployment.

Environment Details:

Azure IoT Hub SKU: S1 (9 Units)

Azure DPS SKU: S1 (Capacity 1)

Active deployed devices: 25,000+

Projected device count within 12 months: 40,000+

Koili (Bitskraft Pvt. Ltd.) operates a large-scale QR Soundbox payment notification platform in Nepal. Our deployed IoT devices provide real-time payment notifications to merchants and rely on Azure DPS for device provisioning.

As our deployment volume continues to grow, we are encountering constraints associated with the current DPS provisioning throughput limit of approximately 1,000 provisioning operations per minute. We would like Microsoft to review whether higher throughput quotas are available for our DPS instance and advise on the maximum supported provisioning rate for our deployment.

Specifically, we would appreciate guidance on:

Whether DPS throughput limits can be increased through a quota review process.

Whether higher provisioning throughput is available for DPS S1 deployments.

The maximum supported provisioning rate Microsoft can provide.

Recommended architecture if our provisioning requirements exceed the documented DPS limits.

If a throughput increase is available, we would like to request consideration for increasing our DPS provisioning throughput to support future growth and large-scale provisioning events.

We are happy to provide additional telemetry, metrics, architecture diagrams, and provisioning statistics upon request.

Thank you for your assistance.

Azure Internet of Things

1 answer

Sort by: Most helpful
  1. Anshika Varshney 14,620 Reputation points Microsoft External Staff Moderator
    2026-06-19T17:46:02.9166667+00:00

    Hello @Ankit Shrestha

    Thank you for contacting us.

    We understand your requirement for higher provisioning throughput for your Azure Device Provisioning Service (DPS) deployment. Based on the details shared, your current setup with Azure IoT Hub S1 (9 units) and DPS S1 (capacity 1) is operating within the standard service limits.

    At this time, DPS throughput limits are not generally increased through a standard quota request. The supported provisioning rate depends on the service design, SKU, and regional capacity, and any exceptions require internal review based on the scale, architecture, and business justification provided.

    For large-scale deployments such as yours, we recommend the following:

    • Stagger device provisioning in batches rather than provisioning the full fleet at once.
    • Use provisioning windows to spread load over time.
    • Review enrollment design and device onboarding flow to minimize burst traffic.
    • Consider architecture patterns that distribute provisioning load more evenly.

    Thank you for your patience and partnership.

    I Hope this helps. Do let me know if you have any further queries.

    Thankyou!

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.