Merge pull request #312407 from jlian/fix/wasm-doc-bugs-batch1

Fix critical bugs in WASM dataflow docs (e2e verified)

Author: JamesJBarnett

articles/iot-operations/connect-to-cloud/howto-dataflow-graph-wasm.md

@@ -6,7 +6,7 @@ ms.author: sethm
 ms.service: azure-iot-operations
 ms.subservice: azure-data-flows
 ms.topic: how-to
-ms.date: 02/25/2026
+ms.date: 02/27/2026
 ai-usage: ai-assisted
 
 ---
@@ -888,20 +888,12 @@ In the data flow diagram, select **Add graph transform (optional)** to add a gra
     artifact: 'temperature-converter:2.1.0'
     configuration: [
       {
-        key: 'input-unit'
-        value: 'fahrenheit'
+        key: 'temperature_lower_bound'
+        value: '-40'
       }
       {
-        key: 'output-unit' 
-        value: 'celsius'
-      }
-      {
-        key: 'precision'
-        value: '2'
-      }
-      {
-        key: 'enable-filtering'
-        value: 'true'
+        key: 'temperature_upper_bound'
+        value: '3422'
       }
     ]
   }
@@ -917,14 +909,10 @@ In the data flow diagram, select **Add graph transform (optional)** to add a gra
     registryEndpointRef: my-acr-endpoint
     artifact: temperature-converter:2.1.0
     configuration:
-      - key: input-unit
-        value: fahrenheit
-      - key: output-unit
-        value: celsius
-      - key: precision
-        value: "2"
-      - key: enable-filtering
-        value: "true"
+      - key: temperature_lower_bound
+        value: "-40"
+      - key: temperature_upper_bound
+        value: "3422"
 ```
 
 ---
@@ -936,6 +924,9 @@ You pass the configuration key-value pairs to the WASM module at runtime. The mo
 - Enable or disable features based on deployment requirements.
 - Set environment-specific values like thresholds or endpoints.
 
+> [!IMPORTANT]
+> Check your WASM module's documentation or source code for required configuration parameters. If a module expects specific parameters (such as filter bounds or thresholds) and you don't provide them, the module may fail at runtime. For details on defining parameters in graph definitions, see [Module configuration parameters](../develop-edge-apps/howto-configure-wasm-graph-definitions.md#module-configuration-parameters).
+
 #### Destination nodes
 
 Destination nodes define where processed data is sent. They connect to data flow endpoints that send data to MQTT brokers, cloud storage, or other systems. Each destination node specifies:
@@ -1130,6 +1121,11 @@ If you deploy the data flow graph but it doesn't process messages:
 
 ## Related content
 
+- [Develop WebAssembly modules](../develop-edge-apps/howto-develop-wasm-modules.md) for writing operators in Rust and Python (includes quickstart)
+- [Configure WebAssembly graph definitions](../develop-edge-apps/howto-configure-wasm-graph-definitions.md) for graph YAML structure and configuration parameters
+- [Deploy WASM modules and graph definitions](../develop-edge-apps/howto-deploy-wasm-graph-definitions.md) for registry setup and artifact management
+- [Build WASM modules with VS Code extension](../develop-edge-apps/howto-build-wasm-modules-vscode.md) for IDE-based development
+- [Run ONNX inference in WASM](../develop-edge-apps/howto-wasm-onnx-inference.md) for ML model integration
 - [Configure MQTT data flow endpoints](howto-configure-mqtt-endpoint.md)
 - [Configure Azure Event Hubs and Kafka data flow endpoints](howto-configure-kafka-endpoint.md)
 - [Configure Azure Data Lake Storage data flow endpoints](howto-configure-adlsv2-endpoint.md)

articles/iot-operations/develop-edge-apps/howto-configure-wasm-graph-definitions.md

@@ -266,23 +266,33 @@ For detailed instructions on uploading graph definitions and WASM modules to reg
 
 ## Module configuration parameters
 
-Graph definitions can specify runtime parameters for WASM operators through module configurations:
+Graph definitions can specify runtime parameters for WASM operators through module configurations. These parameters are passed to your operator's `init` function at runtime, enabling dynamic configuration without rebuilding modules.
+
+> [!IMPORTANT]
+> If a WASM operator requires configuration parameters and you don't provide them in `moduleConfigurations`, the operator may fail at runtime. Always check the operator's documentation or source code for required parameters.
+
+The following example shows module configurations for the [temperature sample](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm/operators/temperature) used in the complex graph:
 
 ```yaml
 moduleConfigurations:
-  - name: my-operator/map
+  - name: module-temperature/map
     parameters:
-      threshold:
-        name: temperature_threshold
-        description: "Temperature threshold for filtering"
-        required: true
-      unit:
-        name: output_unit
-        description: "Output temperature unit"
-        required: false
+      key1:
+        name: key1
+        description: "Example parameter passed to the map operator's init function"
+  - name: module-temperature/filter
+    parameters:
+      temperature_lower_bound:
+        name: temperature_lower_bound
+        description: "Minimum valid temperature in Celsius (default: -40)"
+      temperature_upper_bound:
+        name: temperature_upper_bound
+        description: "Maximum valid temperature in Celsius (default: 3422)"
 ```
 
-These parameters are passed to your WASM operator's `init` function at runtime, enabling dynamic configuration without rebuilding modules. For detailed examples of how to access and use these parameters in your Rust and Python code, see [Module configuration parameters](howto-develop-wasm-modules.md#module-configuration-parameters).
+The `name` field in each configuration entry must match the operator name defined in the graph's `operations` section. Each parameter under `parameters` becomes a key-value tuple in the `configuration.properties` list that your operator's `init` function receives.
+
+For detailed examples of how to access and use these parameters in your Rust and Python code, see [Module configuration parameters](howto-develop-wasm-modules.md#module-configuration-parameters).
 
 For a complete implementation example, see the [branch module](https://github.com/Azure-Samples/explore-iot-operations/tree/main/samples/wasm-python/operators/branch), which demonstrates parameter usage for conditional routing logic.
 

articles/iot-operations/develop-edge-apps/howto-deploy-wasm-graph-definitions.md

@@ -189,6 +189,8 @@ For detailed information about creating and configuring the YAML graph definitio
 
 ## Related content
 
-- [Configure WebAssembly graph definitions](../develop-edge-apps/howto-configure-wasm-graph-definitions.md)
-- [Develop WebAssembly modules for data flow graphs](../develop-edge-apps/howto-develop-wasm-modules.md)
+- [Develop WebAssembly modules](howto-develop-wasm-modules.md) for writing operators in Rust and Python (includes end-to-end quickstart)
+- [Configure WebAssembly graph definitions](howto-configure-wasm-graph-definitions.md) for graph YAML structure and configuration parameters
+- [Use WebAssembly with data flow graphs](../connect-to-cloud/howto-dataflow-graph-wasm.md) for DataflowGraph resource configuration and examples
+- [Build WASM modules with VS Code extension](howto-build-wasm-modules-vscode.md) for IDE-based development
 - [Configure registry endpoints](howto-configure-registry-endpoint.md)