Merge pull request #194178 from dominicbetts/central-remove-v2

IoT Central remove V2 references

Author: ttorble

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

@@ -1334,6 +1334,11 @@
       "source_path_from_root": "/articles/iot-central/preview/concepts-get-connected.md",
       "redirect_url": "/azure/iot-central/core/overview-iot-central-developer/",
       "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/iot-central/core/howto-migrate.md",
+      "redirect_url": "/azure/iot-central/core/overview-iot-central/",
+      "redirect_document_id": false
     }
   ]
 }

articles/iot-central/TOC.yml

@@ -221,8 +221,6 @@
           href: core/howto-create-organizations.md
         - name: Customize application UI
           href: core/howto-customize-ui.md
-        - name: Migrate V2 to V3 application
-          href: core/howto-migrate.md
         - name: Configure and use file uploads
           href: core/howto-configure-file-uploads.md
         - name: Manage and monitor in the Azure portal
@@ -275,6 +273,4 @@
   - name: Customer data requests
     href: core/iot-central-customer-data-requests.md
   - name: Supported browsers
-    href: core/iot-central-supported-browsers.md
-  - name: Azure IoT Central (legacy templates)
-    href: /previous-versions/azure/iot-central/core/overview-iot-central
+    href: core/iot-central-supported-browsers.md

articles/iot-central/core/howto-build-iotc-device-bridge.md

@@ -90,14 +90,12 @@ Each key in the `measurements` object must match the name of a telemetry type in
 
 You can include a `timestamp` field in the body to specify the UTC date and time of the message. This field must be in ISO 8601 format. For example, `2020-06-08T20:16:54.602Z`. If you don't include a timestamp, the current date and time is used.
 
-You can include a `modelId` field in the body. Use this field to assign the device to a device template during provisioning. This functionality is only supported by [V3 applications](howto-faq.yml#how-do-i-get-information-about-my-application-).
+You can include a `modelId` field in the body. Use this field to assign the device to a device template during provisioning.
 
 The `deviceId` must be alphanumeric, lowercase, and may contain hyphens.
 
 If you don't include the `modelId` field, or if IoT Central doesn't recognize the model ID, then a message with an unrecognized `deviceId` creates a new _unassigned device_ in IoT Central. An operator can manually migrate the device to the correct device template. To learn more, see [Manage devices in your Azure IoT Central application > Migrating devices to a template](howto-manage-devices-individually.md).
 
-In [V2 applications](howto-faq.yml#how-do-i-get-information-about-my-application-), the new device appears an unassigned device on the **Devices** page. Select **Assign template** and choose a device template to start receiving incoming telemetry from the device.
-
 > [!NOTE]
 > Until the device is assigned to a template, all HTTP calls to the function return a 403 error status.
 

articles/iot-central/core/howto-configure-rules-advanced.md

@@ -27,9 +27,6 @@ To complete the steps in this how-to guide, you need:
 
 [!INCLUDE [iot-central-prerequisites-basic](../../../includes/iot-central-prerequisites-basic.md)]
 
-> [!NOTE]
-> If you're using a version 2 IoT Central application, see [Build workflows with the IoT Central connector in Azure Logic Apps](/previous-versions/azure/iot-central/core/howto-build-azure-logic-apps) on the previous versions documentation site and use the Azure IoT Central V2 connector
-
 ## Trigger a workflow from a rule
 
 Before you can trigger a workflow in Power Automate or Azure Logic Apps, you need a rule in your IoT Central application. To learn more, see [Configure rules and actions in Azure IoT Central](./howto-configure-rules.md).

articles/iot-central/core/howto-export-data.md

@@ -27,9 +27,7 @@ For example, you can:
 
 ## Prerequisites
 
-To use data export features, you must have a [V3 application](howto-faq.yml#how-do-i-get-information-about-my-application-), and you must have the [Data export](howto-manage-users-roles.md) permission.
-
-If you have a V2 application, see [Migrate your V2 IoT Central application to V3](howto-migrate.md).
+To use data export features, you must have the [Data export](howto-manage-users-roles.md) permission.
 
 ## Set up an export destination
 

articles/iot-central/core/howto-manage-iot-central-from-portal.md

@@ -99,9 +99,6 @@ You can configure role assignments in the Azure portal or use the Azure CLI:
 
 ## Monitor application health
 
-> [!NOTE]
-> Metrics are only available for version 3 IoT Central applications. To learn how to check your application version, see [How do I get information about my application?](howto-faq.yml#how-do-i-get-information-about-my-application-).
-
 You can use the set of metrics provided by IoT Central to assess the health of devices connected to your IoT Central application and the health of your running data exports.
 
 Metrics are enabled by default for your IoT Central application and you access them from the [Azure portal](https://portal.azure.com/). The [Azure Monitor data platform exposes these metrics](../../azure-monitor/essentials/data-platform-metrics.md) and provides several ways for you to interact with them. For example, you can use charts in the Azure portal, a REST API, or queries in PowerShell or the Azure CLI.

articles/iot-central/core/howto-migrate.md

@@ -104,12 +104,6 @@ An administrator can:
 
 To learn more, see [Create and use a custom application template](howto-create-iot-central-application.md#create-and-use-a-custom-application-template) .
 
-## Migrate to a new version
-
-An administrator can migrate an application to a newer version. Currently, all newly created applications are V3 applications. Depending on when it was created, it may be V2. An administrator is responsible for migrating a V2 application to a V3 application.
-
-To learn more, see [Migrate your V2 IoT Central application to V3](howto-migrate.md).
-
 ## Monitor application health
 
 An administrator can use IoT Central metrics to assess the health of connected devices and the health of running data exports.