Address feedback

Author: dominicbetts

articles/iot-operations/discover-manage-assets/howto-autodetect-opcua-assets-using-akri.md

@@ -16,20 +16,38 @@ In this article, you learn how to automatically discover and configure OPC UA as
 
 ## Prerequisites
 
-- A deployed instance of Azure IoT Operations with resource sync rules enabled. You can only enable resource sync rules when you create your Azure IoT Operations instance. To learn more, see [Deploy Azure IoT Operations](../deploy-iot-ops/overview-deploy.md).
+A deployed instance of Azure IoT Operations with resource sync rules enabled. To learn more, see [Deploy Azure IoT Operations](../deploy-iot-ops/overview-deploy.md).
 
-  > [!NOTE]
-  > By default, the [deployment quickstart](../get-started-end-to-end-sample/quickstart-deploy.md) instructions do not enable resource sync rules.
+> [!TIP]
+> By default, the [deployment quickstart](../get-started-end-to-end-sample/quickstart-deploy.md) instructions do not enable resource sync rules. If resource sync rules aren't enabled on your instance, see [Enable resource sync rules on an existing instance](../troubleshoot/troubleshoot.md#you-want-to-enable-resource-sync-rules-on-an-existing-instance).
+
+The custom location in the resource group where you deployed Azure IoT Operations must have the **Azure Kubernetes Service Arc Contributor Role** role enabled with **K8 Bridge** as a member: For example:
+
+# [Azure portal](#tab/portal)
+
+1. Go to the custom location for your Azure IoT Operations instance in the Azure portal.
+
+1. Select **Access control (IAM)**.
+
+1. Select **Add > Add role assignment**.
+
+1. Search for and select the **Azure Kubernetes Service Arc Contributor Role** role. Then click **Next**.
 
-- The custom location in the resource group where you deployed Azure IoT Operations must have the **Azure Kubernetes Service Arc Contributor Role** role enabled with **K8 Bridge** as a member. For example:
+1. Select **Select members**. Search for and select **K8 Bridge**. Then click **Review + Assign**.
 
-  ```bash
-  CUSTOM_LOCATION_NAME=$(az iot ops list -g <YOUR RESOURCE GROUP> --query "[0].extendedLocation.name" -o tsv)
-  
-  ASSIGNEE=$(az ad sp list --display-name "K8 Bridge" --query "[0].appId" -o tsv)
-  
-  az role assignment create --role "Azure Kubernetes Service Arc Contributor Role" --assignee $ASSIGNEE --scope $CUSTOM_LOCATION_NAME
-  ```
+1. To finish adding the role assignment, select **Review + assign** again.
+
+# [Azure CLI](#tab/cli)
+
+```bash
+CUSTOM_LOCATION_NAME=$(az iot ops list -g <YOUR RESOURCE GROUP> --query "[0].extendedLocation.name" -o tsv)
+
+ASSIGNEE=$(az ad sp list --display-name "K8 Bridge" --query "[0].appId" -o tsv)
+
+az role assignment create --role "Azure Kubernetes Service Arc Contributor Role" --assignee $ASSIGNEE --scope $CUSTOM_LOCATION_NAME
+```
+
+---
 
 ## Deploy the preview connectors
 

articles/iot-operations/includes/deploy-preview-media-connectors.md

@@ -7,19 +7,38 @@ ms.date: 04/03/2025
 ms.author: dobett
 ---
 
-To deploy the preview version of the connectors, you can either enable them when you deploy your Azure IoT Operations instance or enable them after you deploy your instance:
+To deploy the preview version of the connectors, you can either enable them when you deploy your Azure IoT Operations instance or enable them after you deploy your instance.
 
-- To enable the preview connectors when you deploy your Azure IoT Operations instance include the `--feature connectors.settings.preview=Enabled` parameter when you run `az iot ops create`.
+To enable the preview connectors when you deploy your Azure IoT Operations instance:
 
-- To enable the preview connectors after you deploy your Azure IoT Operations instance by using the Azure portal:
+# [Azure portal](#tab/portal)
+
+Select **ONVIF Connector and Media Connector (Preview)** in the **Connectors** section of the **Install Azure IoT Operations > Basics** page:
+
+:::image type="content" source="media/deploy-preview-media-connectors/portal-deploy-preview-connectors.png" alt-text="Screenshot of Azure portal that shows how to select the preview connectors.":::
+
+# [Azure CLI](#tab/cli)
+
+Include the `--feature connectors.settings.preview=Enabled` parameter when you run the `az iot ops create` command.
+
+---
+
+To enable the preview connectors after you deploy your Azure IoT Operations instance:
+
+# [Azure portal](#tab/portal)
+
+1. Go to your Azure IoT Operations instance in the Azure portal.
+
+1. Enable the preview connectors:
 
   :::image type="content" source="media/deploy-preview-media-connectors/portal-enable-preview-connectors.png" alt-text="Screenshot of Azure portal that shows how to enable the preview connectors.":::
 
-- To enable the preview connectors after you deploy your Azure IoT Operations instance by using the Azure CLI:
+# [Azure CLI](#tab/cli)
+
+Run the following command to enable the preview connectors:
 
-  ```console
-  az iot ops update -n <your-instance> -g <your-resource-group> --feature connectors.settings.preview=Enabled
-  ```
+```azcli
+az iot ops update -n <your-instance> -g <your-resource-group> --feature connectors.settings.preview=Enabled
+```
 
-> [!IMPORTANT]
-> If you don't enable preview features, you see the following error message in the `aio-supervisor-...` pod logs when you try to use the media or ONVIF connectors: `No connector configuration present for AssetEndpointProfile: <AssetEndpointProfileName>`.
+---