Merge pull request #231802 from kgremban/mar21-hubstate

New article for az iot hub state

Author: JamesJBarnett

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

@@ -921,6 +921,11 @@
       "redirect_url": "/azure/iot-hub/policy-reference",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/iot-hub/iot-hub-how-to-clone.md",
+      "redirect_url": "/azure/iot-hub/migrate-hub-arm",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/iot-hub/iot-hub-csharp-csharp-direct-methods.md",
       "redirect_url": "/azure/iot-hub/quickstart-control-device-dotnet",

articles/iot-hub/TOC.yml

@@ -164,8 +164,6 @@
       - name: High availability and disaster recovery
         displayName: HA, DR, availability zone, failover, failback
         href: iot-hub-ha-dr.md
-      - name: How to clone an IoT Hub to another region
-        href: iot-hub-how-to-clone.md
     - name: Control access to IoT Hub
       items:
         - name: Overview
@@ -281,9 +279,17 @@
             - name: Use Azure CLI
               displayName: file upload, az iot hub update
               href: iot-hub-configure-file-upload-cli.md
-        - name: Upgrade an IoT hub
-          displayName: scale up, size, tier
-          href: iot-hub-upgrade.md
+        - name: Upgrade or migrate an IoT hub
+          items:
+          - name: Upgrade an IoT hub
+            displayName: scale up, size, tier
+            href: iot-hub-upgrade.md
+          - name: Automatically migrate an IoT hub using CLI
+            href: migrate-hub-state-cli.md
+          - name: Manually migrate an IoT hub using ARM
+            href: iot-hub-how-to-clone.md
+          - name: Bulk import and export IoT devices
+            href: iot-hub-bulk-identity-mgmt.md
         - name: Configure IP filtering
           href: iot-hub-ip-filtering.md
         - name: Manage public network access
@@ -298,8 +304,6 @@
             - name: Use Azure CLI
               displayName: automatic device management
               href: iot-hub-automatic-device-management-cli.md
-        - name: Bulk import and export IoT devices
-          href: iot-hub-bulk-identity-mgmt.md
         - name: Manage device twin tags
           href: iot-hubs-manage-device-twin-tags.md
     - name: Develop

articles/iot-hub/iot-hub-bulk-identity-mgmt.md

@@ -12,7 +12,7 @@ ms.custom: devx-track-csharp
 
 # Import and export IoT Hub device identities in bulk
 
-Each IoT hub has an identity registry you can use to create per-device resources in the service. The identity registry also enables you to control access to the device-facing endpoints. This article describes how to import and export device identities in bulk to and from an identity registry. To see a working sample in C# and learn how you can use this capability when cloning a hub to a different region, see [How to Clone an IoT Hub](iot-hub-how-to-clone.md).
+Each IoT hub has an identity registry you can use to create per-device resources in the service. The identity registry also enables you to control access to the device-facing endpoints. This article describes how to import and export device identities in bulk to and from an identity registry. To see a working sample in C# and learn how you can use this capability when migrating an IoT hub to a different region, see [How to migrate an IoT Hub using Azure Resource Manager templates](migrate-hub-arm.md).
 
 > [!NOTE]
 > IoT Hub has recently added virtual network support in a limited number of regions. This feature secures import and export operations and eliminates the need to pass keys for authentication.  Initially, virtual network support is available only in these regions: *WestUS2*, *EastUS*, and *SouthCentralUS*. To learn more about virtual network support and the API calls to implement it, see [IoT Hub Support for virtual networks](virtual-network-support.md).
@@ -436,6 +436,6 @@ static string GetContainerSasUri(CloudBlobContainer container)
 
 ## Next steps
 
-In this article, you learned how to perform bulk operations against the identity registry in an IoT hub. Many of these operations, including how to move devices from one hub to another, are used in the [Managing devices registered to the IoT hub section of How to Clone an IoT Hub](iot-hub-how-to-clone.md#managing-the-devices-registered-to-the-iot-hub). 
+In this article, you learned how to perform bulk operations against the identity registry in an IoT hub. Many of these operations, including how to move devices from one hub to another, are used in the **Manage devices registered to the IoT hub** section of [How to migrate an IoT hub using Azure Resource Manager templates](migrate-hub-arm.md#manage-the-devices-registered-to-the-iot-hub).
 
-The cloning article has a working sample associated with it, which is located in the IoT C# samples on this page: [Azure IoT hub service samples for C#](https://github.com/Azure/azure-iot-sdk-csharp/tree/main/iothub/service/samples/how%20to%20guides), with the project being ImportExportDevicesSample. You can download the sample and try it out; there are instructions in the [How to Clone an IoT Hub](iot-hub-how-to-clone.md) article.
+The migration article has a working sample associated with it, which is located in the IoT C# samples on this page: [Azure IoT hub service samples for C#](https://github.com/Azure/azure-iot-sdk-csharp/tree/main/iothub/service/samples/how%20to%20guides), with the project being ImportExportDevicesSample.

articles/iot-hub/iot-hub-ha-dr.md

@@ -149,7 +149,7 @@ Failover capability won't be available if you disable disaster recovery for an I
 
 :::image type="content" source="media/iot-hub-ha-dr/disaster-recovery-disabled.png" alt-text="Screenshot that shows disaster recovery disabled for an IoT hub in Singapore region.":::
 
-You can only disable disaster recovery to avoid data replication outside of the paired region in Brazil South or Southeast Asia when you create an IoT hub. If you want to configure your existing IoT hub to disable disaster recovery, you need to create a new IoT hub with disaster recovery disabled and manually migrate your existing IoT hub. For guidance, see [How to clone an Azure IoT Hub to another region](iot-hub-how-to-clone.md). This article contains advice about migrating routes, custom endpoints, and other IoT Hub artifacts when migrating to a new Iot hub. You can ignore concerns that have to do with migrating across regions.
+You can only disable disaster recovery to avoid data replication outside of the paired region in Brazil South or Southeast Asia when you create an IoT hub. If you want to configure your existing IoT hub to disable disaster recovery, you need to create a new IoT hub with disaster recovery disabled and manually migrate your existing IoT hub. For guidance, see [How to migrate an IoT hub](migrate-hub-state-cli.md).
 
 ## Achieve cross region HA