Update prereqs

Author: dominicbetts

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

@@ -16,7 +16,26 @@ In this article, you learn how to automatically discover and configure OPC UA as
 
 ## Prerequisites
 
-A deployed instance of Azure IoT Operations. If you don't already have an instance, see [Quickstart: Run Azure IoT Operations in GitHub Codespaces with K3s](../get-started-end-to-end-sample/quickstart-deploy.md).
+- 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).
+
+  > [!NOTE]
+  > By default, the [deployment quickstart](../get-started-end-to-end-sample/quickstart-deploy.md) instructions do not enable resource sync rules.
+
+- 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:
+
+  ```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
+
+Currently, discovery is only enabled in the preview version of the connector for OPC UA.
+
+[!INCLUDE [deploy-preview-media-connectors](../includes/deploy-preview-media-connectors.md)]
 
 ## Create an asset endpoint
 
@@ -26,7 +45,7 @@ To create an asset endpoint with discovery enabled:
 
 1. Add a new asset endpoint and select the **Enable discovery** option:
 
-   :::image type="content" source="media/howto-autodetect-opcua-assets-using-akri/enable-auto-discover.png" alt-text="Create an asset endpoint with discovery enabled.":::
+    :::image type="content" source="media/howto-autodetect-opcua-assets-using-akri/enable-auto-discover.png" alt-text="Create an asset endpoint with discovery enabled.":::
 
 1. Select **Create** to create the asset endpoint.
 
@@ -36,7 +55,7 @@ Azure IoT Operations uses the asset endpoint to connect to the OPC UA server and
 
 1. Go to the **Discovery** page for your instance in the operations experience:
 
-   :::image type="content" source="media/howto-autodetect-opcua-assets-using-akri/discovered-assets-list.png" alt-text="View discovered assets.":::
+  :::image type="content" source="media/howto-autodetect-opcua-assets-using-akri/discovered-assets-list.png" alt-text="View discovered assets.":::
 
 1. You can filter the list by the asset endpoint name, or by keyword. The list shows the discovered assets and their status.
 

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

@@ -3,41 +3,23 @@ title: include file
 description: include file
 author: dominicbetts
 ms.topic: include
-ms.date: 03/20/2025
+ms.date: 04/03/2025
 ms.author: dobett
 ---
 
-To update the version of the media and ONVIF connectors in your Azure IoT Operations deployment, run the following PowerShell commands to enable preview features:
+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:
 
-> [!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>`.
+- 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`.
 
-```powershell
-$clusterName="<YOUR AZURE IOT OPERATIONS CLUSTER NAME>"
-$clusterResourceGroup="<YOUR RESOURCE GROUP NAME>"
+- To enable the preview connectors after you deploy your Azure IoT Operations instance by using the Azure portal:
 
-$extension = az k8s-extension list `
---cluster-name $clusterName `
---cluster-type connectedClusters `
---resource-group $clusterResourceGroup `
---query "[?extensionType == 'microsoft.iotoperations']" `
-| ConvertFrom-Json
+  :::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:
 
-az k8s-extension update `
---version $extension.version `
---name $extension.name `
---release-train $extension.releaseTrain `
---cluster-name $clusterName `
---resource-group $clusterResourceGroup `
---cluster-type connectedClusters `
---auto-upgrade-minor-version false `
---config connectors.image.registry=mcr.microsoft.com `
---config connectors.image.repository=aio-connectors/helmchart/microsoft-aio-connectors `
---config connectors.image.tag=1.1.0 `
---config connectors.values.enablePreviewFeatures=true `
---yes
-```
+  ```console
+  az iot ops update -n <your-instance> -g <your-resource-group> --feature connectors.settings.preview=Enabled
+  ```
 
-> [!NOTE]
-> This update process is for preview components only. The media and ONVIF connectors are currently preview components.
+> [!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>`.