Merge pull request #225099 from MicrosoftDocs/release-iotedge-moniker-retirement

Retire IoT Edge 1.1 content

Author: huypub

articles/industrial-iot/TOC.yml

@@ -73,22 +73,6 @@
         href: ../iot-edge/how-to-create-virtual-switch.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
       - name: Configure GPU acceleration
         href: ../iot-edge/gpu-acceleration.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
-    - name: Windows containers on Windows hosts
-      items:
-      - name: Provision a single device
-        items:
-        - name: Symmetric key attestation
-          href: ../iot-edge/how-to-provision-single-device-windows-symmetric.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
-        - name: X.509 certificate attestation
-          href: ../iot-edge/how-to-provision-single-device-windows-x509.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
-      - name: Provision devices at scale
-        items:
-        - name: Symmetric key attestation
-          href: ../iot-edge/how-to-provision-devices-at-scale-windows-symmetric.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
-        - name: X.509 certificate attestation
-          href: ../iot-edge/how-to-provision-devices-at-scale-windows-x509.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
-        - name: TPM attestation
-          href: ../iot-edge/how-to-provision-devices-at-scale-windows-tpm.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
     - name: Update IoT Edge
       href: ../iot-edge/how-to-update-iot-edge.md?toc=/azure/industrial-iot/toc.json&bc=/azure/industrial-iot/breadcrumb/toc.json
     - name: Manage device certificates

articles/iot-dps/how-to-troubleshoot-dps.md

@@ -63,7 +63,7 @@ Use this table to understand and resolve common errors.
 | 400 | The body of the request is not valid; for example, it cannot be parsed, or the object cannot be validated.| 400 Bad format |
 | 401 | The authorization token cannot be validated; for example, it is expired or does not apply to the request's URI. This error code is also returned to devices as part of the TPM attestation flow. | 401 Unauthorized|
 | 404 | The Device Provisioning Service instance, or a resource (e.g. an enrollment) does not exist. | 404 Not Found|
-| 405 | The client service knows the request method, but the target service doesn't recognize this method; for example, a rest operations is missing the enrollment or registration Id parameters | 405 Method Not Allowed |
+| 405 | The client service knows the request method, but the target service doesn't recognize this method; for example, a rest operation is missing the enrollment or registration ID parameters | 405 Method Not Allowed |
 | 409 | The request could not be completed due to a conflict with the current state of the target Device Provisioning Service instance; for example, the customer has already created the data point and is attempting to recreate the same datapoint again. | 409 Conflict |
 | 412 | The ETag in the request does not match the ETag of the existing resource, as per RFC7232. | 412 Precondition failed |
 | 415 | The server refuses to accept the request because the payload format is in an unsupported format. For supported formats, see [Iot Hub Device Provisioning Service REST API](/rest/api/iot-dps/) | 415 Unsupported Media Type |
@@ -72,18 +72,18 @@ Use this table to understand and resolve common errors.
 
 ### Suggested actions
 
