Merge pull request #217907 from dominicbetts/central-howto-screenshots

IoT Central: how to screenshot updates

Author: PMEds28

articles/iot-central/core/howto-configure-file-uploads.md

@@ -40,7 +40,7 @@ To configure device file uploads:
 
 1. Select **Save**. When the status shows **Configured**, you're ready to upload files from devices.
 
-:::image type="content" source="media/howto-configure-file-uploads/file-upload-configuration.png" alt-text="Configure file upload in application":::
+:::image type="content" source="media/howto-configure-file-uploads/file-upload-configuration.png" alt-text="Screenshot that shows a properly configured file upload." lightbox="media/howto-configure-file-uploads/file-upload-configuration.png":::
 
 ## Disable device file uploads
 
@@ -69,7 +69,7 @@ If you enabled access to files in the file upload configuration, users with the
 
 To view and delete uploaded files, navigate to the **Files** view for a device. On this page, you can see thumbnails of the uploaded files and toggle between a gallery and list view. Each file has options to download or delete it:
 
-:::image type="content" source="media/howto-configure-file-uploads/file-upload-list-files.png" alt-text="Screenshot that shows the gallery view for uploaded files.":::
+:::image type="content" source="media/howto-configure-file-uploads/file-upload-list-files.png" alt-text="Screenshot that shows the gallery view for uploaded files." lightbox="media/howto-configure-file-uploads/file-upload-list-files.png":::
 
 > [!TIP]
 > The file type is determined by the mime type assigned to the file when it was uploaded to blob storage. The default type is `binary/octet-stream`.
@@ -78,7 +78,7 @@ You can customize the list view by filtering based on file name and choosing the
 
 To preview the content of the file and get more information about the file, select it. IoT Central supports previews of common file types such as text and images:
 
-:::image type="content" source="media/howto-configure-file-uploads/file-upload-preview.png" alt-text="Screenshot that shows a preview of a text file.":::
+:::image type="content" source="media/howto-configure-file-uploads/file-upload-preview.png" alt-text="Screenshot that shows a preview of a text file." lightbox="media/howto-configure-file-uploads/file-upload-preview.png":::
 
 ## Next steps
 

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

@@ -19,18 +19,18 @@ Rules in IoT Central serve as a customizable response tool that trigger on activ
 
 Use the target devices section to select on what kind of devices this rule will be applied. Filters allow you to further refine what devices should be included. The filters use properties on the device template to filter down the set of devices. Filters themselves don't trigger an action. In the following screenshot, the devices that are being targeted are of device template type **Refrigerator**. The filter states that the rule should only include **Refrigerators** where the **Manufactured State** property equals **Washington**.
 
-:::image type="content" source="media/howto-configure-rules/filters.png" alt-text="Screenshot that shows a condition definition.":::
+:::image type="content" source="media/howto-configure-rules/filters.png" alt-text="Screenshot that shows a filter definition in a rule." lightbox="media/howto-configure-rules/filters.png":::
 
 ## Use multiple conditions
 
 Conditions are what rules trigger on. You can add multiple conditions to a rule and specify if the rule should trigger when all the conditions are true or any of the conditions are true.  
 
-In the following screenshot, the conditions check when the temperature is greater than 70° F and the humidity is less than 10. When any of these statements are true, the rule evaluates to true and triggers an action.
+In the following screenshot, the conditions check when the temperature is greater than 70° F and the humidity is less than 10%. When any of these statements are true, the rule evaluates to true and triggers an action.
 
 :::image type="content" source="media/howto-configure-rules/conditions.png" alt-text="Screenshot shows a refrigerator monitor with conditions specified for temperature and humidity." lightbox="media/howto-configure-rules/conditions.png":::
 
 > [!NOTE]
-> Currently only Telemetry Conditions are supported.  
+> Currently only telemetry conditions are supported.  
 
 ### Use a cloud property in a value field
 
