Events with DeviceTelemetry type are no longer sent to EventHub when unauthorized access to IoT Hub is attempted

Piotr Machowski 0

Events with DeviceTelemetry type are no longer sent to EventHub when an unauthorized access to IoT Hub is attempted (with invalid authorization).

This functionality used to work, but at this moment events are no longer visible via servicebus connection nor Stream Analytics

1 answer

Sander van de Velde | MVP 31,021 Reputation points MVP

2024-07-09T16:54:06.06+00:00

Hello @Piotr Machowski,

welcome to this moderated Azure community forum.

Did you by chance create a custom route and endpoint in your IoT Hub?

If so, this probably change the default behavior of the normal (eventhub-compatible) route towards eg. Stream Analytics.

The normal route suddenly acts like a fallback, only passing on message not caught by any other route.

To fix this, just add a route pointing to the 'events' endpoint:

This is marked as a 'built-in' endpoint:

Does this solve your problem?

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.
Please sign in to rate this answer.
Piotr Machowski 0 Reputation points

2024-07-10T14:05:36.4366667+00:00

Hi @Sander van de Velde | MVP ,

thank you for your fast response!

No, I do not use any custom route/endpoint. It is also worth to mention that fallback route is enabled and I still receive other events from IoT Hub in Event Hub, so communication itself works correctly.

Sander van de Velde | MVP 31,021 Reputation points MVP

2024-07-10T18:03:23.2166667+00:00

Ok, lets try to find out where the flow is broken.

The telemetry flow you have is?

iot-hub (via the normal (eventhub compatible) endpoint) -> stream analytics -> event hub

Where should I put servicebus in this flow?

There is not a single custom route created?

Do you use $default as consumer group for the iothub input? If so, please use a new consumer group (like asa) so you know for sure your stream analytics job gets its own copy of each incoming telemetry message.

Can you test the iot hub input (there is a test option in the azure portal).

Piotr Machowski 0 Reputation points

2024-07-11T13:40:36.9133333+00:00

My config looks the following way:

IoT Hub --[configured in Diagnostic Settings]--> Event Hub --[Process data: Real time insights]--> Stream Analytics (preview_data_consumer_group consumer group) --[sb://servicebus.windows.net endpoint]--> My application ($Default consumer group)

There is not a single custom route created?

There are no custom routes/custom endpoints configured in IoT Hub, fallback route is active.

Do you use $default as consumer group for the iothub input? If so, please use a new consumer group (like asa) so you know for sure your stream analytics job gets its own copy of each incoming telemetry message.

I use Real time insights on Azure Portal, it uses preview_data_consumer_group consumer group. My application doesn't specify a consumer group, so I suppose it uses $Default.

Can you test the iot hub input (there is a test option in the azure portal).

I haven't found this option in the portal, could you please specify where to find it? Other types of events (e.g. device statistics) are visible in both Real time insights and my application, so I assume that communication is set up correctly.
Sign in to comment

Share via

Events with DeviceTelemetry type are no longer sent to EventHub when unauthorized access to IoT Hub is attempted

1 answer