Remove bugbash instructions

Author: kgremban

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

@@ -15,11 +15,6 @@ ms.date: 09/24/2024
 
 Azure IoT Operations uses Azure Key Vault as the managed vault solution on the cloud, and uses [Azure Key Vault Secret Store extension for Kubernetes](/azure/azure-arc/kubernetes/secret-store-extension) to sync the secrets down from the cloud and store them on the edge as Kubernetes secrets.
 
->[!NOTE]
->**Special instructions for AIO Internal Bugbash**:
->
->Refer to [Test secrets and user-assigned managed identity](https://msazure.visualstudio.com/One/_wiki/wikis/AIO.wiki/710296/Test-Secrets-and-User-Assigned-Managed-Identity) for instructions on how to test secrets with the PLC simulator.
-
 ## Prerequisites
 
 * An Azure IoT Operations instance deployed with secure settings. If you deployed Azure IoT Operations with test settings and now want to use secrets, you need to first [enable secure settings](./howto-enable-secure-settings.md).

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

@@ -39,16 +39,6 @@ To prepare your Azure Arc-enabled Kubernetes cluster, you need:
 
 * The latest version of the Azure IoT Operations extension for Azure CLI. Use the following command to add the extension or update it to the latest version:
 
-  > [!NOTE]
-  > **Special instructions for AIO Internal Bugbash**:
-  >
-  > Official IoT Ops CLI releases are installed via extension index with the *az extension add --upgrade --name azure-iot-ops* command mentioned below. However for bug bashes, we will distribute one-off release candidates intended to expose functionality to exercise internally. Use this for Bug Bash 2 on 9/27 and skip the az extension command below
-  >
-  >``` bash
-  >az storage blob download --auth-mode login --blob-url https://azedgecli.blob.core.windows.net/drop/azure_iot_ops-0.7.0a11-py3-none-any.whl -f ./azure_iot_ops-0.7.0a11-py3-none-any.whl
-  >az extension add --upgrade --source ./azure_iot_ops-0.7.0a11-py3-none-any.whl
-  >```
-
   ```bash
   az extension add --upgrade --name azure-iot-ops
   ```
@@ -66,16 +56,6 @@ To prepare your Azure Arc-enabled Kubernetes cluster, you need:
 
 * Azure CLI version 2.64.0 or newer installed on your development machine. Use `az --version` to check your version and `az upgrade` to update if necessary. For more information, see [How to install the Azure CLI](/cli/azure/install-azure-cli).
 
-> [!NOTE]
-   > **Special instructions for AIO Internal Bugbash**:
-   >
-   > Official IoT Ops CLI releases are installed via extension index with the *az extension add --upgrade --name azure-iot-ops* command mentioned below. However for bug bashes, we will distribute one-off release candidates intended to expose functionality to exercise internally. Use this for Bug Bash 2 on 9/27 and skip the az extension command below
-   >
-   > ``` bash
-   >    az storage blob download --auth-mode login --blob-url https://azedgecli.blob.core.windows.net/drop/azure_iot_ops-0.7.0a11-py3-none-any.whl -f ./azure_iot_ops-0.7.0a11-py3-none-any.whl
-   >    az extension add --upgrade --source ./azure_iot_ops-0.7.0a11-py3-none-any.whl
-   > ```
-
 * The latest version of the Azure IoT Operations extension for Azure CLI. Use the following command to add the extension or update it to the latest version:
 
   ```bash
@@ -118,21 +98,6 @@ The [AksEdgeQuickStartForAio.ps1](https://github.com/Azure/AKS-Edge/blob/main/to
    | CLUSTER_NAME | A name for the new cluster to be created. |
    | ARC_APP_OBJECT_ID | The object ID value that you retrieved in the previous step. |
 
-   > [!NOTE]
-   > **Special instructions for AIO Internal Bugbash**:
-   >
-   > The instructions below for AksEdgeQuickStartForAio.ps1 from AKS-Edge GitHub repo are for external customer consumption and will only work after AIO 0.7 is released.
-   >
-   > For internal bug bashes, use this powershell script below instead
-   >
-   >```powershell
-   >$url = "https://raw.githubusercontent.com/jagadishmurugan/AKS-Edge/blob/users/jagamu/changes-for-M2-integration/tools/scripts/AksEdgeQuickStart/AksEdgeQuickStartForAio.ps1"
-   >Invoke-WebRequest -Uri $url -OutFile .\AksEdgeQuickStartForAio.ps1
-   >Unblock-File .\AksEdgeQuickStartForAio.ps1
-   >Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process -Force
-   >.\AksEdgeQuickStartForAio.ps1 -SubscriptionId "<SUBSCRIPTION_ID>" -TenantId "<TENANT_ID>" -ResourceGroupName "<RESOURCE_GROUP_NAME>"  -Location "<LOCATION>"  -ClusterName "<CLUSTER_NAME>" -Tag "test-v0.3" -CustomLocationOid $customlocationOid
-   >```
-
    ```powershell
    $url = "https://raw.githubusercontent.com/Azure/AKS-Edge/main/tools/scripts/AksEdgeQuickStart/AksEdgeQuickStartForAio.ps1"
    Invoke-WebRequest -Uri $url -OutFile .\AksEdgeQuickStartForAio.ps1

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

@@ -77,17 +77,6 @@ To connect your cluster to Azure Arc:
 
 1. After you sign in, Azure CLI displays all of your subscriptions and indicates your default subscription with an asterisk `*`. To continue with your default subscription, select `Enter`. Otherwise, type the number of the Azure subscription that you want to use.
 
-   > [!NOTE]
-   > **Special instructions for AIO Internal Bugbash**:
-   >
-   > Codespaces come preloaded with the Azure CLI and the latest public release of the azure-iot-ops extension.
-   > However for bug bashes, we will distribute one-off release candidates intended to expose functionality to exercise internally. Use this for Bug Bash 2 on 9/27:
-   >
-   > ``` bash
-   >    az storage blob download --auth-mode login --blob-url https://azedgecli.blob.core.windows.net/drop/azure_iot_ops-0.7.0a11-py3-none-any.whl -f ./azure_iot_ops-0.7.0a11-py3-none-any.whl
-   >    az extension add --upgrade --source ./azure_iot_ops-0.7.0a11-py3-none-any.whl
-   > ```
-
 1. Register the required resource providers in your subscription:
 
    >[!NOTE]