Hello @重归 , Thanks for reaching out on this forum.
Could you please add more info on the issue.
1) Which Region you have created Azure IoT Hub
2) Azure IoT Hub Tier?
3) How did you make the MQTT connection, any specific client used?
4) Any screenshots of the error or the logs would be more helpful to help you further....
5) Any log traces?
Thanks for understanding
Other workarounds from similar issues which may be helpful in this scenario:
setting the Clean Session flag to ‘0’ and QoS=1 which prevents losing messages when the device is in a disconnected state.
The device does not receive any messages from IoT Hub until it has successfully subscribed to its device-specific endpoint, represented by the devices/{device_id}/messages/devicebound/# topic filter. After a subscription has been established, the device receives cloud-to-device messages that were sent to it after the time of the subscription. If the device connects with CleanSession flag set to 0, the subscription is persisted across different sessions. In this case, the next time the device connects with CleanSession 0 it receives any outstanding messages sent to it while disconnected. If the device uses CleanSession flag set to 1 though, it does not receive any messages from IoT Hub until it subscribes to its device-endpoint.
If you try to do lot of connect/disconnects at same time for n number of devices, then there will be throttling. Numbers are in below link
https://video2.skills-academy.com/en-us/azure/iot-hub/iot-hub-devguide-quotas-throttling
But you can always avoid throttling by scaling up as per your needs.
https://azure.microsoft.com/en-us/blog/iot-hub-throttling-and-you/