Addressing feedback

Author: SoniaLopezBravo

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

@@ -15,8 +15,6 @@ ms.date: 10/22/2024
 
 Observability provides visibility into every layer of your Azure IoT Operations configuration. It gives you insight into the actual behavior of issues, which increases the effectiveness of site reliability engineering. Azure IoT Operations offers observability through custom curated Grafana dashboards that are hosted in Azure. These dashboards are powered by Azure Monitor managed service for Prometheus and by Container Insights. This guide shows you how to set up Azure Managed Prometheus and Grafana and enable monitoring for your Azure Arc cluster.
 
-Complete the steps in this article *before* deploying Azure IoT Operations to your cluster.
-
 ## Prerequisites
 
 * An Arc-enabled Kubernetes cluster.
@@ -231,6 +229,23 @@ Configure Prometheus metrics collection on your cluster.
    kubectl apply -f ama-metrics-prometheus-config.yaml
    ```
 
+
+## Set up observability configuration
+
+You can set up the observability configuration of your Azure IoT Operations deployment at any time. 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 [instructions in this article](#deploy-opentelemetry-collector) use the sample values **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 [instructions in this article](#deploy-opentelemetry-collector) use the sample value **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.
+
 ## Deploy dashboards to Grafana
 
 Azure IoT Operations provides a [sample dashboard](https://github.com/Azure/azure-iot-operations/tree/main/samples/grafana-dashboard) designed to give you many of the visualizations you need to understand the health and performance of your Azure IoT Operations deployment.
@@ -254,3 +269,6 @@ Complete the following steps to install the Azure IoT Operations curated Grafana
 1. When the application prompts, select your managed Prometheus data source.
 
 1. Select **Import**.
+
+
+

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

@@ -118,25 +118,6 @@ If you want to upgrade to a specific version of Azure IoT Operations that isn't
 az extension add --upgrade --name azure-iot-ops --version <VERSION_NUMBER>
 ```
 
-## Upgrade observability configuration
-
-To upgrade the observability configuration of your Azure IoT Operations instance, first you need to follow the steps in [Deploy observability resources](../configure-observability-monitoring/howto-configure-observability.md).
-
-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.
-
-
 ## MQTT broker upgrade considerations
 
 To ensure zero data loss and high availability during deployment upgrades, the MQTT broker implements rolling updates across the MQTT broker pods. The health manager pod coordinates an incremental upgrade process for the MQTT broker pods to ensure that:

articles/iot-operations/secure-iot-ops/howto-manage-certificates.md

@@ -149,7 +149,7 @@ To set up Azure IoT Operations with your own issuer for internal communications,
 
 The certificate management experience for external communications uses Azure Key vault as the managed vault solution on the cloud. Certificates are added to the key vault as secrets and synchronized to the edge as Kubernetes secrets via [Azure Key Vault Secret Store extension](/azure/azure-arc/kubernetes/secret-store-extension).
 
-Connectors use the certificate management experience to configure client application authentication to external servers. Azure IoT Operations manages two distinct certificate stores for connectors: one for the *Trust list* and one for the *Issuer list*. To learn more about how connectors use certificates to establish mutual trust with external servers, see the connector-specific certificate management documentation.
+Connectors use the certificate management experience to configure client application authentication to external servers. To learn more about how connectors use certificates to establish mutual trust with external servers, see the connector-specific certificate management documentation.
 
 When you [deploy Azure IoT Operations with secure settings](../deploy-iot-ops/overview-deploy.md#secure-settings-deployment), you can start adding certificates to Azure Key Vault, and sync them to the Kubernetes cluster to be used in the *Trust list* and *Issuer list* stores for external connections.
 
@@ -191,6 +191,6 @@ To manage certificates for external communications, follow these steps:
     :::image type="content" source="media/howto-manage-certificates/list-certificates.png" lightbox="media/howto-manage-certificates/list-certificates.png" alt-text="Screenshot that shows the list of certificates in the devices page and how to filter by Trust List and Issuer List.":::
 
 
-To learn more about the *Trust list* and *Issuer list* stores, see the connector-specific certificate management documentation.
+To learn more about how trust certificates are managed for specific connectors, see the connector-specific certificate management documentation.
 
 You can delete synced certificates as well. When you delete a synced certificate, it only deletes the synced certificate from the Kubernetes cluster, and doesn't delete the contained secret reference from Azure Key Vault. You must delete the certificate secret manually from the key vault.