Edits

Author: kgremban

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

@@ -79,29 +79,35 @@ This helper command checks connectivity to Azure Resource Manager and Microsoft
 
 ## Create a storage account and schema registry
 
-One of the components that Azure IoT Operations deploys, schema registry, requires a storage account with hierarchical namespace enabled.
-
-The storage account must be created in a *different* Azure region than the schema registry. This requirement is so that you can set up secure connection rules between the storage account and the schema registry. When the two resources are in different regions, you can disable public access to the storage account and create a network rule to allow connections from only the schema registry IP addresses. If the two were in the same region, IP network rules wouldn't apply.
+Azure IoT Operations requires a schema registry on your cluster. Schema registry requires an Azure storage account so that it can synchronize schema information between cloud and edge.
 
 Run the following CLI commands in your Codespaces terminal.
 
-1. Create a storage account with hierarchical namespace enabled and public access disabled. This command uses the `westcentralus` region for example. If you want to change to a different region closer to you, make sure it's a different region than the one you used in your codespace.
+1. Set environment variables for the resources you create in this section.
+
+   | Placeholder | Value |
+   | ----------- | ----- |
+   | <STORAGE_ACCOUNT_NAME> | A name for your storage account. Storage account names must be between 3 and 24 characters in length and only contain numbers and lowercase letters. |
+   | <SCHEMA_REGISTRY_NAME> | A name for your schema registry. |
+   | <SCHEMA_REGISTRY_NAMESPACE> | A name for your schema registry namespace. The namespace uniquely identifies a schema registry within a tenant. |
 
    ```azurecli
-   export STORAGE_ACCOUNT=${CLUSTER_NAME:0:16}-storage
-   az storage account create --name $STORAGE_ACCOUNT --location <REGION> -g $RESOURCE_GROUP --enable-hierarchical-namespace --allow-shared-key-access false --default-action Deny --allow-blob-public-access false 
+   export STORAGE_ACCOUNT=<STORAGE_ACCOUNT_NAME>
+   export SCHEMA_REGISTRY=<SCHEMA_REGISTRY_NAME>
+   export SCHEMA_REGISTRY_NAMESPACE=<SCHEMA_REGISTRY_NAMESPACE>
+   ```
 
-1. Allow schema registry IP addresses to access the storage account.
+1. Create a storage account with hierarchical namespace enabled.
 
    ```azurecli
-   az storage account network-rule add -g $RESOURCE_GROUP --account-name $STORAGE_ACCOUNT --ip-address 20.1.75.142 20.252.196.43 20.51.24.43 20.51.28.95 4.157.157.214 20.253.64.236 20.85.106.152 20.96.85.51 20.82.208.202 20.105.106.242 20.195.58.86 40.119.231.144 20.101.219.97 51.124.23.193 20.245.227.204 40.112.138.48 20.99.136.137 20.252.49.47 20.106.114.138 20.125.89.107
+   az storage account create --name $STORAGE_ACCOUNT --location $LOCATION --resource-group $RESOURCE_GROUP --enable-hierarchical-namespace
    ```
 
 1. Create a schema registry that connects to your storage account.
 
    ```azurecli
-   export SCHEMA_REGISTRY=${CLUSTER_NAME:0:16}-schema
-   az iot ops schema registry create -n myschemaregistry -g mygroup --registry-namespace mynamespace --sa-resource-id $(az storage account show --name $STORAGE_ACCOUNT -o tsv --query id)
+   az iot ops schema registry create --name $SCHEMA_REGISTRY --resource-group $RESOURCE_GROUP --registry-namespace $SCHEMA_REGISTRY_NAMESPACE --sa-resource-id $(az storage account show --name $STORAGE_ACCOUNT -o tsv --query id)
+   ```
 
 ## Deploy Azure IoT Operations Preview
 
@@ -121,7 +127,7 @@ Run the following CLI commands in your Codespaces 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
+   az iot ops create --cluster $CLUSTER_NAME --resource-group $RESOURCE_GROUP --name ${CLUSTER_NAME}-instance
    ```
 
    If you get an error that says *Your device is required to be managed to access your resource*, run `az login` again and make sure that you sign in interactively with a browser.
@@ -144,7 +150,7 @@ To view your resources on the Azure portal, use the following steps:
 
 1. Select the name of your Azure IoT Operations instance.
 
-1. On the **Overview** page of your instance, the **Arc extensions** table displays the resources that were deployed to your cluster.
+1. On the **Overview** page of your instance, the **Arc extensions** tab displays the resources that were deployed to your cluster.
 
    :::image type="content" source="../get-started-end-to-end-sample/media/quickstart-deploy/view-instance.png" alt-text="Screenshot that shows the Azure IoT Operations instance on your Arc-enabled cluster." lightbox="../get-started-end-to-end-sample/media/quickstart-deploy/view-instance.png":::
 

articles/iot-operations/includes/connect-cluster-codespaces.md

@@ -23,11 +23,7 @@ To connect your cluster to Azure Arc:
    > * Open the codespace in VS Code desktop, and then return to the browser terminal and rerun `az login`.
    > * Or, after you get the localhost error on the browser, copy the URL from the browser and run `curl "<URL>"` in a new terminal tab. You should see a JSON response with the message "You have logged into Microsoft Azure!."
 
-1. Set the Azure subscription context for all commands:
-
-   ```azurecli
-   az account set -s $SUBSCRIPTION_ID
-   ```
+1. After signing 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.
 
 1. Register the required resource providers in your subscription:
 
@@ -46,19 +42,19 @@ To connect your cluster to Azure Arc:
 1. Use the [az group create](/cli/azure/group#az-group-create) command to create a resource group in your Azure subscription to store all the resources:
 
    ```azurecli
