Hello @Hinata Katsunori ,
as @AshokPeddakotla-MSFT already mentioned, by adding multiple routes, the same incoming message can be 'duplicated' to multiple endpoints, including Azure (Blob) storage.
There is one little thing that could give the wrong impression.
If you connect an Azure function using the IoT HUb trigger, you probably use the 'event hub compatible endpoint'.
This endpoint is used to stream all telemetry to services:
But, if you add a first route (like one sending data to the blob storage endpoint) the 'event hub compatible endpoint' turns into a fall-back endpoint:
So, it only gets the messages not picked up by other routes...
Because all messages are sent to the blob storage, your Azure function is not receiving any data ...
This fallback route is a great addition but in your case, you just want a copy sent to the default event endpoint.
Luckily, there is a simple solution.
Just add a second route, sending all data to this pre-defined 'events' endpoint:
This just represents the endpoint and overrules the fallback functionality.
This way, you both store telemetry in storage and have an Azure function react to real-time data:
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.