What’s changing:
The architecture of your IoT Hub includes a cluster of front-end message processing servers and software we call the IoT Hub gateway. We are rolling out availability, reliability, and security improvements to this gateway between July 2023 and November 2023.
Potential impact:
The gateway upgrade will result in:
- A forced disconnect and reconnect for all devices.
- New static IP addresses for all IoT hubs.
Device disconnects:
Your devices will disconnect from IoT Hub while we upgrade the gateway nodes. The time it takes for your devices to reconnect depends on:
- DNS update propagation: If your devices leverage DNS to resolve your IoT hub’s IP address, it will resolve the new IP address after the DNS updates propagate to the device’s DNS server(s) and any local DNS cache expires.
- DPS reprovisioning: Reprovisioning is subject to DPS limits. Follow the recommended best practices to reprovision devices with DPS. Avoid reprovisioning unless IoT Hub returns an error other than 429 or 5xx.
- Device connection retry logic: If your devices leverages the Azure IoT SDKs, they will attempt to reconnect according to their retry policy.
- Device connection throttling: IoT Hub throttles device connections based on your selected tier.
Firewall rules and impact:
- If you followed our best practices to configure your IoT Hub by using Fully Qualified Domain Name (FQDN), then no action is required.
- If you implemented a range-based approach using IoT Hub service tags, no action is required.
- If you restrict access based on a specific IP address for your IoT Hub, follow our best practices and move away from a static IP address. The IP address of your IoT Hub might change at any time for any reason.
- If you cannot follow our best practices or have questions, reach out to your Azure IoT or Microsoft contacts.
