M365Con 2027 – free online conference · 11–22 Jan 2027 · 120 sessions m365con.net

Azure IoT Hub Device Provisioning Service (DPS)

Product

An Azure helper service for IoT Hub that verifies a device's proof of identity against enrollment rules on first boot and assigns it to an IoT hub using an allocation policy, enabling zero-touch provisioning.

◆ PRODUCTAzure IoT Hub DeviceProvisioning Service…M365.FM
Title graphic: Azure IoT Hub Device Provisioning Service (DPS) (Product)

Relationships

Azure IoT Hub Device Provisioning Service (DPS) is a product and part of Azure IoT Hub.

Description

Azure IoT Hub Device Provisioning Service (DPS), also referred to as IoT Hub Device Provisioning Service or Device Provisioning Service, is a helper service for Azure IoT Hub. It enables zero-touch, just-in-time provisioning of devices to the right IoT hub without manual steps. In practice, it answers a question that becomes harder as fleets grow: which hub should a given device talk to, and how does that device get registered there without anyone configuring it by hand?

The process follows a defined sequence. The manufacturer stores credentials and the DPS endpoint on the device. In the cloud, enrollments define which devices are valid and how they are provisioned. On first boot, the device contacts DPS and proves its identity. DPS checks that proof against the enrollment list, assigns the device to a hub using an allocation policy, and registers it there. After that, the device communicates with the hub directly. DPS only becomes involved again if a device needs to be reprovisioned.

The service supports X.509 and TPM-based attestation, which are the mechanisms a device can use to present cryptographic proof of its identity. Enrollments come in two forms, individual and group, so that a device can be listed on its own or as part of a larger set. Allocation policies decide which hub receives a device: lowest latency, evenly weighted and static are available, and custom allocation is possible through Azure Functions webhooks. Devices can connect over HTTPS, AMQP or MQTT.

Typical scenarios named in the documentation are load balancing across multiple hubs, multitenancy, geo-sharding and reprovisioning. Several operational points matter when planning a deployment. Each API call is a billable operation, and per-subscription limits apply, for example to the number of instances, enrollments and linked hubs. Provisioning of nested IoT Edge devices is not supported. These constraints are relevant when estimating cost and capacity for large rollouts.

The M365.FM episode "Azure DPS: Why Provisioning 100,000 IoT Devices Is an Architecture Problem" frames DPS as an architectural decision rather than a configuration detail. According to the episode, DPS acts as the secure reception desk for a cloud estate, standing between unconfigured hardware and the specific IoT hub that will handle its daily traffic. Instead of hard-coding endpoints into firmware, devices contact a global provisioning endpoint on first boot, present their cryptographic proof, and receive the details of their assigned hub.

The episode also stresses a separation between a device's manufacturing identity, meaning where and how the unit was built, and its operational identity, which determines how and where the device connects to the cloud. The episode says this separation keeps device images portable across different customer environments and deployment waves. This ties directly to how DPS works: the image carries credentials and the provisioning endpoint, while the hub assignment is decided later in the cloud through enrollments and allocation policies.

DPS is part of Azure IoT Hub's ecosystem and is closely related to it. IoT Hub handles the ongoing device communication, while DPS handles the initial assignment and registration. For teams planning large device populations, the relevant decisions are the attestation method, the choice between individual and group enrollments, the allocation policy, and whether reprovisioning will be needed over the device lifetime.

Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.

TypeProduct

Episodes about Azure IoT Hub Device Provisioning Service (DPS)

Episodes in which Azure IoT Hub Device Provisioning Service (DPS) is discussed:

From Sensor to Dashboard: The MQTT Pipeline Through Azure IoT Hub

2026-10-19

Most factory dashboards start at the wrong end: they show a temperature or an OEE number, but nobody can explain where the message came from or whether it can be trusted. This episode is for OT and IT architects, data engineers and manufacturing leaders…

Frequently asked questions

Questions marked with AI were written with AI from the facts on this page.

What does Azure IoT Hub Device Provisioning Service do? (AI)

It is a helper service for Azure IoT Hub that verifies a device's proof of identity against enrollment rules on first boot and assigns the device to an IoT hub using an allocation policy. This enables zero-touch, just-in-time provisioning without manual steps.

Which attestation methods and allocation policies does DPS support? (AI)

DPS supports X.509 and TPM-based attestation. Allocation policies include lowest latency, evenly weighted and static, plus custom allocation through Azure Functions webhooks.

Does a device keep contacting DPS after it is provisioned? (AI)

No. After provisioning, the device talks to its assigned IoT hub directly. DPS only becomes involved again for reprovisioning.

Related topics in brief

Topics linked to Azure IoT Hub Device Provisioning Service (DPS), each briefly explained:

All relationships of Azure IoT Hub Device Provisioning Service (DPS), grouped by type of relationship:

Part of

Offerings of which Azure IoT Hub Device Provisioning Service (DPS) is a part:

Glossary

Community wiki

Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.

Experts and companies for this topic

Nobody has listed this topic yet. Add it to your profile.

Sources

Maintained by Mirko Peters (Microsoft MVP) · Last updated: