Fix code-breaking bugs in WASM dataflow docs

- Fix temperature conversion direction (C→F → F→C) to match function name and all other docs
- Fix Rust SDK reference: configuration.parameters.get() → configuration.properties with tuple iteration
- Fix Python SDK reference: remove fictional configuration.get_parameter() API, use properties tuples
- Fix debug snippet: fn filter(message:) → fn filter(input:) to match variable usage
- Fix RegistryEndpoint API version: v1beta1 → v1 (only version served by CRD)
- Fix 'ONNX interference' → 'ONNX inference' typo in section header
- Fix Bicep customLocations API versions: 2021-08-31-15 and 2021-08-15 → 2021-08-31-preview

Author: jlian

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: 01/15/2026
+ms.date: 02/25/2026
 ai-usage: ai-assisted
 
 ---
@@ -134,7 +134,7 @@ resource aioInstance 'Microsoft.IoTOperations/instances@2025-10-01' existing = {
   name: aioInstanceName
 }
 
-resource customLocation 'Microsoft.ExtendedLocation/customLocations@2021-08-31-15' existing = {
+resource customLocation 'Microsoft.ExtendedLocation/customLocations@2021-08-31-preview' existing = {
   name: customLocationName
 }
 
@@ -406,7 +406,7 @@ resource aioInstance 'Microsoft.IoTOperations/instances@2025-10-01' existing = {
   name: aioInstanceName
 }
 
-resource customLocation 'Microsoft.ExtendedLocation/customLocations@2021-08-15' existing = {
+resource customLocation 'Microsoft.ExtendedLocation/customLocations@2021-08-31-preview' existing = {
   name: customLocationName
 }
 

articles/iot-operations/develop-edge-apps/howto-build-wasm-modules-vscode.md

@@ -4,7 +4,7 @@ description: Learn how to build WebAssembly (WASM) modules for data flows using
 author: dominicbetts 
 ms.author: dobett 
 ms.topic: how-to
-ms.date: 12/08/2025
+ms.date: 02/25/2026
 ms.service: azure-iot-operations
 
 # CustomerIntent: As a developer, I want to understand how to use the VS Code extension to build and deploy WASM modules to use in data flow graphs or the HTTP/REST connector.
@@ -480,7 +480,7 @@ Complete the [Schema registry support for WASM modules](#schema-registry-support
 1. Locate the `filter` function and set a breakpoint by clicking in the margin next to the line number or by pressing `F9`.
 
     ```rust
-    fn filter(message: DataModel) -> Result<bool, Error> {
+    fn filter(input: DataModel) -> Result<bool, Error> {
         let DataModel::Message(message) = input else {
             return Err(Error {message: "Unexpected input type.".to_string()});
         };

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

@@ -5,7 +5,7 @@ author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot-operations
 ms.topic: how-to
-ms.date: 12/16/2025
+ms.date: 02/25/2026
 ai-usage: ai-assisted
 
 ---
@@ -68,7 +68,7 @@ resource publicRegistryEndpoint 'Microsoft.IoTOperations/instances/registryEndpo
 # [Kubernetes](#tab/kubernetes)
 
 ```yaml
-apiVersion: connectivity.iotoperations.azure.com/v1beta1
+apiVersion: connectivity.iotoperations.azure.com/v1
 kind: RegistryEndpoint
 metadata:
   name: public-ghcr

articles/iot-operations/develop-edge-apps/howto-develop-wasm-modules.md

@@ -6,7 +6,7 @@ ms.author: dobett
 ms.service: azure-iot-operations
 ms.subservice: azure-data-flows
 ms.topic: how-to
-ms.date: 12/08/2025
+ms.date: 02/25/2026
 ai-usage: ai-assisted
 ---
 
@@ -247,7 +247,7 @@ Python WASM modules don't require other project configuration files. The Python
 
 ## Create a simple module
 
-Create a simple module that converts temperature from Celsius to Fahrenheit. This example demonstrates the basic structure and processing logic for both Rust and Python implementations.
+Create a simple module that converts temperature from Fahrenheit to Celsius. This example demonstrates the basic structure and processing logic for both Rust and Python implementations.
 
 # [Rust](#tab/rust)
 
@@ -274,10 +274,10 @@ fn fahrenheit_to_celsius(input: DataModel) -> Result<DataModel, Error> {
     if let Ok(data_str) = std::str::from_utf8(payload) {
         if let Ok(mut data) = serde_json::from_str::<Value>(data_str) {
             if let Some(temp) = data["temperature"]["value"].as_f64() {
-                let fahrenheit = (temp * 9.0 / 5.0) + 32.0; // Celsius -> Fahrenheit
+                let celsius = (temp - 32.0) * 5.0 / 9.0; // Fahrenheit -> Celsius
                 data["temperature"] = json!({
-                    "value_fahrenheit": fahrenheit,
-                    "original_celsius": temp
+                    "value_celsius": celsius,
+                    "original_fahrenheit": temp
                 });
 
                 if let Ok(output_str) = serde_json::to_string(&data) {
@@ -482,16 +482,17 @@ use wasm_graph_sdk::logger::{self, Level};
 use wasm_graph_sdk::ModuleConfiguration;
 
 fn my_operator_init(configuration: ModuleConfiguration) -> bool {
-    // Access required parameters
-    if let Some(threshold_param) = configuration.parameters.get("temperature_threshold") {
-        let threshold: f64 = threshold_param.parse().unwrap_or(25.0);
+    // Access parameters via configuration.properties (a list of key-value tuples)
+    if let Some((_, threshold_value)) = configuration.properties.iter().find(|(k, _)| k == "temperature_threshold") {
+        let threshold: f64 = threshold_value.parse().unwrap_or(25.0);
         logger::log(Level::Info, "my-operator", &format!("Using threshold: {}", threshold));
     }
 
     // Access optional parameters with defaults
-    let unit = configuration.parameters
-        .get("output_unit")
-        .map(|s| s.as_str())
+    let unit = configuration.properties
+        .iter()
+        .find(|(k, _)| k == "output_unit")
+        .map(|(_, v)| v.as_str())
         .unwrap_or("celsius");
 
     logger::log(Level::Info, "my-operator", &format!("Output unit: {}", unit));
@@ -556,9 +557,14 @@ from map_impl.imports import types
 # Implement the operator interface
 class Map(exports.Map):
     def init(self, configuration) -> bool:
-        # Access configuration parameters
-        threshold = configuration.get_parameter("temperature_threshold")
-        unit = configuration.get_parameter("output_unit", default="celsius")
+        # Access configuration parameters via configuration.properties (list of key-value tuples)
+        threshold = None
+        unit = "celsius"
+        for key, value in configuration.properties:
+            if key == "temperature_threshold":
+                threshold = value
+            elif key == "output_unit":
+                unit = value
 
         imports.logger.log(imports.logger.Level.INFO, "my-operator", 
                           f"Initialized with threshold={threshold}, unit={unit}")

articles/iot-operations/develop-edge-apps/howto-wasm-onnx-inference.md

@@ -5,7 +5,7 @@ author: dominicbetts
 ms.author: dobett
 ms.service: azure-iot-operations
 ms.topic: how-to
-ms.date: 11/24/2025
+ms.date: 02/25/2026
 ai-usage: ai-assisted
 
 ---
@@ -17,7 +17,7 @@ This article shows how to embed and run small Open Neural Network Exchange (ONNX
 > [!IMPORTANT]
 > Data flow graphs currently only support MQTT (Message Queuing Telemetry Transport), Kafka, and OpenTelemetry endpoints. Other endpoint types like Data Lake, Microsoft Fabric OneLake, Azure Data Explorer, and Local Storage aren't supported. For more information, see [Known issues](../troubleshoot/known-issues.md#data-flow-graphs-only-support-specific-endpoint-types).
 
-## Why use in-band ONNX interference
+## Why use in-band ONNX inference
 
 With Azure IoT Operations data flow graphs, you can embed small ONNX model inference directly in the pipeline instead of calling an external prediction service. This approach offers several practical advantages: