Move screenshots; upgrade hub

Author: kgremban

articles/iot-hub/create-connect-device.md

@@ -157,8 +157,12 @@ If you want to keep a device in your IoT hub's identity registry, but want to pr
 
    * To prevent a device from connecting, set the **Enable connection to IoT Hub** parameter to **Disable**.
 
+     :::image type="content" source="./media/create-connect-device/disable-device.png" alt-text="screenshot that shows disabling a device in the Azure portal.":::
+
    * To completely remove a device from your IoT hub's identity registry, select **Delete**.
 
+     :::image type="content" source="./media/create-connect-device/delete-device.png" alt-text="screenshot that shows deleting a device in the Azure portal.":::
+
 ### [Azure CLI](#tab/cli)
 
 To disable a device, use the [az iot hub device-identity update](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-update) command and change the `status` of the device. For example:

articles/iot-hub/create-hub.md

@@ -1,7 +1,7 @@
 ---
-title: Create an IoT hub
+title: Create an Azure IoT hub
 titleSuffix: Azure IoT Hub
-description: How to create, manage, and delete Azure IoT hubs through the Azure portal and CLI. Includes information about pricing tiers, scaling, security, and messaging configuration.
+description: How to create, manage, and delete Azure IoT hubs through the Azure portal and CLI. Includes information about retrieving the service connection string.
 author: kgremban
 
 ms.author: kgremban
@@ -11,7 +11,7 @@ ms.date: 06/10/2024
 ms.custom: ['Role: Cloud Development']
 ---
 
-# Create an IoT hub using the Azure portal
+# Create and manage Azure IoT hubs
 
 This article describes how to create and manage an IoT hub.
 
@@ -42,24 +42,6 @@ The previous command creates an IoT hub in the S1 pricing tier for which you're
 
 ---
 