@@ -42,13 +42,13 @@ If you choose an event type telemetry value, the **Value** drop-down includes th
 
 You can specify a time aggregation to trigger your rule based on a time window. Rule conditions evaluate aggregate time windows on telemetry data as tumbling windows. If there are any property filters in the rule, they're applied at the end of the time window. In the screenshot below, the time window is five minutes. Every five minutes, the rule evaluates on the last five minutes of telemetry data. The data is only evaluated once in the window to which it corresponds.
 
-:::image type="content" source="media/howto-configure-rules/tumbling-window.png" alt-text="A diagram showing how tumbling windows are defined.":::
+:::image type="content" source="media/howto-configure-rules/tumbling-window.png" alt-text="A diagram showing how tumbling windows are defined." border="false":::
 
 ## Create an email action
 
 When you create an email action, the email address must be a **user ID** in the application, and the user must have signed in to the application at least once. You can also specify a note to include in the email. IoT Central shows an example of what the email will look like when the rule triggers:
 
-:::image type="content" source="media/howto-configure-rules/email-action.png" alt-text="Screenshot that shows an email action for a rule.":::
+:::image type="content" source="media/howto-configure-rules/email-action.png" alt-text="Screenshot that shows an email action for a rule." lightbox="media/howto-configure-rules/email-action.png":::
 
 ## Create a webhook action
 
@@ -62,7 +62,7 @@ In this example, you connect to *RequestBin* to get notified when a rule fires:
 
 1. Add an action to your rule:
 
-    :::image type="content" source="media/howto-configure-rules/webhook-create.png" alt-text="Screenshot that shows the webhook creation screen.":::
+    :::image type="content" source="media/howto-configure-rules/webhook-create.png" alt-text="Screenshot that shows the webhook creation screen." lightbox="media/howto-configure-rules/webhook-create.png":::
 
 1. Choose the webhook action, enter a display name, and paste the RequestBin URL as the **Callback URL**.
 
@@ -193,15 +193,15 @@ An action group can:
 
 The following screenshot shows an action group that sends email and SMS notifications and calls a webhook:
 
-:::image type="content" source="media/howto-configure-rules/action-group.png" alt-text="Screenshot that shows an action group in the Azure portal.":::
+:::image type="content" source="media/howto-configure-rules/action-group.png" alt-text="Screenshot that shows an action group in the Azure portal." lightbox="media/howto-configure-rules/action-group.png":::
 
 To use an action group in an IoT Central rule, the action group must be in the same Azure subscription as the IoT Central application.
 
 When you add an action to the rule in IoT Central, select **Azure Monitor Action Groups**.
 
 Choose an action group from your Azure subscription:
 
-:::image type="content" source="media/howto-configure-rules/choose-action-group.png" alt-text="Screenshot that shows an action group in an IoT Central rule.":::
+:::image type="content" source="media/howto-configure-rules/choose-action-group.png" alt-text="Screenshot that shows an action group in an IoT Central rule." lightbox="media/howto-configure-rules/choose-action-group.png":::
 
 Select **Save**. The action group now appears in the list of actions to run when the rule is triggered.
 

articles/iot-central/core/howto-create-custom-analytics.md

@@ -108,7 +108,7 @@ Use the URL output by the script to navigate to the IoT Central application it c
     | Host name | The event hub namespace host name, it's the value you assigned to `eventhubnamespace` in the earlier script  |
     | Event Hub | The event hub name, it's the value you assigned to `eventhub` in the earlier script  |
 
-    :::image type="content" source="media/howto-create-custom-analytics/data-export-1.png" alt-text="Screenshot showing data export destination.":::
+    :::image type="content" source="media/howto-create-custom-analytics/data-export-1.png" alt-text="Screenshot showing data export destination." lightbox="media/howto-create-custom-analytics/data-export-1.png":::
 
 1. Select **Save**.
 
@@ -127,7 +127,7 @@ To create the export definition:
 
 1. Select **Save**.
 
