Azure IoT Hub
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
Our Azure IoT Update appears to be malfunctioning.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 76%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAW%3C/text%3E%3C/svg%3E)
Adrian Wreyford
65
Reputation points
Good Day,
For the last month we have been experiencing issues with Azure IoT Hub - Specifically the Update blade.
We have created a new tag: ADUGroup: LoadAssistTestADU-ESP32S3-F16-R8, and flashed a new ESP32S3 based custom PCB, with it, the 'ADU version' 1.0.
We provisioned this new device, and it now shows in IoTHub - Devices blade, and it's digital twin is correct.
The Device Provisioning service is correctly set up, and inserted this ADU tag in the devices Digital Twin as was expected to be the case.
The New LoadAssistTestADU-ESP32S3-F16-R8 Update Group appeared when we provisioned the device.
So far all looks good.
The Update appears in the Updates pane, and when clicking on Groups and Deployments, there now is a new group with Group name: LoadAssistTestADU-ESP32S3-F16-R8.
Is is exactly as we would expect it to be, and as it has always been working.
When we click on this specific group, it shows that no devices are linked, not even the device we just provisioned, that obviously triggered the creation of the group.
This is where things start to go wrong.
Group Basics are correct for the name and type, but no link appears to deploy the new update we just uploaded.
The Device List when refreshed is also not displaying the device. Even hours later.
And yes I have done this for the past two years and know the ropes. The digital twin is also correct.
Searching for the device (Group basics), results in No devices or modules match your filter.
So we cannot deploy updates :(
It doesn't end there either...
If we go to our other older existing update groups, where we used to see all the devices, we only see a few (less than 5%) of the devices.
So something appears broken on the Azure Update on our node.
DPS hosted Location: East US, as to date not available in SA North where the remainder of our Azure is hosted.
Can some one please help address this issue.
Azure IoT Hub
{count} votes
-
Sander van de Velde | MVP 36,941 Reputation points MVP Volunteer Moderator2025-07-20T18:52:01.0833333+00:00 Hello @Adrian Wreyford ,
welcome to this moderated Azure community forum where community member answer questions.
It seems you have a specific issue with the Device Update functionality that worked in the past.
It could be this is a temporary issue but it doesn't look like that.
I recommend creating an Azure support ticket due to the complexity.
If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 74%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
VSawhney 880 Reputation points Microsoft External Staff Moderator2025-07-21T10:02:03.4766667+00:00 Hello Adrian Wreyford,
It seems you're facing a frustrating issue with the Azure IoT Hub's Device Update functionality, especially with devices not linking to the new update group you created. Here’s a rundown of things you might want to check or try to resolve the situation:
- Device Connection: Ensure that the new ESP32S3 device is correctly connected to both the IoT Hub and the Device Update service. You can verify this by checking if it shows up under the "Ungrouped" devices section in the Azure portal.
- Update Group Settings: Double-check the settings of your Update Group, ensuring that the filter criteria for device inclusion align with the capabilities and tags of your device.
- Provisioning Status: Confirm that the provisioning process for your new device completed successfully without errors. You can do this by reviewing the provisioning logs.
- Delivery Optimization: Make sure that the Delivery Optimization service is running as it plays a key role in managing updates.
- Digital Twin Validation: While you mentioned the digital twin is correct, if any properties were set incorrectly, the device may not link properly. Review the properties set in the digital twin and see if they align with the expected values.
- Update Compliance: The device should report its compliance status to check whether it qualifies for the updates in your Update Group.
Hope this helps you get on the right path! Please let us know how it goes or if you have more info to share.
Thank you! -
Adrian Wreyford 65 Reputation points
2025-07-22T13:03:38.26+00:00 We cannot afford additional cost of $100 per month to be able to submit a support ticket.
I've checked all the suggested checks above, and they are all correct.
Please note -- we have been using it and was functioning correctly. It is now broken.
We have invested heavily in Azure, at great cost, but this is really a showbreaker. No way to get support without forking out money. -
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator2025-07-29T01:23:34.4866667+00:00 We understand your constraints. Just wanted to let you know that I saw some product group tickets earlier on Device update which are in mitigated.
If the issue persists, please let us know your resource url of IOT hub in private message (/subscription/<subid>/resourcegroup/<rgname/...) to tag in that ICM or create a new ICM.
Looking forward to hearing from you.
Thank you
-
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator
2025-08-01T03:07:35.8666667+00:00 Have reached product group with the details shared. Shall update once we have some analysis from product group.
Have message service owner too to look into this case
Thank you
-
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator
2025-08-04T03:15:16.05+00:00 It has rotated back to IOT hub product group after it was investigated on DPS side. No issue on DPS side.
Have messaged privately current service owner for further investigation.
Shall keep you posted as we progress.
Thank you.
-
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator
2025-08-06T03:47:42.19+00:00 Could you share at least 10 Device Ids which are not appearing in Device group on private message.
Thank you
-
Manas Mohanty 8,150 Reputation points Microsoft External Staff Moderator
2025-08-08T02:10:24.4333333+00:00 We could not hear from you on the device ids. Closing this case temporarily until we hear back from you.
Thank you
Sign in to comment
Sign in to answer