Hello @Harman,
the short answer is that EventHub messages follow this EventData format.
This means that next to a message body, either devices or any service between the device and the EventHub van add Application properties (a property bag, key-value pairs). This could be the IoT Hub (e.g. using IoT Hub message enrichment)
There are also system properties but these properties are reserved for Azure resources.
Unfortunately, the Azure Data Explorer data connections (eg. IoT Hub ingest of Event Hub data ingest) do not support application properties yet!
So, if you want to ingest application properties next to the message body, you need to transform the incoming messages using services like Azure Functions or Azure Stream Analytics.
An alternative is using the Azure Data Explorer SDK so you can construct completely newly structured messages.
This could also be used in an Azure Function as an alternative for the message count, eg. in combination with a static counter variable.
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.