Upgrade observability

Author: SoniaLopezBravo

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

@@ -245,9 +245,9 @@ Complete the following steps to install the Azure IoT Operations curated Grafana
    az grafana show --name <GRAFANA_NAME> --resource-group <RESOURCE_GROUP> --query url -o tsv
    ```
 
-1. In the Grafana application, select the **+** icon.
+1. On the Grafana landing page, select the **Create your first dashboard** tile.
 
-1. Select **Import dashboard**.
+1. Select **Import Dashboard**.
 
 1. Browse to the sample dashboard directory in your local copy of the Azure IoT Operations repository, **azure-iot-operations** > **samples** > **grafana-dashboard**, then select the  `aio.sample.json` dashboard file.
 

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

@@ -54,8 +54,6 @@ A cluster host:
 
   If you deployed Azure IoT Operations to your cluster previously, uninstall those resources before continuing. For more information, see [Update Azure IoT Operations](./howto-manage-update-uninstall.md#uninstall).
 
-* (Optional) Prepare your cluster for observability before deploying Azure IoT Operations: [Configure observability](../configure-observability-monitoring/howto-configure-observability.md).
-
 * (Recommended) Configure your own certificate authority issuer before deploying Azure IoT Operations: [Bring your own issuer](../secure-iot-ops/howto-manage-certificates.md#bring-your-own-issuer).
 
 ## Deploy in Azure portal
@@ -186,14 +184,6 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
       --feature connectors.settings.preview=Enabled
       ```
 
-   * If you followed the optional prerequisites to prepare your cluster for observability, add the following optional parameters to the `create` command:
-
-       | Optional 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**. |
-
-
     * If you followed the optional prerequisites to set up your own certificate authority issuer, add the `--trust-settings` parameters to the `create` command:
 
     ```bash

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

@@ -54,7 +54,6 @@ A cluster host:
 
   If you deployed Azure IoT Operations to your cluster previously, uninstall those resources before continuing. For more information, see [Update Azure IoT Operations](./howto-manage-update-uninstall.md#uninstall).
 
-* (Optional) Prepare your cluster for observability before deploying Azure IoT Operations: [Configure observability](../configure-observability-monitoring/howto-configure-observability.md).
 
 ## Deploy in Azure portal
 
@@ -168,14 +167,6 @@ One at a time, run each Azure CLI command on the **Automation** tab in a termina
     --feature connectors.settings.preview=Enabled
     ```
 
-    * If you followed the optional prerequisites to prepare your cluster for observability, add the following parameters to the `create` 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**. |
-
-
 1. Once all of the Azure CLI commands complete successfully, you can close the **Install Azure IoT Operations** wizard.
 
 Once the `create` command completes successfully, you have a working Azure IoT Operations instance running on your cluster. At this point, your instance is configured for most testing and evaluation scenarios.

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

@@ -12,7 +12,7 @@ ms.date: 07/18/2025
 
 # Upgrade to a new 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.
+Learn how to upgrade an Azure IoT Operations deployment to a newer version.
 
 ## Prerequisites
 
@@ -114,17 +114,27 @@ You can only install a preview version using the Azure CLI.
 
 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>
+```azurecli
+az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
 ```
 
+## Upgrade observability configuration
+
+After deployment is complete, you need to follow [Deploy observability resources](../configure-observability-monitoring/howto-configure-observability.md) to upgrade the observability configuration of your Azure IoT Operations instance. 
+
+Once observability resources are configured, you can upgrade the observability configuration by running the `az iot ops upgrade` command with the `--ops-config` parameter to specify the new configuration values.
+
+```azurecli
+az iot ops upgrade --resource-group <rg name> -n <instance name> --ops-config observability.metrics.openTelemetryCollectorAddress=<>
+```
+
+| 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**. |
+
 > [!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**. |
+> 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.
 
 
 ## MQTT broker upgrade considerations