-   az group create --location $LOCATION --resource-group $RESOURCE_GROUP --subscription $SUBSCRIPTION_ID
+   az group create --location $LOCATION --resource-group $RESOURCE_GROUP
    ```
 
 1. Use the [az connectedk8s connect](/cli/azure/connectedk8s#az-connectedk8s-connect) command to Arc-enable your Kubernetes cluster and manage it as part of your Azure resource group:
 
    ```azurecli
-   az connectedk8s connect -n $CLUSTER_NAME -l $LOCATION -g $RESOURCE_GROUP --subscription $SUBSCRIPTION_ID --disable-auto-upgrade
+   az connectedk8s connect --name $CLUSTER_NAME --location $LOCATION --resource-group $RESOURCE_GROUP --disable-auto-upgrade
    ```
 
    >[!TIP]
    >The value of `$CLUSTER_NAME` is automatically set to the name of your codespace. Replace the environment variable if you want to use a different name.
 
-1. Get the `objectId` of the Microsoft Entra ID application that the Azure Arc service uses and save it as an environment variable.
+1. Get the `objectId` of the Microsoft Entra ID application that the Azure Arc service in your tenant uses and save it as an environment variable.
 
    ```azurecli
    export OBJECT_ID=$(az ad sp show --id bc313c14-388c-4e7d-a58e-70017303ee3b --query id -o tsv)

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

@@ -81,10 +81,10 @@ The northbound cloud connectors let you connect the MQTT broker directly to clou
 
 ## Process data
 
-In Azure IoT operations v0.6.0, the data processor is replaced by [data flows](./connect-to-cloud/overview-dataflow.md). Data flows provide enhanced data transformation and data contextualization capabilities within Azure IoT Operations. Data flows can use schemas stored in the schema registry to deserialize and serialize messages.
+In Azure IoT operations v0.6.0, the data processor was replaced by [data flows](./connect-to-cloud/overview-dataflow.md). Data flows provide enhanced data transformation and data contextualization capabilities within Azure IoT Operations. Data flows can use schemas stored in the schema registry to deserialize and serialize messages.
 
 > [!NOTE]
-> If you want to continue using the data processor, you must deploy Azure IoT Operations v0.5.1 with the additional flag to include data processor component. It's not possible to deploy the data processor with Azure IoT Operations v0.6.0. The Azure IoT operations CLI extension that includes the flag for deploying the data processor is version 0.5.1b1. This version requires Azure CLI v2.46.0 or greater. The data processor documentation is currently available on the previous versions site: [Azure IoT Operations data processor](/previous-versions/azure/iot-operations/process-data/overview-data-processor).
+> If you want to continue using the data processor, you must deploy Azure IoT Operations v0.5.1 with the additional flag to include data processor component. It's not possible to deploy the data processor with Azure IoT Operations v0.6.0 or newer. The Azure IoT operations CLI extension that includes the flag for deploying the data processor is version 0.5.1b1. This version requires Azure CLI v2.46.0 or greater. The data processor documentation is currently available on the previous versions site: [Azure IoT Operations data processor](/previous-versions/azure/iot-operations/process-data/overview-data-processor).
 
 ## Visualize and analyze telemetry
 
@@ -103,20 +103,18 @@ To secure communication between devices and the cloud through isolated network e
 
 ## Supported regions
 
-In the 0.6.x public preview release, Azure IoT Operations supports clusters that are Arc-enabled in the following regions:
+In the 0.7.x public preview release, Azure IoT Operations supports clusters that are Arc-enabled in the following regions:
 
 | Region       | CLI value   |
 |--------------|-------------|
 | East US      | eastus      |
 | East US 2    | eastus2     |
 | West US      | westus      |
 | West US 2    | westus2     |
+| West US 3    | westus3     |
 | West Europe  | westeurope  |
 | North Europe | northeurope |
 
->[!NOTE]
->West US 3 was supported in previous versions of Azure IoT Operations, but isn't supported in version 0.6.x.
-
 This list of supported regions only applies to the region that you use when connecting your cluster to Azure Arc. This list doesn't restrict you from using your preferred Azure region for your cloud resources. Azure IoT Operations components and other resources deployed to your cluster in these supported regions can still connect to cloud resources in different regions.
 
 ## Next step