pricing of IoT Hub build-in event hub endpoint

Question

Hello,

I have a question about the IoT Hub message pricing.

The IoT Hub has a build-in event hub endpoint to which the messages are routed by default https://learn.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-messages-d2c#built-in-endpoint-as-a-routing-endpoint. If we send D2C messages and read them with an app from the build-in endpoint, does it count as one message or two? So if we send 1000 messages a day and consume each of them from the build-in endpoint, are we charged for 2000 messages?

Answer 1

Hello @Victor Be This is a great question!

So if we send 1000 messages a day and consume each of them from the build-in endpoint, are we charged for 2000 messages?

No, please see the below section.

Updated:04/13/2021 PDT removed confusing sentences related to this query.
IoTHub will not charge for egress for built-in EventHub, please see the below-quoted message for better clarification. For a full list of metrics counts, please see the section on Monitoring Azure IoT Hub data reference and Monitoring Azure IoT Hub.
The most important section to follow and understand is : Charges per operation

Please don't be confused with charged quota and metrics being displayed!

IoT Hub does not charge for egress. The messages will be counted towards quota only once.
yes, services used downstream will be charged per their pricing, but IoT Hub will not use up quota if you pull data from built-in EH or even if you route it out. No charge for routing, but custom endpoint service will charge per use.

Below example will help in checking the metrics on Azure Portal: For quick testing purposes, please make use of online simulator+Azure IoT Device connection string to send simulated telemetry to IoTHub.

-->I have sent total 97 telemetry messages from the online simulator and I read only 1 telemetry message from the backend application using the IoT Explorer tool.
So assume that a total of 98 would be the message count, but the metrics can be tracked on Azure Portal quickly, please see the below screenshots.

Sending...

Reading...

Metrics on Azure Portal:

Actual Telemetry sent:

One of the other Metrics which are included as part of the above testing: because I have initiated my backend application to list available devices in the IoTHub.

Please leverage the IoTHub Azure Portal and verify quickly from your side as well.

Also visit the examples on this page: Example#1, Example#2

Please leave a comment in the below section if you have further questions in this matter, happy to help!

If the response is helpful, please click "Accept Answer" and upvote it so that it is helpful to others as well!