-    :::image type="content" source="media/howto-create-custom-analytics/data-export-2.png" alt-text="Screenshot showing data export definition.":::
+:::image type="content" source="media/howto-create-custom-analytics/data-export-2.png" alt-text="Screenshot showing data export definition." lightbox="media/howto-create-custom-analytics/data-export-2.png":::
 
 Wait until the export status is **Healthy** on the **Data export** page before you continue.
 

articles/iot-central/core/howto-create-custom-rules.md

@@ -3,7 +3,7 @@ title: Extend Azure IoT Central with custom rules and notifications | Microsoft
 description: As a solution developer, configure an IoT Central application to send email notifications when a device stops sending telemetry. This solution uses Azure Stream Analytics, Azure Functions, and SendGrid.
 author: dominicbetts 
 ms.author: dobett 
-ms.date: 06/21/2022
+ms.date: 11/08/2022
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -43,9 +43,9 @@ Create an IoT Central application on the [Azure IoT Central application manager]
 | URL | Accept the default or choose your own unique URL prefix |
 | Directory | Your Azure Active Directory tenant |
 | Azure subscription | Your Azure subscription |
-| Region | Your nearest region |
+| Location | Your nearest Azure data center |
 
-The examples and screenshots in this article use the **United States** region. Choose a location close to you and make sure you create all your resources in the same region.
+The examples and screenshots in this article use the **East US*** location. Choose a location close to you and make sure you create all your resources in the same location.
 
 This application template includes two simulated thermostat devices that send telemetry.
 
