Tidy third IoT central quickstart

Author: dominicbetts

articles/iot-central/core/quick-configure-rules.md

@@ -1,6 +1,6 @@
 ---
 title: Quickstart - Configure rules and actions in Azure IoT Central
-description: This quickstart shows you how to configure telemetry-based rules and actions in your IoT Central application.
+description: In this quickstart, you learn how to configure telemetry-based rules and actions in your IoT Central application.
 author: dominicbetts
 ms.author: dobett
 ms.date: 09/26/2022
@@ -14,7 +14,7 @@ ms.custom: mvc, mode-other
 
 # Quickstart: Configure rules and actions for your device in Azure IoT Central
 
-Get started with IoT Central rules. In this quickstart you create a rule that sends an email when someone turns your phone over.
+Get started with IoT Central rules. IoT Central rules let you automate actions that occur in response to specific conditions. The example in this quickstart uses accelerometer telemetry from the phone to trigger a rule when the phone is turned over.
 
 In this quickstart, you:
 

articles/iot-central/core/quick-deploy-iot-central.md

@@ -1,6 +1,6 @@
 ---
 title: Quickstart - Connect a device to an Azure IoT Central application | Microsoft Docs
-description: In this quickstart you learn how to connect your first device to a new IoT Central application. This quickstart uses a smartphone app from either the Google Play or Apple app store as an IoT device.
+description: In this quickstart, you learn how to connect your first device to a new IoT Central application. This quickstart uses a smartphone app from either the Google Play or Apple app store as an IoT device.
 author: dominicbetts
 ms.author: dobett
 ms.date: 09/26/2022
@@ -43,6 +43,8 @@ IoT Central provides various industry-focused application templates to help you
 
     :::image type="content" source="media/quick-deploy-iot-central/iot-central-create-new-application.png" alt-text="Build your IoT application page":::
 
+    If you're prompted to sign in, use the Microsoft account associated with your Azure subscription.
+
 1. On the **New application** page, make sure that **Custom application** is selected under the **Application template**.
 
 1. Azure IoT Central automatically suggests an **Application name** based on the application template you've selected. Enter your own application name such as *Contoso quickstart app*.

articles/iot-central/core/quick-export-data.md

@@ -1,6 +1,6 @@
 ---
 title: Quickstart - Export data from Azure IoT Central
-description: In this quickstart you learn how to use the data export feature in IoT Central to integrate with other cloud services.
+description: In this quickstart, you learn how to use the data export feature in IoT Central to integrate with other cloud services.
 author: dominicbetts
 ms.author: dobett
 ms.date: 09/26/2022
@@ -34,97 +34,37 @@ Completing this quickstart incurs a small cost in your Azure account for the Azu
 
 ## Install Azure services
 
