Skip to content

Commit 0d9e498

Browse files
committed
Addd faq for multiple DPS instances provisioning to an IoT hub.
1 parent 8add49b commit 0d9e498

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/iot-dps/dps-faq.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,10 @@ sections:
3838
How does the health of an IoT hub affect device provisioning?
3939
answer: |
4040
Currently DPS doesn't check the health of an IoT hub before assigning devices. DPS will continue to try to assign devices to an IoT hub that is down based on its configured allocation policy. For example, if the configured allocation policy is *Lowest latency* and DPS has a linked IoT hub in region A (hub A) and one in region B (hub B), it will assign a device trying to provision from region A to hub A, even if hub A is down. To factor in IoT hub health when provisioning devices, you can implement a custom allocation policy with your own monitoring logic based on [IoT Hub diagnostics](../iot-hub//monitor-iot-hub.md) or your own user-defined metrics. To learn more about custom allocation policies, see [How to use custom allocation policies](how-to-use-custom-allocation-policies.md).
41+
- question: |
42+
Can multiple DPS instances provision devices to the same IoT hub?
43+
answer: |
44+
Yes; however, built-in allocation policies apply to each DPS instance individually, so load balancing across multiple IoT hubs is not possible when using the built-in DPS policies. Instead, you can use a custom allocation policy to implement load balancing when using multiple DPS instances. To learn more about custom allocation policies, see [How to use custom allocation policies](how-to-use-custom-allocation-policies.md).
4145
4246
- name: DPS Billing
4347
questions:

0 commit comments

Comments
 (0)