IoT Hub: Latest deployment information not reflected in portal despite device updates

Question

IoT Hub: Latest deployment information not reflected in portal despite device updates

Davy Meybos 80

Problem description

I am experiencing an issue where the Azure portal's IoT Hub Devices view does not display the most recent deployment information for my devices, even though the modules on the devices are updated successfully. The deployment is sent programmatically from a C#/.NET application using the Microsoft.Azure.Devices SDK, and the modules reportedly do update to the latest deployment. However, the portal continues to show older deployment data. I have not shared specific error messages or device IDs, and the environment details are not fully specified.

Environment

Azure IoT Hub used for device/module deployment management. Client/application stack: C# (.NET) with the Microsoft.Azure.Devices SDK. SDK version: 1.4.

What I've already tried

The device modules themselves do receive and apply the latest deployment information. No specific troubleshooting steps or support interactions are documented. The troubleshooting guidance suggests checking SDK version, deployment start time, targeting, manifest validity, and device-side logs, but it is unclear if these checks were performed.

Current status

Currently, the device side reflects the latest deployment, but the Azure portal Devices view does not update to show this change. I am seeking guidance on why the portal might be out of sync and how to resolve this discrepancy. I'm sure it is because of a change on the IoT Hub side that needs investigation by the IoT Hub Team.

Suhail Ahamed J 0 Reputation points Microsoft External Staff Moderator

2026-10-08T11:47:59.6933333+00:00
Hello @Davy Meybos ,
Greetings,
Below is the resolution for the issue where Azure IoT Hub's portal is not reflecting the latest deployment information, despite successful updates on your devices.
Root Cause Possibilities:

Device Twin Synchronization Issues: If the device/module twin’s reported properties haven't been updated properly, the portal will show outdated information.

Portal Synchronization Delays: Latency or caching in the portal view may result in data not updating in real-time.

Deployment or Manifest Issues: Invalid targeting conditions or a misconfigured manifest can cause discrepancies.

SDK or Environment Issues: Outdated SDK versions or device-side code might impact updates to the IoT Hub.

Recommended Steps to Resolve:

Verify Device Twin Synchronization

Check the current reported properties of the module twin programmatically using the Microsoft.Azure.Devices SDK:
var registryManager = RegistryManager.CreateFromConnectionString("<IoT Hub Connection String>"); var twin = await registryManager.GetTwinAsync("<DeviceId>", "<ModuleId>"); Console.WriteLine($"Reported Properties: {twin.Properties.Reported.ToJson()}");
Ensure the properties reflect the latest deployment information.

If they don’t, update reported properties explicitly from the device or module side:

var moduleClient = ModuleClient.CreateFromConnectionString("<Connection String>"); await moduleClient.UpdateReportedPropertiesAsync(report);

2. Refresh Portal and Query Status Programmatically

Force a refresh of the Azure portal by manually selecting the "Refresh" button in the IoT Hub > Devices pane.

Alternatively, query the device/module twin status using the Azure CLI instead of relying on the portal:
az iot hub module-twin show --device-id <deviceId> --hub-name <IoTHubName> --module-id <moduleId>

3. Validate SDK Version and Debug Device Logs

Ensure you are using the latest version of the Microsoft.Azure.Devices SDK (recommendation: 1.40.3 or above). Update the SDK via NuGet if necessary:

dotnet add package Microsoft.Azure.Devices --version 1.40.3

Check device-side logs (or Edge agent logs if applicable) to confirm connectivity, authentication, and proper reporting of deployment information.

4. Ensure Deployment Targeting and Manifest Validity

Review deployment targeted criteria (e.g., tags, device IDs) to confirm they match the intended devices.

Validate the deployment manifest against IoT Hub logs (az monitor) and ensure it applies correctly without errors.

5. Address Portal Caching Issues

Clear your browser cache or use private/incognito mode when accessing the Azure portal to eliminate possible caching issues.

6. Escalate to Azure Support If Needed

If the issue persists despite following the above steps, this could indicate a backend synchronization issue with IoT Hub. Please open a support request via the Azure Portal’s Help + Support section for further investigation.

Let us know if you require additional guidance or if new details arise during your troubleshooting. We're here to assist as needed.

Thanks,

1 answer

Your answer

Answer 1

If the device/module twin and SDK/API query show the new deployment while only the portal shows old information, treat this primarily as a portal/UI synchronization or display issue and raise a Microsoft support case with the IoT Hub name, Device/Module ID, deployment ID, timestamp, region, SDK version, and screenshots.

Recommendation:

Check the device/module twin directly and compare desired versus reported properties and their versions. This establishes whether IoT Hub itself has the latest state.
Verify that the application is updating the correct IoT Hub, Device ID, Module ID and deployment/configuration.
If the twin is correct but the Azure portal remains stale, refresh/reopen the portal view and allow time for deployment metrics/configuration evaluation to update.
Reproduce using the Azure CLI or IoT Hub SDK to distinguish a portal display issue from an IoT Hub backend issue. Microsoft supports managing/querying twins through both the portal and CLI.
Upgrade/test with a current supported Microsoft Azure IoT SDK if the reported SDK version is genuinely 1.4, since the environment should be validated against current SDK support before escalating. Azure IoT Hub provides separate device, service and management SDKs.