@@ -88,24 +88,27 @@ Use the [Azure portal to create a function app](https://portal.azure.com/#create
 | App name    | Choose your function app name |
 | Subscription | Your subscription |
 | Resource group | DetectStoppedDevices |
-| OS | Windows |
-| Hosting Plan | Consumption Plan |
-| Location | East US |
+| Publish | Code |
 | Runtime Stack | .NET |
+| Region | East US |
+| OS | Windows |
+| Hosting Plan | Consumption (Serverless) |
 | Storage | Create new |
 
 ### SendGrid account and API Keys
 
 If you don't have a Sendgrid account, create a [free account](https://app.sendgrid.com/) before you begin.
 
-1. From the Sendgrid Dashboard Settings on the left menu, select **API Keys**.
-1. Click **Create API Key.**
+1. From the Sendgrid Dashboard, select **Settings** on the left menu, select **Settings > API Keys**.
+1. Select **Create API Key.**
 1. Name the new API key **AzureFunctionAccess.**
-1. Click **Create & View**.
+1. Select **Create & View**.
+
+    :::image type="content" source="media/howto-create-custom-rules/sendgrid-api-keys.png" alt-text="Screenshot that shows how to create a SendGrid API key." lightbox="media/howto-create-custom-rules/sendgrid-api-keys.png":::
 
-    :::image type="content" source="media/howto-create-custom-rules/sendgrid-api-keys.png" alt-text="Screenshot of the Create SendGrid API key.":::
+Make a note of the generated API key, you use it later.
 
-Afterwards, you will be given an API key. Save this string for later use.
+Create a **Single Sender Verification** in your SendGrid account for the email address you'll use as the **From** address.
 
 ## Create an event hub
 
@@ -114,26 +117,24 @@ You can configure an IoT Central application to continuously export telemetry to
 1. In the Azure portal, navigate to your Event Hubs namespace and select **+ Event Hub**.
 1. Name your event hub **centralexport**, and select **Create**.
 
-Your Event Hubs namespace looks like the following screenshot: 
-
-:::image type="content" source="media/howto-create-custom-rules/event-hubs-namespace.png" alt-text="Screenshot of Event Hubs namespace." border="false":::
+:::image type="content" source="media/howto-create-custom-rules/event-hubs-namespace.png" alt-text="Screenshot of the Event Hubs namespace with an event hub." border="false" lightbox="media/howto-create-custom-rules/event-hubs-namespace.png":::
 
 ## Define the function
 
 This solution uses an Azure Functions app to send an email notification when the Stream Analytics job detects a stopped device. To create your function app:
 
-1. In the Azure portal, navigate to the **App Service** instance in the **DetectStoppedDevices** resource group.
-1. Select **+** to create a new function.
-1. Select **HTTP Trigger**.
-1. Select **Add**.
+1. In the Azure portal, navigate to the **Function App** instance in the **DetectStoppedDevices** resource group.
+1. Select **Functions**, then **+ Create** to create a new function.
+1. Select **HTTP Trigger** as the function template.
+1. Select **Create**.
 
-    :::image type="content" source="media/howto-create-custom-rules/add-function.png" alt-text="Image of the Default HTTP trigger function"::: 
+:::image type="content" source="media/howto-create-custom-rules/add-function.png" alt-text="Screenshot of the Azure portal that shows how to create an HTTP trigger function." lightbox="media/howto-create-custom-rules/add-function.png":::
 
 ## Edit code for HTTP Trigger
 
-The portal creates a default function called **HttpTrigger1**:
+The portal creates a default function called **HttpTrigger1**. Select **Code + Test**:
 
-:::image type="content" source="media/howto-create-custom-rules/default-function.png" alt-text="Screenshot of Edit HTTP trigger function.":::
+:::image type="content" source="media/howto-create-custom-rules/default-function.png" alt-text="Screenshot that shows the default function code." lightbox="media/howto-create-custom-rules/default-function.png":::
 
 1. Replace the C# code with the following code:
 
@@ -174,7 +175,6 @@ The portal creates a default function called **HttpTrigger1**:
     }
     ```
 
-    You may see an error message until you save the new code.
 1. Select **Save** to save the function.
 
 ## Add SendGrid Key
@@ -184,48 +184,46 @@ To add your SendGrid API Key, you need to add it to your **Function Keys** as fo
 1. Select **Function Keys**.
 1. Choose **+ New Function Key**.
 1. Enter the *Name* and *Value* of the API Key you created before.
-1. Click **OK.**
-
-    :::image type="content" source="media/howto-create-custom-rules/add-key.png" alt-text="Screenshot of Add Sangrid Key.":::
+1. Select **OK.**
 
+:::image type="content" source="media/howto-create-custom-rules/add-key.png" alt-text="Screenshot of function keys including the SendGridAPI key." lightbox="media/howto-create-custom-rules/add-key.png":::
 
 ## Configure HttpTrigger function to use SendGrid
 
 To send emails with SendGrid, you need to configure the bindings for your function as follows:
 
-1. Select **Integrate**.
-1. Choose **Add Output** under **HTTP ($return)**.
+1. Select **Integration**.
+1. Select **HTTP ($return)**.
 1. Select **Delete.**
-1. Choose **+ New Output**.
-1. For Binding Type, then choose **SendGrid**.
-1. For SendGrid API Key Setting Type, click New.
+1. Select **+ Add output**.
+1. Select **SendGrid** as the binding type.
+1. For the **SendGrid API Key App Setting**, select **New**.
 1. Enter the *Name* and *Value* of your SendGrid API key.
 1. Add the following information:
 
 | Setting | Value |
 | ------- | ----- |
-| Message parameter name | Choose your name |
-| To address | Choose the name of your To Address |
-| From address | Choose the name of your From Address |
-| Message subject | Enter your subject header |
-| Message text | Enter the message from your integration |
+| Message parameter name | name |
+| To address | Enter your To Address |
+| From address | Enter your SendGrid verified single sender email address |
+| Message subject | Device stopped |
+| Message text | The device connected to IoT Central has stopped sending telemetry. |
 
-1. Select **OK**.
-
-    :::image type="content" source="media/howto-create-custom-rules/add-output.png" alt-text="Screenshot of Add SandGrid Output.":::
+1. Select **Save**.
 
+:::image type="content" source="media/howto-create-custom-rules/add-output.png" alt-text="Screenshot of the SendGrid output configuration." lightbox="media/howto-create-custom-rules/add-output.png":::
 
 ### Test the function works
 
-To test the function in the portal, first choose **Logs** at the bottom of the code editor. Then choose **Test** to the right of the code editor. Use the following JSON as the **Request body**:
+To test the function in the portal, first select **Logs** at the bottom of the code editor. Then select **Test/Run**. Use the following JSON as the **Request body**:
 
 ```json
 [{"deviceid":"test-device-1","time":"2019-05-02T14:23:39.527Z"},{"deviceid":"test-device-2","time":"2019-05-02T14:23:50.717Z"},{"deviceid":"test-device-3","time":"2019-05-02T14:24:28.919Z"}]
 ```
 
 The function log messages appear in the **Logs** panel:
 
-:::image type="content" source="media/howto-create-custom-rules/function-app-logs.png" alt-text="Function log output":::
+:::image type="content" source="media/howto-create-custom-rules/function-app-logs.png" alt-text="Screenshot that shows the function log output." lightbox="media/howto-create-custom-rules/function-app-logs.png":::
 
 After a few minutes, the **To** email address receives an email with the following content:
 
@@ -306,9 +304,9 @@ This solution uses a Stream Analytics query to detect when a device stops sendin
 1. Select **Save**.
 1. To start the Stream Analytics job, choose **Overview**, then **Start**, then **Now**, and then **Start**:
 
-    :::image type="content" source="media/howto-create-custom-rules/stream-analytics.png" alt-text="Screenshot of Stream Analytics.":::
+    :::image type="content" source="media/howto-create-custom-rules/stream-analytics.png" alt-text="Screenshot of Stream Analytics overview page." lightbox="media/howto-create-custom-rules/stream-analytics.png":::
 
-## Configure export in IoT Central 
+## Configure export in IoT Central
 
 On the [Azure IoT Central application manager](https://aka.ms/iotcentral) website, navigate to the IoT Central application you created.
 
@@ -322,10 +320,10 @@ In this section, you configure the application to stream the telemetry from its
     | Display Name | Export to Event Hubs |
     | Enabled | On |
     | Type of data to export | Telemetry |
-    | Enrichments | Enter desired key / Value of how you want the exported data to be organized | 
+    | Enrichments | Enter desired key / Value of how you want the exported data to be organized |
     | Destination | Create New and enter information for where the data will be exported |
 
-    :::image type="content" source="media/howto-create-custom-rules/cde-configuration.png" alt-text="Screenshot of the Data Export.":::
+    :::image type="content" source="media/howto-create-custom-rules/cde-configuration.png" alt-text="Screenshot of the data export settings in IoT Central." lightbox="media/howto-create-custom-rules/cde-configuration.png":::
 
 Wait until the export status is **Running** before you continue.
 

articles/iot-central/core/howto-export-to-azure-data-explorer.md

@@ -2,8 +2,8 @@
 title: Export data to Azure Data Explorer IoT Central | Microsoft Docs
 description: How to use the new data export to export your IoT data to Azure Data Explorer
 services: iot-central
-author: eross-msft
-ms.author: lizross
+author: dominicbetts
+ms.author: dobett
 ms.date: 04/28/2022
 ms.topic: how-to
 ms.service: iot-central

articles/iot-central/core/howto-export-to-blob-storage.md

@@ -2,8 +2,8 @@
 title: Export data to Blob Storage IoT Central | Microsoft Docs
 description: How to use the new data export to export your IoT data to Blob Storage
 services: iot-central
-author: eross-msft
-ms.author: lizross
+author: dominicbetts
+ms.author: dobett
 ms.date: 04/28/2022
 ms.topic: how-to
 ms.service: iot-central