Document Details
Tutorial Message Enrichments
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Detected Bias Types
missing_linux_example
windows_tools
windows_first
Summary
The documentation provides instructions for using the Azure portal and Azure CLI, which are cross-platform. However, the only code sample for simulating a device is a .NET console application (SimulatedDevice), which is Windows-centric by default and lacks explicit Linux instructions or alternatives. There are no examples using Linux-native tools (such as Python, Bash, or MQTT CLI clients), and the documentation assumes familiarity with Windows development patterns. The sample path and instructions (e.g., `/iot-hub/Tutorials/Routing/SimulatedDevice/` and editing `Program.cs`) are also more familiar to Windows/.NET users.
Recommendations
- Provide a Linux-native example for simulating device messages, such as using Python, Bash, or an MQTT CLI tool (e.g., mosquitto_pub).
- Explicitly mention that the .NET sample can be run on Linux using .NET Core, and provide installation instructions if needed.
- Include file path examples and instructions that are platform-agnostic or show both Windows and Linux path formats.
- Offer alternative code samples in other languages commonly used on Linux (e.g., Python, Node.js) for sending device messages.
- Clarify that the Azure CLI commands work on all platforms and, if any step is platform-specific, provide equivalent instructions for both Windows and Linux.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
 Clean
|
| 2026-01-13 00:00 | #246 | completed |
Clean
|
| 2026-01-11 00:00 | #240 | completed |
Clean
|
| 2026-01-10 00:00 | #237 | completed |
Clean
|
| 2026-01-09 00:34 | #234 | completed |
Clean
|
| 2026-01-08 00:53 | #231 | completed |
Clean
|
| 2026-01-06 18:15 | #225 | cancelled |
Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Clean
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-09 13:09 | #3 | cancelled |
Clean
|
| 2025-07-08 04:23 | #2 | cancelled |
Biased
|
Flagged Code Snippets
After leaving the console application to run for a few minutes, view the data: 1. In the [Azure portal](https://portal.azure.com), navigate to your storage account. 1. Select **Storage browser** from the navigation menu. Select **Blob containers** to see the two containers that you created over the course of these tutorials. :::image type="content" source="./media/tutorial-message-enrichments/show-blob-containers.png" alt-text="Screenshot showing the blob containers in the storage account."::: The messages in the container called **enriched** have the message enrichments included in the messages. The messages in the container you created earlier have the raw messages with no enrichments. Drill down into the **enriched** container until you get to the bottom and then open the most recent message file. Then do the same for the other container to verify that one is enriched and one isn't. When you look at messages that have been enriched, you should see `"myIotHub"` with the hub name, the location, and the customer ID, like this: