Merge pull request #289216 from dominicbetts/release-aio-m3-bb

AIO [M3]: Fixup versions and links

Author: prmerger-automator[bot]

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

@@ -152,7 +152,7 @@ Use these steps if you chose the **Test settings** option on the **Dependency ma
       | `--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**. |
 
       >[!TIP]
-      >The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.7.0 deployed on it, you can skip this step.
+      >The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.8.0 deployed on it, you can skip this step.
 
       This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 
@@ -217,7 +217,7 @@ Use these steps if you chose the **Secure settings** option on the **Dependency
       | `--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**. |
 
       >[!TIP]
-      >The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.7.0 deployed on it, you can skip this step.
+      >The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.8.0 deployed on it, you can skip this step.
 
       This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 

articles/iot-operations/get-started-end-to-end-sample/quickstart-configure.md

@@ -54,40 +54,6 @@ The following snippet shows the YAML file that you applied:
 > [!CAUTION]
 > This configuration uses a self-signed application instance certificate. Don't use this configuration in a production environment. To learn more, see [Configure OPC UA certificates infrastructure for the connector for OPC UA](../discover-manage-assets/howto-configure-opcua-certificates-infrastructure.md).
 
-To establish mutual trust between the OPC PLC simulator and the OPC UA connector, run the following commands:
-
-# [Bash](#tab/bash)
-
-```bash
-# Extract the OPC UA connector application instance certificate and add it to the OPC PLC trust list
-kubectl -n azure-iot-operations get secret aio-opc-opcuabroker-default-application-cert -o jsonpath='{.data.tls\.crt}' | base64 -d > opcuabroker.crt
-data=$(kubectl create secret generic temp --from-file=opcuabroker.crt=./opcuabroker.crt --dry-run=client -o jsonpath='{.data}')
-kubectl patch secret opc-plc-trust-list -n azure-iot-operations -p "{\"data\": $data}"
-rm ./opcuabroker.crt
-
-# Extract the OPC PLC application instance certificate and add it to the OPC UA connector trust list
-kubectl -n azure-iot-operations get secret opc-plc-default-application-cert -o jsonpath='{.data.tls\.crt}' | base64 -d > opcplc.crt
-data=$(kubectl create secret generic temp --from-file=opcplc-000000.crt=./opcplc.crt --dry-run=client -o jsonpath='{.data}')
-kubectl patch secret aio-opc-ua-broker-trust-list -n azure-iot-operations -p "{\"data\": $data}"
-rm ./opcplc.crt
-```
-
-# [PowerShell](#tab/powershell)
-
-```powershell
-# Extract the OPC UA connector application instance certificate and add it to the OPC PLC trust list
-kubectl -n azure-iot-operations get secret aio-opc-opcuabroker-default-application-cert -o jsonpath='{.data.tls\.crt}' | %{ [Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($_)) } > opcuabroker.crt
-$data = kubectl create secret generic temp --from-file=opcuabroker.crt=./opcuabroker.crt --dry-run=client -o jsonpath='{.data}'
-kubectl patch secret opc-plc-trust-list -n azure-iot-operations -p "{`"data`": $data}"
-rm ./opcuabroker.crt
-
-# Extract the OPC PLC application instance certificate and add it to the OPC UA connector trust list
-kubectl -n azure-iot-operations get secret opc-plc-default-application-cert -o jsonpath='{.data.tls\.crt}' | %{ [Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($_)) } > opcplc.crt
-$data = kubectl create secret generic temp --from-file=opcplc-000000.crt=./opcplc.crt --dry-run=client -o jsonpath='{.data}'
-kubectl patch secret aio-opc-ua-broker-trust-list -n azure-iot-operations -p "{`"data`": $data}"
-rm ./opcplc.crt
-```
-
 ---
 
 ## Set your environment variables
@@ -133,12 +99,10 @@ Run the following commands to download and run the Bicep file that configures yo
 
 <!-- TODO: Fix download link -->
 
-Download the Bicep file to your local environment from [quickstart.bicep](https://dev.azure.com/msazure/One/_git/azure-iot-operations-tests?path=%2F.pipelines%2Fbicep%2Fquickstart.bicep)
-
 # [Bash](#tab/bash)
 
 ```bash
-# wget https://dev.azure.com/msazure/One/_git/azure-iot-operations-tests?path=/.pipelines/bicep/quickstart.bicep -O quickstart.bicep
+wget https://raw.githubusercontent.com/Azure-Samples/explore-iot-operations/release-m3/samples/quickstarts/quickstart.bicep -O quickstart.bicep
 
 AIO_EXTENSION_NAME=$(az k8s-extension list -g $RESOURCE_GROUP --cluster-name $CLUSTER_NAME --cluster-type connectedClusters --query "[?extensionType == 'microsoft.iotoperations'].id" -o tsv | awk -F'/' '{print $NF}')
 AIO_INSTANCE_NAME=$(az iot ops list -g $RESOURCE_GROUP --query "[0].name" -o tsv)

articles/iot-operations/get-started-end-to-end-sample/quickstart-deploy.md

@@ -20,9 +20,6 @@ The rest of the quickstarts in this end-to-end series build on this one to defin
 
 If you want to deploy Azure IoT Operations to a local cluster such as Azure Kubernetes Service Edge Essentials or K3s on Ubuntu, see [Deployment details](../deploy-iot-ops/overview-deploy.md).
 
-> [!IMPORTANT]
-> If you're upgrading your public preview from version 0.6.0 to version 0.7.0, you must uninstall the previous version before deploying the new version. For more information, see [Update Azure IoT Operations](../deploy-iot-ops/howto-manage-update-uninstall.md#update).
-
 ## Before you begin
 
 This series of quickstarts is intended to help you get started with Azure IoT Operations as quickly as possible so that you can evaluate an end-to-end scenario. In a true development or production environment, multiple teams working together perform these tasks and some tasks might require elevated permissions.
@@ -174,18 +171,18 @@ Run the following CLI commands in your Codespaces terminal.
 1. Initialize your cluster for Azure IoT Operations.
 
    >[!TIP]
-   >The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.7.0 deployed on it, you can skip this step.
+   >The `init` command only needs to be run once per cluster. If you're reusing a cluster that already had Azure IoT Operations version 0.8.0 deployed on it, you can skip this step.
 
    ```azurecli
-   az iot ops init --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --sr-resource-id $(az iot ops schema registry show --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP -o tsv --query id)
+   az iot ops init --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP
    ```
 
    This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.
 
 1. Deploy Azure IoT Operations. This command takes several minutes to complete:
 
    ```azurecli
-   az iot ops create --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name ${CLUSTER_NAME}-instance
+   az iot ops create --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name ${CLUSTER_NAME}-instance  --sr-resource-id $(az iot ops schema registry show --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP -o tsv --query id)
    ```
 
    This command might take several minutes to complete. You can watch the progress in the deployment progress display in the terminal.

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

@@ -102,7 +102,7 @@ To secure communication between devices and the cloud through isolated network e
 
 ## Supported regions
 
-In the 0.7.x public preview release, Azure IoT Operations supports clusters that are Arc-enabled in the following regions:
+In the 0.8.x public preview release, Azure IoT Operations supports clusters that are Arc-enabled in the following regions:
 
 | Region       | CLI value   |
 |--------------|-------------|