-* If an IoT Edge device fails to start with error message `failed to provision with IoT Hub, and no valid device backup was found dps client error`, see [DPS Client error](../iot-edge/troubleshoot-common-errors.md?preserve-view=true&view=iotedge-2018-06#dps-client-error) in the IoT Edge (1.1) documentation.
+* If an IoT Edge device fails to start with error message `failed to provision with IoT Hub, and no valid device backup was found dps client error`, see [DPS Client error](/previous-versions/azure/iot-edge/troubleshoot-common-errors#dps-client-error) in the IoT Edge (1.1) documentation.
 
 * For 401 Unauthorized, 403 Forbidden, or 404 Not Found errors perform a full re-registration by calling the [DPS registration API](/rest/api/iot-dps/device/runtime-registration/register-device).
 
 * For a 429 error, follow the retry pattern of IoT Hub that has exponential backoff with a random jitter. You can follow the retry-after header provided by the SDK.
 
-* For 500-series server errors, retry your [connection](./concepts-deploy-at-scale.md#iot-hub-connectivity-considerations) using cached credentials or a [Device Registration Status Lookup API](/rest/api/iot-dps/device/runtime-registration/device-registration-status-lookup#deviceregistrationresult) call.
+* For 500-series server errors, retry your [connection](/azure/iot-dps/concepts-deploy-at-scale#iot-hub-connectivity-considerations) using cached credentials or a [Device Registration Status Lookup API](/rest/api/iot-dps/device/runtime-registration/device-registration-status-lookup#deviceregistrationresult) call.
 
-For related best practices, such as retrying operations, see [Best practices for large-scale IoT device deployments](./concepts-deploy-at-scale.md).
+For related best practices, such as retrying operations, see [Best practices for large-scale IoT device deployments](/azure/iot-dps/concepts-deploy-at-scale).
 
 ## Next Steps
 
 - To learn more about using Azure Monitor with DPS, see [Monitor Device Provisioning Service](monitor-iot-dps.md).
 
-- To learn about metrics, logs, and schemas emitted for DPS in Azure Monitor, see [Monitoring Device Provisioning Service data reference](monitor-iot-dps-reference.md).
+- To learn about metrics, logs, and schemas emitted for DPS in Azure Monitor, see [Monitoring Device Provisioning Service data reference](monitor-iot-dps-reference.md).

articles/iot-edge/.openpublishing.redirection.iot-edge.json

@@ -234,6 +234,86 @@
             "source_path_from_root": "/articles/iot-edge/how-to-publish-subscribe.md",
             "redirect_url": "/azure/iot-edge/",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-machine-learning-edge-01-intro.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-machine-learning-edge-01-intro",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-machine-learning-edge-02-prepare-environment.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-machine-learning-edge-02-prepare-environment",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-machine-learning-edge-03-generate-data.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-machine-learning-edge-03-generate-data",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-machine-learning-edge-04-train-model.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-machine-learning-edge-04-train-model",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-machine-learning-edge-05-configure-edge-device.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-machine-learning-edge-05-configure-edge-device",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-machine-learning-edge-06-custom-modules.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-machine-learning-edge-06-custom-modules",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-machine-learning-edge-07-send-data-to-hub.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-machine-learning-edge-07-send-data-to-hub",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-develop-for-windows.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-develop-for-windows",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-c-module-windows.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-c-module-windows",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/tutorial-csharp-module-windows.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/tutorial-csharp-module-windows",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/how-to-provision-single-device-windows-x509.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/how-to-provision-single-device-windows-x509",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/how-to-provision-single-device-windows-symmetric.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/how-to-provision-single-device-windows-symmetric",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/how-to-provision-devices-at-scale-windows-x509.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/how-to-provision-devices-at-scale-windows-x509",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/how-to-provision-devices-at-scale-windows-tpm.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/how-to-provision-devices-at-scale-windows-tpm",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/how-to-provision-devices-at-scale-windows-symmetric.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/how-to-provision-devices-at-scale-windows-symmetric",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/iot-edge/reference-windows-scripts.md",
+            "redirect_url": "/previous-versions/azure/iot-edge/reference-windows-scripts",
+            "redirect_document_id": false
         }
     ]
 }

articles/iot-edge/TOC.yml

@@ -16,12 +16,8 @@
     href: quickstart-linux.md
 - name: Tutorials
   items:
-  - name: Set up development environment
-    items:
-    - name: Develop with Linux containers
-      href: tutorial-develop-for-linux.md
-    - name: Develop with Windows containers
-      href: tutorial-develop-for-windows.md
+  - name: Develop with Linux containers
+    href: tutorial-develop-for-linux.md
   - name: Develop custom code modules
     items:
     - name: C
@@ -34,12 +30,6 @@
       href: tutorial-node-module.md
     - name: Python
       href: tutorial-python-module.md
-    - name: Use Windows containers
-      items:
-      - name: C
-        href: tutorial-c-module-windows.md
-      - name: C#
-        href: tutorial-csharp-module-windows.md
   - name: Deploy Azure services as modules
     items:
     - name: Filter data with Azure Functions
@@ -54,22 +44,6 @@
     items:
     - name: Create hierarchies of IoT Edge devices
       href: tutorial-nested-iot-edge.md
-  - name: Machine learning at the edge
-    items:
-    - name: Introduction
-      href: tutorial-machine-learning-edge-01-intro.md
-    - name: Set up development machine and Azure services
-      href: tutorial-machine-learning-edge-02-prepare-environment.md
-    - name: Generate simulated device data
-      href: tutorial-machine-learning-edge-03-generate-data.md
-    - name: Train and deploy an Azure Machine Learning model
-      href: tutorial-machine-learning-edge-04-train-model.md
-    - name: Configure a transparent gateway
-      href: tutorial-machine-learning-edge-05-configure-edge-device.md
-    - name: Create and deploy IoT Edge modules
-      href: tutorial-machine-learning-edge-06-custom-modules.md
-    - name: Send data to IoT Hub via transparent gateway
-      href: tutorial-machine-learning-edge-07-send-data-to-hub.md
   - name: Monitor devices and modules
     href: tutorial-monitor-with-workbooks.md
   - name: Configure EST server
@@ -138,22 +112,6 @@
           href: how-to-provision-devices-at-scale-linux-tpm.md
         - name: Symmetric key attestation
           href: how-to-provision-devices-at-scale-linux-symmetric.md
-    - name: Windows containers on Windows hosts
-      items:
-      - name: Provision a single device
-        items:
-        - name: Symmetric key attestation
-          href: how-to-provision-single-device-windows-symmetric.md
-        - name: X.509 certificate attestation
-          href: how-to-provision-single-device-windows-x509.md
-      - name: Provision devices at scale
-        items:
-        - name: Symmetric key attestation
-          href: how-to-provision-devices-at-scale-windows-symmetric.md
-        - name: X.509 certificate attestation
-          href: how-to-provision-devices-at-scale-windows-x509.md
-        - name: TPM attestation
-          href: how-to-provision-devices-at-scale-windows-tpm.md
     - name: Update IoT Edge
       href: how-to-update-iot-edge.md
     - name: Manage device certificates
@@ -348,10 +306,6 @@
   items:
   - name: Runtime modules environment variables
     href: https://github.com/Azure/iotedge/blob/release/1.4/doc/EnvironmentVariables.md
-  - name: PowerShell functions
-    items:
-    - name: IoT Edge for Windows
-      href: reference-windows-scripts.md
   - name: Create test certificates
     href: how-to-create-test-certificates.md
   - name: Azure CLI

articles/iot-edge/about-iot-edge.md

@@ -2,9 +2,6 @@
 title: What is Azure IoT Edge | Microsoft Docs
 description: Overview of the Azure IoT Edge service
 author: PatAltimore
-
-# this is the PM responsible
-ms.reviewer: chipalost
 ms.service: iot-edge
 services: iot-edge
 ms.topic: overview

articles/iot-edge/configure-connect-verify-gpu.md

@@ -12,6 +12,8 @@ services: iot-edge
 
 # Tutorial: Configure, connect, and verify an IoT Edge module for a GPU
 
+[!INCLUDE [iot-edge-version-1.4](includes/iot-edge-version-1.4.md)]
+
 This tutorial shows you how to build a GPU-enabled virtual machine (VM). From the VM, you'll see how to run an IoT Edge device that allocates work from one of its modules to your GPU. 
 
 We'll use the Azure portal, the Azure Cloud Shell, and your VM's command line to:

articles/iot-edge/gpu-acceleration.md

@@ -2,7 +2,6 @@
 title: GPU acceleration for Azure IoT Edge for Linux on Windows | Microsoft Docs
 description: Learn about how to configure your Azure IoT Edge for Linux on Windows virtual machines to use host device GPUs.
 author: PatAltimore
-manager: kgremban
 ms.author: patricka
 ms.date: 6/7/2022
 ms.topic: conceptual
@@ -12,7 +11,7 @@ services: iot-edge
 
 # GPU acceleration for Azure IoT Edge for Linux on Windows
 
-[!INCLUDE [iot-edge-version-1.1-or-1.4](includes/iot-edge-version-1.1-or-1.4.md)]
+[!INCLUDE [iot-edge-version-1.4](includes/iot-edge-version-1.4.md)]
 
 GPUs are a popular choice for artificial intelligence computations, because they offer parallel processing capabilities and can often execute vision-based inferencing faster than CPUs. To better support artificial intelligence and machine learning applications, Azure IoT Edge for Linux on Windows (EFLOW) can expose a GPU to the virtual machine's Linux module.
 
@@ -84,7 +83,7 @@ For example, the following commands create a GPU-enabled virtual machine with ei
 Deploy-Eflow -gpuPassthroughType DirectDeviceAssignment -gpuCount 1 -gpuName "NVIDIA A2"
 
 #Deploys EFLOW with Intel(R) Iris(R) Xe Graphics assigned to the EFLOW VM
-Deploy-Eflow -gpuPassthroughType ParaVirtualization -gpuCount 1 -gpuName “Intel(R) Iris(R) Xe Graphics”
+Deploy-Eflow -gpuPassthroughType ParaVirtualization -gpuCount 1 -gpuName "Intel(R) Iris(R) Xe Graphics"
 ```
 
 To find the name of your GPU, you can run the following command or look for Display adapters in Device Manager.

articles/iot-edge/how-to-access-dtpm.md

@@ -12,7 +12,7 @@ services: iot-edge
 
 # dTPM access for Azure IoT Edge for Linux on Windows
 
-[!INCLUDE [iot-edge-version-1.1-or-1.4](includes/iot-edge-version-1.1-or-1.4.md)]
+[!INCLUDE [iot-edge-version-1.4](includes/iot-edge-version-1.4.md)]
 
 A Trusted platform module (TPM) chip is a secure crypto-processor that is designed to carry out cryptographic operations. This technology is designed to provide hardware-based, security-related functions. The Azure IoT Edge for Linux on Windows (EFLOW) virtual machine doesn't have a virtual TPMs attached to the VM. However, the user can enable or disable the TPM passthrough feature, that allows the EFLOW virtual machine to use the Windows host OS TPM. The TPM passthrough feature enables two main scenarios: