如何设置Azure IoT Hub系统属性？及解决消息未附加系统属性导致Blob存储路由异常问题

Hey there, let's work through this issue you're facing with Azure message properties and Blob storage routing!

First, let's clarify a key point: the system properties you set in the Test/Properties interface are usually only for the test messages you send directly from that interface. They won't automatically apply to messages sent through your production routing workflows. That's probably why you're seeing the properties show up correctly in tests but not in actual routing scenarios.

Here's what you can do to fix this:

• Set properties at the message source
  No matter if you're using Logic Apps, Azure Functions, or custom code to send messages, you need to explicitly add these system properties in your actual sending logic:

  • For code-based sending (e.g., C#), you'd set properties like this:

    var message = new ServiceBusMessage(JsonSerializer.Serialize(yourPayload))
    {
        ContentType = "application/json",
        ContentEncoding = "utf-8"
    };
    

  • For low-code tools like Logic Apps, look for the "Advanced options" section in your "Send message" action, then add these properties under the "System properties" dropdown.

• Verify message properties before routing
  Use Azure Portal's message peek feature (in your Service Bus queue/topic, for example) to check if the messages actually carry these properties before they get routed. If they don't, double-check your sending configuration—there's a chance the properties aren't being applied correctly at the source.

• Check Blob routing behavior
  When routing to Blob storage, Azure uses these system properties to handle the content appropriately. If the properties are missing, it might default to a generic content type, which can cause issues with how the blob is stored or accessed. Ensuring the properties are present at the source will make the routing process behave as expected.

• Watch out for property loss during forwarding
  If your messages are passing through intermediate services (like Event Grid or another messaging service), make sure those services don't strip away system properties. Some services have default settings that filter non-standard properties, so you may need to adjust configurations to preserve contentType and contentEncoding.

Once you've added these properties to your actual message sending workflow, they should carry through to the Blob storage routing process and resolve your issue.

内容的提问来源于stack exchange，提问作者Traderjoe