IoT Central Export to Azure Event Hub Stuck in “Waiting” State

Hello Priyanshu Aggarwal,

It sounds like you're having a bit of trouble with your Azure IoT Central export to Azure Event Hub getting stuck in a "Waiting" state. That can be frustrating, especially with everything else set up and apparently functional. Here are a few things you can check to try to resolve this issue:

1. Managed Identity Permissions: Make sure that the system-assigned managed identity for your IoT Central application has been granted the necessary permissions for Azure Event Hubs. Specifically, it should have the "Azure Event Hubs Data Sender" role assigned to it. You can verify this in the Azure portal under the "Identity" section of your IoT Central application.
2. Connection String: If you're using a connection string instead of the managed identity, ensure that it's correctly set up and that the event hub name is case-sensitive. If using a managed identity, connections through simulated devices are not supported as well.
3. Diagnostic Settings: Be sure that your diagnostic settings are correctly defined. This includes routing the metrics and logs to the Event Hub. If any of the diagnostic settings are missing, it could impact the ability to export data.
4. Check the Export Status: On the "Data export" page in IoT Central, look for any status messages or metrics that might indicate why the export is stuck. You could use Azure Monitor to look for metrics like the number of messages being exported, number of messages successfully exported, etc.
5. Wait Time: Sometimes, it can take up to 60 seconds for the messages to be exported from IoT Central to your destination. If you’re testing with a quick timeline, ensure that you allow sufficient time before checking state changes.

If after all of these steps the export destination still remains in "Waiting," it may be helpful to review the health of both the IoT Central application and Event Hubs for any potential issues.

Hope this helps!
Thank you!

Thank you for the detailed suggestions — much appreciated!

Just to clarify, we’ve already reviewed and implemented most of the steps you mentioned. Here's a summary of the current state:

✅ Managed Identity Permissions: The system-assigned managed identity of the IoT Central application has been granted the Azure Event Hubs Data Sender role at the namespace level. This was confirmed through Azure Portal → IAM.

1. ✅ Connection String: We are not using a connection string — the export is configured to use managed identity only. Also, the Event Hub name is correctly spelled and case-verified.

❌ Diagnostic Settings: As this is a telemetry data export from IoT Central to Event Hub, diagnostic settings are not required in this path. This feature is handled internally by IoT Central’s export pipeline.

✅ Export Status Monitoring: The export destination remains stuck in "Waiting", and no error messages appear. We also checked Event Hub metrics, and no incoming messages have been received so far, confirming that no data is being exported yet.

✅ Wait Time Consideration: We’ve waited well beyond the expected propagation time (15+ minutes) after assigning the roles — yet the destination status has not changed from "Waiting".

🔄 Health Check: Both the IoT Central app and Event Hub are active and healthy with no service alerts or region issues.

Hello Priyanshu Aggarwal,

I understand you cannot connect using a system-assigned managed identity.

It could be that there is a managed identity hiccup between IoT Central and eventhub.

Can you first try to connect your IoT Central to the evenhub using a connectionstring to the same EventHub namespace to check if the connection can be made that way?

Or try to use another type of target to check it that one is working.

Hello @VSawhney and @Sander van de Velde | MVP ,we have the same issue creating an "Azure blob storage" destination, we put container name and right connection string for a storage General Purpose V2 - Standard, but after creation the destination remains in "waiting" state.

We have the same issue also configuring a managed identity.

P.S. Some months ago we created an "Azure blob storage" destination in different iot-central organization and it's still working better, but now the same configuration in the same organization with a different container or the same configuration in a different organization remains in a "Waiting" state.
Do you have idea for resolution ?

Hello @VSawhney and @Sander van de Velde | MVP ,we have the same issue creating an "Azure blob storage" destination, we put container name and right connection string for a storage General Purpose V2 - Standard, but after creation the destination remains in "waiting" state.

We have the same issue also configuring a managed identity.

P.S. Some months ago we created an "Azure blob storage" destination in different iot-central organization and it's still working better, but now the same configuration in the same organization with a different container or the same configuration in a different organization remains in a "Waiting" state. Do you have idea for resolution ?