-Before you can export data from your IoT Central application, you need an Azure Data Explorer cluster and database. In this quickstart, you use the bash environment in the [Azure Cloud Shell](https://shell.azure.com) to create and configure them.
+Before you can export data from your IoT Central application, you need an Azure Data Explorer cluster and database. In this quickstart, you run a bash script in the [Azure Cloud Shell](https://shell.azure.com) to create and configure them.
 
-Run the following script in the Azure Cloud Shell. Replace the `clustername` value with a unique name for your cluster before you run the script. The cluster name can contain only lowercase letters and numbers. Replace the `centralurlprefix` value with the URL prefix you chose in the first quickstart:
+The script completes the following steps:
 
-> [!IMPORTANT]
-> The script can take 20 to 30 minutes to run.
+- Prompts you to sign in to your Azure subscription so that it can generate a bearer token to authenticate the REST API calls.
+- Creates an Azure Data Explorer cluster and database.
+- Creates a managed identity for your IoT Central application.
+- Configures the managed identity with permission to access the Azure Data Explorer database.
+- Adds a table to the database to store the incoming telemetry from IoT Central.
+
+Run the following commands to download the script to your Azure Cloud Shell environment:
 
 ```azurecli
-# The cluster name can contain only lowercase letters and numbers.
-# It must contain from 4 to 22 characters.
-clustername="<A unique name for your cluster>"
-
-centralurlprefix="<The URL prefix of your IoT Central application>"
-
-databasename="phonedata"
-location="eastus"
-resourcegroup="IoTCentralExportData-rg"
-
-az extension add -n kusto
-
-# Create a resource group for the Azure Data Explorer cluster
-az group create --location $location \
-    --name $resourcegroup
-
-# Create the Azure Data Explorer cluster
-# This command takes at least 10 minutes to run
-az kusto cluster create --cluster-name $clustername \
-    --sku name="Standard_D11_v2"  tier="Standard" \
-    --enable-streaming-ingest=true \
-    --enable-auto-stop=true \
-    --resource-group $resourcegroup --location $location
-
-# Create a database in the cluster
-az kusto database create --cluster-name $clustername \
-    --database-name $databasename \
-    --read-write-database location=$location soft-delete-period=P365D hot-cache-period=P31D \
-    --resource-group $resourcegroup
-
-# Create and assign a managed identity to use
-# when authenticating from IoT Central.
-# This assumes your IoT Central was created in the default
-# IOTC resource group.
-MI_JSON=$(az iot central app identity assign --name $centralurlprefix \
-    --resource-group IOTC --system-assigned)
-
-## Assign the managed identity permissions to use the database.
-az kusto database-principal-assignment create --cluster-name $clustername \
-                                              --database-name $databasename \
-                                              --principal-id $(jq -r .principalId <<< $MI_JSON) \
-                                              --principal-assignment-name $centralurlprefix \
-                                              --resource-group $resourcegroup \
-                                              --principal-type App \
-                                              --tenant-id $(jq -r .tenantId <<< $MI_JSON) \
-                                              --role Admin
-
-echo "Azure Data Explorer URL: $(az kusto cluster show --name $clustername --resource-group $resourcegroup --query uri -o tsv)" 
+wget https://raw.githubusercontent.com/Azure-Samples/iot-central-docs-samples/main/quickstart-cde/createADX.sh
+chmod u+x createADX.sh
 ```
 
-Make a note of the **Azure Data Explorer URL**. You use this value later in the quickstart.
-
-## Configure the database
-
-To add a table in the database to store the accelerometer data from the **IoT Plug and Play** smartphone app:
-
-1. Use the **Azure Data Explorer URL** from the previous section to navigate to your Azure Data Explorer environment.
-
-1. Expand the cluster node and select the **phonedata** database. The cope of the query window changes to `Scope:yourclustername.eastus/phonedata`.
-
-1. Paste the following Kusto script into the query editor and select **Run**:
-
-    ```kusto
-    .create table acceleration (
-      EnqueuedTime:datetime,
-      Device:string,
-      X:real,
-      Y:real,
-      Z:real
-    );
-    ```
-
-    The result looks like the following screenshot:
+Use the following command to run the script:
 
-    :::image type="content" source="media/quick-export-data/azure-data-explorer-create-table.png" alt-text="Screenshot that shows the results of creating the table in Azure Data Explorer.":::
+- Replace `CLUSTER_NAME` with a unique name for your Azure Data Explorer cluster. The cluster name can contain only lowercase letters and numbers. The length of the cluster name must be between 4 and 22 characters.
+- Replace `CENTRAL_URL_PREFIX` with URL prefix you chose in the first quickstart for your IoT Central application.
+- When prompted, follow the instructions to sign in to your account. It's necessary for the script to sign in because it generates a bearer token to authenticate a REST API call.
 
-1. In the Azure Data Explorer, open a new tab and paste in the following Kusto script. The script enables streaming ingress for the **acceleration** table:
+```azurecli
+./createADX.sh CLUSTER_NAME CENTRAL_URL_PREFIX
+```
 
-    ```kusto
-    .alter table acceleration policy streamingingestion enable;
-    ```
+> [!IMPORTANT]
+> This script can take 20 to 30 minutes to run.
 
-Keep the Azure Data Explorer page open in your browser. After you configure the data export in your IoT Central application, you'll run a query to view the accelerometer telemetry stored in the **acceleration** table.
+Make a note of the **Azure Data Explorer URL** output by the script. You use this value later in the quickstart.
 
 ## Configure data export
 
@@ -218,13 +158,19 @@ Wait until the export status shows **Healthy**:
 
 ## Query exported data
 
-In Azure Data Explorer, open a new tab and paste in the following Kusto query and then select **Run** to plot the accelerometer telemetry:
+To query the exported telemetry:
 
-```kusto
-['acceleration'] 
-    | project EnqueuedTime, Device, X, Y, Z
-    | render timechart 
-```
+1. Use the **Azure Data Explorer URL** output by the script you ran previously to navigate to your Azure Data Explorer environment.
+
+1. Expand the cluster node and select the **phonedata** database. The scope of the query window changes to `Scope:yourclustername.eastus/phonedata`.
+
+1. In Azure Data Explorer, open a new tab and paste in the following Kusto query and then select **Run** to plot the accelerometer telemetry:
+
+  ```kusto
+  ['acceleration'] 
+      | project EnqueuedTime, Device, X, Y, Z
+      | render timechart 
+  ```
 
 You may need to wait for several minutes to collect enough data. Try holding your phone in different orientations to see the telemetry values change: