Merge pull request #302975 from SoniaLopezBravo/aio2507-preview-features

Adding new location support and upgrading to preview

Author: JamesJBarnett

articles/iot-operations/configure-observability-monitoring/howto-configure-observability.md

@@ -43,8 +43,8 @@ Complete the steps in this article *before* deploying Azure IoT Operations to yo
 1. Install Azure CLI extensions for Metrics collection for Azure Arc-enabled clusters and Azure Managed Grafana.
 
    ```azurecli
-   az extension add --name k8s-extension
-   az extension add --name amg
+   az extension add --upgrade --name k8s-extension
+   az extension add --upgrade --name amg
    ```
 
 1. Create an Azure Monitor workspace to enable metric collection for your Azure Arc-enabled Kubernetes cluster.

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-operations.md

@@ -214,8 +214,15 @@ The `check` command displays a warning about missing data flows, which is normal
 
 You can check the configurations of topic maps, QoS, and message routes by adding the `--detail-level 2` parameter to the `check` command for a verbose view.
 
+You can view all versions of the Azure IoT Operations CLI extension that are available by running the following command:
+
+```azurecli
+az iot ops get-versions
+```
+
 ## Next steps
 
-If your components need to connect to Azure endpoints like SQL or Fabric, learn how to [Manage secrets for your Azure IoT Operations deployment](../deploy-iot-ops/howto-manage-secrets.md).
+- If your components need to connect to Azure endpoints like SQL or Fabric, learn how to [Manage secrets for your Azure IoT Operations deployment](../deploy-iot-ops/howto-manage-secrets.md).
+- To upgrade your Azure IoT Operations deployment to a newer version, see [Upgrade Azure IoT Operations](./howto-upgrade.md).
 
 

articles/iot-operations/deploy-iot-ops/howto-deploy-iot-test-operations.md

@@ -174,6 +174,12 @@ The `check` command displays a warning about missing data flows, which is normal
 
 You can check the configurations of topic maps, QoS, and message routes by adding the `--detail-level 2` parameter to the `check` command for a verbose view.
 
+You can view all versions of the Azure IoT Operations CLI extension that are available by running the following command:
+
+```azurecli
+az iot ops get-versions
+```
+
 ## Next steps
 
 The Azure IoT Operations instance you deployed is configured for testing scenarios. If you want to enable secure setting and prepare the instance for production scenarios, follow the steps in [Enable secure settings on an existing Azure IoT Operations instance](./howto-enable-secure-settings.md).

articles/iot-operations/deploy-iot-ops/howto-upgrade.md

@@ -5,39 +5,39 @@ author: dominicbetts
 ms.author: dobett
 ms.topic: how-to
 ms.custom: devx-track-azurecli
-ms.date: 03/03/2025
+ms.date: 07/18/2025
 
 #CustomerIntent: As an IT professional, I want to manage Azure IoT Operations instances.
 ---
 
 # Upgrade to a new version
 
-Upgrade an Azure IoT Operations deployment to a newer version. Azure IoT Operations supports upgrade from version 1.0.x onwards. There's no support for upgrading from any preview version of Azure IoT Operations to any generally available (GA) version.
+Learn how to upgrade an Azure IoT Operations deployment to a newer version. There's no support for upgrading from any preview version of Azure IoT Operations to any generally available (GA) version.
 
 ## Prerequisites
 
-* Azure CLI. This scenario requires Azure CLI version 2.53.0 or higher. Use `az --version` to check your version and `az upgrade` to update if necessary. For more information, see [Get started with Azure CLI](/cli/azure/get-started-with-azure-cli).
-
-* The Azure IoT Operations extension for Azure CLI. Use the following command to add the extension or update it to the latest version:
-
-  ```azurecli
-  az extension add --upgrade --name azure-iot-ops
-  ```
+- An Azure account with an active subscription. If you don't have an account, you can create a [free account](https://azure.microsoft.com/free).
+- Azure CLI version 2.53.0 or higher. Use `az --version` to check your version and `az upgrade` to update if necessary. For more information, see [Get started with Azure CLI](/cli/azure/get-started-with-azure-cli).
 
 ## Understand upgrade support
 
