Merge pull request #311835 from MicrosoftDocs/main

Auto Publish – main to live - 2026-02-15 23:00 UTC

Author: learn-build-service-prod[bot]

articles/iot-edge/how-to-access-host-storage-from-module.md

@@ -87,7 +87,7 @@ On version 1.4 and newer, there's no need for manually setting ownership or perm
 
 If your custom module requires access to persistent storage on the host file system, use the module's create options to bind a storage folder in module container to a folder on the host machine.
 
-You can use a bind mount or a volume mount. A bind mount allows you to specify a host directory to be mounted into the module container. A volume mount allows you to specify a volume that is managed by Docker. For more information about when to use bind mounts or volume mounts, see the Docker documentation for [volume mounts](https://docs.docker.com/engine/storage/volumes) and [bind mounts](https://docs.docker.com/storage/bind-mounts).
+You can use a bind mount or a volume mount. A bind mount allows you to specify a host directory to be mounted into the module container. A volume mount allows you to specify a volume that is managed by Docker. For more information about when to use bind mounts or volume mounts, see the Docker documentation for [volume mounts](https://docs.docker.com/engine/storage/volumes) and [bind mounts](https://docs.docker.com/engine/storage/bind-mounts/).
 
 The following example shows how to use a bind mount in the module's create options:
 
@@ -107,7 +107,7 @@ The following example shows how to use a bind mount in the module's create optio
 }
 ```
 
-Replace `<HostStoragePath>` and `<ModuleStoragePath>` with your host and module storage path; both values must be an absolute path. Refer to the [Docker Engine Mount specification](https://any-api.com/docker_com/engine/docs/Definitions/Mount) for option details.
+Replace `<HostStoragePath>` and `<ModuleStoragePath>` with your host and module storage path; both values must be an absolute path. Refer to the [Docker Engine storage documentation](https://docs.docker.com/engine/storage/bind-mounts/) for option details.
 
 ### Host system permissions
 

articles/iot-edge/how-to-collect-and-transport-metrics.md

@@ -90,7 +90,7 @@ All configuration for the metrics-collector is done using environment variables.
 | `ScrapeFrequencyInSecs` | Recurring time interval in seconds at which to collect and transport metrics.<br><br>  Example: *600* <br><br>  **Not required** <br><br> Default value: *300* |
 | `MetricsEndpointsCSV` | Comma-separated list of endpoints to collect Prometheus metrics from. All module endpoints to collect metrics from must appear in this list.<br><br>  Example: *http://edgeAgent:9600/metrics, http://edgeHub:9600/metrics, http://MetricsSpewer:9417/metrics* <br><br>  **Not required** <br><br> Default value: *http://edgeHub:9600/metrics, http://edgeAgent:9600/metrics* |
 | `AllowedMetrics` | List of metrics to collect, all other metrics are ignored. Set to an empty string to disable. For more information, see [Allow and disallow lists](#allow-and-disallow-lists). <br><br>Example: *metricToScrape{quantile=0.99}[endpoint=http://MetricsSpewer:9417/metrics]*<br><br>  **Not required** <br><br> Default value: *empty* |
-| `BlockedMetrics` | List of metrics to ignore. Overrides *AllowedMetrics*, so a metric is reported if it's included in both lists. For more information, see [Allow and disallow lists](#allow-and-disallow-lists). <br><br>   Example: *metricToIgnore{quantile=0.5}[endpoint=http://VeryNoisyModule:9001/metrics], docker_container_disk_write_bytes*<br><br>  **Not required**  <br><br>Default value: *empty* |
+| `BlockedMetrics` | List of metrics to ignore. Overrides *AllowedMetrics*, so a metric isn't reported if it's included in both lists. For more information, see [Allow and disallow lists](#allow-and-disallow-lists). <br><br>   Example: *metricToIgnore{quantile=0.5}[endpoint=http://VeryNoisyModule:9001/metrics], docker_container_disk_write_bytes*<br><br>  **Not required**  <br><br>Default value: *empty* |
 | `CompressForUpload` | Controls if compression should be used when uploading metrics. Applies to all upload targets.<br><br>  Example: *true* <br><br>    **Not required** <br><br>  Default value: *true* |
 | `AzureDomain` | Specifies the top-level Azure domain to use when ingesting metrics directly to Log Analytics. <br><br>  Example: *azure.us* <br><br>    **Not required** <br><br>  Default value: *azure.com* |
 

articles/iot-edge/troubleshoot-iot-edge-for-linux-on-windows.md

@@ -84,14 +84,11 @@ Second, the issue could be related to lack of resources. You can set the *EflowV
     Get-CIMInstance Win32_OperatingSystem | Select FreePhysicalMemory
     ```
 1. Check the available CPU cores. Make sure that *NumberOfLogicalProcessors* is greater than *EflowVmAssignedCPUcores*.
-   ```powershell
-    wmic cpu get NumberOfLogicalProcessors
-    ```ssignedCPUcores*.
    ```powershell
     wmic cpu get NumberOfLogicalProcessors
     ```
 
-Finally, the issue might be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-common-errors.md).
+Finally, the issue might be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-iot-edge-for-linux-on-windows-networking.md).
 
 ## Check the status of the IoT Edge runtime
 

articles/iot-edge/tutorial-deploy-custom-vision.md

@@ -555,7 +555,6 @@ The final deployment manifest looks similar to the following:
       "properties.desired": {
         "schemaVersion": "1.2",
         "routes": {
-          "sensorToclassifier": "FROM /messages/modules/tempSensor/outputs/temperatureOutput INTO BrokeredEndpoint(\"/modules/classifier/inputs/input1\")",
           "classifierToIoTHub": "FROM /messages/modules/classifier/outputs/* INTO $upstream",
           "cameracaptureToIoTHub": "FROM /messages/modules/cameracapture/outputs/* INTO $upstream"
         },

articles/iot-edge/using-private-link.md

@@ -45,17 +45,32 @@ When Private Link is enabled, you must configure IoT Edge to use the **private e
 | Azure Container Registry (ACR) | `<registry>.azurecr.io` | `<registry>.privatelink.azurecr.io` | Use Private Link FQDN |
 | Storage (Blob) | `<account>.blob.core.windows.net` | `<account>.privatelink.blob.core.windows.net` | Use Private Link FQDN |
 
-#### Example IoT Edge `config.yaml`
+#### Example IoT Edge `config.toml` (DPS provisioning)
+
+```toml
+# DPS provisioning with symmetric key
+[provisioning]
+source = "dps"
+global_endpoint = "https://global.privatelink.azure-devices-provisioning.net"
+id_scope = "<scope-id>"
+
+[provisioning.attestation]
+method = "symmetric_key"
+registration_id = "<registration-id>"
+symmetric_key = { value = "<symmetric-key>" }
+```
+
+#### Example IoT Edge `config.toml` (manual provisioning)
 
-```yaml
-provisioning:
-  source: "dps"
-  global_endpoint: "global.privatelink.azure-devices-provisioning.net"
-  scope_id: "<scope-id>"
+```toml
+[provisioning]
+source = "manual"
+iothub_hostname = "<hubname>.privatelink.azure-devices.net"
+device_id = "<device-id>"
 
-agent:
-  env:
-    IOTEDGE_IOTHUBHOSTNAME: "<hubname>.privatelink.azure-devices.net"
+[provisioning.authentication]
+method = "sas"
+device_id_pk = { value = "<shared-access-key>" }
 ```
 
 #### DNS requirement