-## Update an IoT hub
-
-You can change the settings of an existing IoT hub after it's created. Here are some properties you can set for an IoT hub:
-
-* **Pricing and scale**: Migrate to a different tier or set the number of IoT Hub units.
-
-* **IP Filter**: Specify a range of IP addresses for the IoT hub to accept or reject.
-
-* **Properties**: A list of properties that you can copy and use elsewhere, such as the resource ID, resource group, location, and so on.
-
-### [Azure portal](#tab/portal)
-
-### [Azure CLI](#tab/cli)
-
-Use the [az iot hub update](/cli/azure/iot/hub#az-iot-hub-update) command to make changes to an existing IoT hub.
-
----
-
 ## Connect to an IoT hub
 
 Provide access permissions to applications and services that use IoT Hub functionality.
@@ -114,11 +96,13 @@ In production scenarios, we recommend using Microsoft Entra ID and Azure role-ba
 
 ## Delete an IoT hub
 
+When you delete an IoT hub, you lose the associated device identity registry. Any registered devices will need to be registered to a new IoT hub to continue sending data. If you want to move or upgrade an IoT hub, or delete an IoT hub but keep the devices, consider [migrating an IoT hub using the Azure CLI](./migrate-hub-state-cli.md).
+
 ### [Azure portal](#tab/portal)
 
 To delete an IoT hub, open your IoT hub in the Azure portal, then choose **Delete**.
 
-:::image type="content" source="./media/iot-hub-create-through-portal/delete-iot-hub.png" alt-text="Screenshot showing where to find the delete button for an IoT hub in the Azure portal." lightbox="./media/iot-hub-create-through-portal/delete-iot-hub.png":::
+:::image type="content" source="./media/create-hub/delete-iot-hub.png" alt-text="Screenshot showing where to find the delete button for an IoT hub in the Azure portal." lightbox="./media/create-hub/delete-iot-hub.png":::
 
 ### [Azure CLI](#tab/cli)
 
@@ -133,7 +117,20 @@ az iot hub delete --name {your iot hub name} -\
 
 ## Other tools for managing IoT hubs
 
-* **PowerShell cmdlets**: Use the [Az.IoTHub](/powershell/module/az.iothub) set of commands to create and manage IoT hubs.
-* **IoT Hub resource provider REST API**: Use the [IoT Hub Resource](/rest/api/iothub/iot-hub-resource) set of operations to create and manage IoT hubs.
-* **Azure resource manager templates, Bicep, or Terraform**: Use the [Microsoft.Devices/IoTHubs](/azure/templates/microsoft.devices/iothubs) resource type to create and manage IoT hubs. For examples, see [IoT Hub sample templates](/samples/browse/?terms=iot%20hub&languages=bicep%2Cjson)
-* **Visual Studio Code**: Use the [Azure IoT Hub extension for Visual Studio Code](./reference-iot-hub-extension.md) to create and manage IoT hubs.
+In addition to the Azure portal and CLI, the following tools are available to help you work with IoT hubs in whichever way supports your scenario:
+
+* **PowerShell cmdlets**
+
+  Use the [Az.IoTHub](/powershell/module/az.iothub) set of commands to create and manage IoT hubs.
+
+* **IoT Hub resource provider REST API**
+
+  Use the [IoT Hub Resource](/rest/api/iothub/iot-hub-resource) set of operations to create and manage IoT hubs.
+
+* **Azure resource manager templates, Bicep, or Terraform**    
+
+  Use the [Microsoft.Devices/IoTHubs](/azure/templates/microsoft.devices/iothubs) resource type to create and manage IoT hubs. For examples, see [IoT Hub sample templates](/samples/browse/?terms=iot%20hub&languages=bicep%2Cjson)
+
+* **Visual Studio Code**
+
+  Use the [Azure IoT Hub extension for Visual Studio Code](./reference-iot-hub-extension.md) to create and manage IoT hubs.

articles/iot-hub/iot-hub-upgrade.md

@@ -5,7 +5,7 @@ author: kgremban
 
 ms.service: iot-hub
 ms.topic: upgrade-and-migration-article
-ms.date: 02/07/2023
+ms.date: 06/21/2024
 ms.author: kgremban
 ---
 
@@ -20,18 +20,26 @@ When you have more devices and need more capabilities, there are three ways to a
 * Change the size of the IoT hub. For example, migrate a hub from the B1 tier to the B2 tier to increase the number of messages that each unit can support per day from 400,000 to 6 million. Both these changes can occur without interrupting existing operations.
 
 * Upgrade to a higher tier. For example, upgrade a hub from the B1 tier to the S1 tier for access to advanced features with the same messaging capacity.
+
    > [!Warning]
    > You cannot upgrade from a Free Hub to a Paid Hub through our upgrade function.  You must create a Paid hub and migrate the configurations and devices from the Free hub to the Paid hub. This process is documented at [How to migrate an IoT hub](./migrate-hub-state-cli.md).
+
    > [!Tip]
    > When you are upgrading your IoT Hub to a higher tier, some messages may be received out of order for a short period of time. If your business logic relies on the order of messages, we recommend upgrading during non-business hours.
 
 If you want to downgrade your IoT hub, you can remove units and reduce the size of the IoT hub but you can't downgrade to a lower tier. For example, you can move from the S2 tier to the S1 tier, but not from the S2 tier to the B1 tier. Only one type of [IoT Hub edition](https://azure.microsoft.com/pricing/details/iot-hub/) within a tier can be chosen per IoT hub. For example, you can create an IoT hub with multiple units of S1. However, you can't create an IoT hub with a mix of units from different editions, such as S1 and B3 or S1 and S2.
 
 These examples are meant to help you understand how to adjust your IoT hub as your solution changes. For specific information about each tier's capabilities, you should always refer to [Azure IoT Hub pricing](https://azure.microsoft.com/pricing/details/iot-hub/).
 
+Get more details about [How to choose the right IoT Hub tier](iot-hub-scaling.md).
+
 ## Upgrade your existing IoT hub
 
-If you want to upgrade an existing IoT hub, you can do so from the Azure portal.
+If you want to upgrade an existing IoT hub, you can do so from the Azure portal or Azure CLI. 
+
+### [Azure portal](#tab/portal)
+
+In the Azure portal, navigate to your IoT hub to view and update its settings.
 
 1. Sign in to the [Azure portal](https://portal.azure.com/) and navigate to your IoT hub.
 
@@ -47,8 +55,28 @@ If you want to upgrade an existing IoT hub, you can do so from the Azure portal.
 
    :::image type="content" source="./media/iot-hub-upgrade/message-pricing-advanced-options.png" alt-text="Screenshot that shows how to upgrade the size or units of your IoT hub.":::
 
-The maximum limit of device-to-cloud partitions for basic tier and standard tier IoT hubs is 32. Most IoT hubs only need four partitions. You choose the number of partitions when you create the IoT hub. The number of partitions relates the device-to-cloud messages to the number of simultaneous readers of these messages. The number of partitions remains unchanged when you migrate from the basic tier to the standard tier.
+### [Azure CLI](#tab/cli)
+
+Use the [az iot hub show](/cli/azure/iot/hub#az-iot-hub-show) command to view the current details of an IoT hub.
+
+```bash
+az iot hub show --name <HUB_NAME>
+```
 
-## Next steps
+Use the [az iot hub update](/cli/azure/iot/hub#az-iot-hub-update) command to make changes to an existing IoT hub.
 
-Get more details about [How to choose the right IoT Hub tier](iot-hub-scaling.md).
+For example, the following command updates the IoT hub tier to `S2`, or standard tier, size 2.
+
+```bash
+az iot hub update --name <HUB_NAME> --sku S2
+```
+
+For example, the following command sets the number of units for an IoT hub. The type of units in an IoT hub are determined by the size value of the tier (1, 2, or 3) but you can scale up or down by changing the number of units.
+
+```bash
+az iot hub update -n MyIotHub --unit 2
+```
+
+---
+
+The maximum limit of device-to-cloud partitions for basic tier and standard tier IoT hubs is 32. Most IoT hubs only need four partitions. You choose the number of partitions when you create the IoT hub. The number of partitions relates the device-to-cloud messages to the number of simultaneous readers of these messages. The number of partitions remains unchanged when you migrate from the basic tier to the standard tier.