-You can upgrade an existing Azure IoT Operations instance to any patch of the same minor version, or to the next minor version.
+Azure IoT Operations release versions can be preview or generally available (GA), you can find the latest version in the [Azure IoT Operations versions](https://aka.ms/aio-versions) document. The Azure IoT Operations CLI extension version is tied to the Azure IoT Operations version, so you need to ensure that you have the correct CLI extension version installed to perform an upgrade.
+
+Azure IoT Operations supports the following upgrade scenarios:
 
-Azure IoT Operations doesn't support downgrading between versions. To move to an older version, uninstall Azure IoT Operations and reinstall the desired version.
+- You can upgrade an existing Azure IoT Operations instance to any patch of the same minor version, or to the next minor version.
+- You can't downgrade between versions. To move to an older version, [uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) and reinstall the desired version. 
+- You can't upgrade from any preview version to a GA version. You need to [uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) and reinstall the new version. 
+- You can't upgrade from any GA version to a preview version. For more information on how to install a preview version, see [Upgrade to preview version](howto-upgrade.md#upgrade-to-preview-version).
 
 > [!NOTE]
 > Azure IoT Operations doesn't support live upgrades. Please expect some downtime during the upgrade process.
 
 ## Upgrade
 
-Azure IoT Operations supports upgrading instances to new GA versions as they're released.
+Azure IoT Operations supports upgrading instances to new GA versions as they're released. If your Azure IoT Operations instance is eligible for an upgrade, you can use the Azure portal or the Azure CLI to perform the upgrade.
 
-You can't upgrade from a preview installation to a GA version. To move to version 1.0.x, [uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) and reinstall the new version.
+If the latest version of the Azure IoT Operations is in preview, see [Upgrade to preview version](howto-upgrade.md#upgrade-to-preview-version).
 
 ### [Azure portal](#tab/portal)
 
@@ -77,7 +77,7 @@ The upgrade command evaluates the entire Azure IoT Operations deployment for ava
 
 Use the following steps to upgrade your deployment to the latest version:
 
-1. You need to use the latest version of the Azure IoT Operations CLI extension to get the latest version of Azure IoT Operations. If you didn't update the extension as part of the prerequisites, do so now.
+1. Add the latest version of the Azure IoT Operations CLI extension.
 
    ```azurecli
    az extension add --upgrade --name azure-iot-ops
@@ -89,17 +89,43 @@ Use the following steps to upgrade your deployment to the latest version:
    az iot ops upgrade --resource-group <RESOURCE_GROUP_NAME> --name <INSTANCE_NAME>
    ```
 
-1. The CLI outputs a table of the components that have available upgrades. Enter `Y` to continue with the upgrade.
+1. The CLI outputs a table of the components that have available upgrades. Enter `Y` to continue with the upgrade. 
+
+If you want to upgrade to a specific version of Azure IoT Operations that isn't the latest, you can run `az iot ops get-versions` or refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want. Get the version number and run the following command to upgrade to that version:
+
+```azurecli
+az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
+```
+
+---
+
+## Upgrade to preview version
 
-If you want to upgrade to a specific version of Azure IoT Operations that isn't the latest, use the related CLI extension version. Each version of Azure IoT Operations maps to a version of the Azure IoT Operations CLI extension.
+Sometimes the latest version of Azure IoT Operations is in preview. Check the [Azure IoT Operations versions](https://aka.ms/aio-versions) to see the latest version. During preview releases, version upgrade is blocked, and you need to uninstall Azure IoT Operations and reinstall the preview version. 
 
-Refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want. Then, upgrade the CLI extension:
+You can only install a preview version using the Azure CLI.
+
+1. If you have an existing Azure IoT Operations instance, you need to [Uninstall Azure IoT Operations](howto-manage-update-uninstall.md#uninstall) to do a new deployment. 
+1. Add the latest version of the Azure IoT Operations CLI extension with the `--allow-preview` flag.
 
    ```azurecli
-   az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
+   az extension add --upgrade --name azure-iot-ops --allow-preview
    ```
 
----
+If you want to upgrade to a specific version of Azure IoT Operations that isn't the latest, you can run `az iot ops get-versions` or refer to [IoT Operations versions](https://aka.ms/aio-versions) to find the CLI extension version associated with the Azure IoT Operations version that you want. Get the version number and run the following command to upgrade to that version:
+
+   ```azurecli
+   az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
+```
+
+> [!NOTE]
+> In preview releases, the `az iot ops upgrade` command doesn't work for upgrading to a preview version, but it works for configuring the Azure IoT Operations for observability. Add the following parameters to the `upgrade` command:
+>
+> | Parameter | Value | Description |
+> | --------- | ----- | ----------- |
+> | `--ops-config` | `observability.metrics.openTelemetryCollectorAddress=<FULLNAMEOVERRIDE>.azure-iot-operations.svc.cluster.local:<GRPC_ENDPOINT>` | Provide the OpenTelemetry (OTel) collector address you configured in the otel-collector-values.yaml file.<br><br>The sample values used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) are **fullnameOverride=aio-otel-collector** and **grpc.endpoint=4317**. |
+> | `--ops-config` | `observability.metrics.exportInternalSeconds=<CHECK_INTERVAL>` | Provide the **check_interval** value you configured in the otel-collector-values.yaml file.<br><br>The sample value used in [Configure observability](../configure-observability-monitoring/howto-configure-observability.md) is **check_interval=60**. |
+
 
 ## MQTT broker upgrade considerations
 

articles/iot-operations/overview-iot-operations.md

@@ -144,6 +144,7 @@ Azure IoT Operations supports clusters that are Arc-enabled in the following reg
 | West US 3    | westus3     |
 | West Europe  | westeurope  |
 | North Europe | northeurope |
+|Germany West Central | germanywestcentral |
 
 This list of supported regions only applies to the region that you use when connecting your cluster to Azure Arc. This list doesn't restrict you from using your preferred Azure region for your cloud resources. Azure IoT Operations components and other resources deployed to your cluster in these supported regions can still connect to cloud resources in different regions.