Skip to content

Commit dd828de

Browse files
committed
most review changes
1 parent e6070e2 commit dd828de

File tree

4 files changed

+10
-10
lines changed

4 files changed

+10
-10
lines changed

articles/iot-hub-device-update/create-device-update-account.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create Azure Device Update for IoT Hub resources
33
description: Create an Azure Device Update for Iot Hub account and instance by using the Azure portal or Azure CLI.
44
author: eshashah-msft
55
ms.author: eshashah
6-
ms.date: 11/19/2024
6+
ms.date: 11/27/2024
77
ms.topic: how-to
88
ms.service: azure-iot-hub
99
ms.subservice: device-update
@@ -21,14 +21,14 @@ A Device Update instance contains updates and deployments associated with its Io
2121

2222
# [Azure portal](#tab/portal)
2323

24-
- **Owner** or **User Access Administrator** role permissions in an Azure subscription
25-
- A Standard (S1) or higher instance of Azure IoT Hub
26-
- An Azure Storage account to store diagnostics logs for your Device Update instance
24+
- To create the resources in this article, **Owner** or **User Access Administrator** role permissions in an Azure subscription
25+
- A Standard (S1) or higher instance of [Azure IoT Hub](/azure/iot-hub/create-hub?tabs=portal)
26+
- If you opt to store diagnostic logs, an Azure Storage account to store diagnostics logs for your Device Update instance
2727

2828
# [Azure CLI](#tab/cli)
2929

3030
- **Owner** or **User Access Administrator** role permissions in an Azure subscription
31-
- A Standard (S1) or higher instance of Azure IoT Hub
31+
- A Standard (S1) or higher instance of [Azure IoT Hub](/azure/iot-hub/create-hub?tabs=portal)
3232
- The Bash environment in [Azure Cloud Shell](/azure/cloud-shell/quickstart) for running Azure CLI commands. Select **Launch Cloud Shell** to open Cloud Shell now, or select the Cloud Shell icon in the top toolbar of the Azure portal.
3333

3434
:::image type="icon" source="~/reusable-content/ce-skilling/azure/media/cloud-shell/launch-cloud-shell-button.png" alt-text="Button to launch the Azure Cloud Shell." border="false" link="https://shell.azure.com":::
@@ -63,19 +63,19 @@ A Device Update instance contains updates and deployments associated with its Io
6363

6464
If you have the required **Owner** or **User Access Administrator** permissions in your Azure subscription, Device Update setup automatically assigns IoT Hub Data Contributor role to the Device Update service principal.
6565

66-
1. Select **Next: Diagnostics**
67-
6866
:::image type="content" source="media/create-device-update-account/account-details.png" alt-text="Screenshot of account details for a new Device Update account.":::
6967

70-
1. On the **Diagnostics** tab, slide the toggle to **Microsoft diagnostics logging Enabled**. Enabling Microsoft diagnostics allows Microsoft to collect, store, and analyze diagnostic log files from your devices if they encounter an update failure.
68+
1. Optionally, select **Next: Diagnostics** or the **Diagnostics** tab to configure diagnostics logging as part of the instance creation process. Enabling Microsoft diagnostics allows Microsoft to collect, store, and analyze diagnostic log files from your devices if they encounter an update failure. Otherwise, select the **Networking** tab.
69+
70+
1. To enable diagnostics logging, on the **Diagnostics** tab, slide the toggle to **Microsoft diagnostics logging Enabled**.
7171

7272
1. Select **Select Azure Storage Account** and then select an Azure Blob storage account to link to your Device Update instance for remote diagnostic log collection. The Storage account details update automatically.
7373

7474
1. Select **Next: Networking**.
7575

7676
:::image type="content" source="media/create-device-update-account/account-diagnostics.png" alt-text="Screenshot of diagnostic details.":::
7777

78-
1. On the **Networking** tab, you choose the endpoints that devices can use to connect to your Device Update instance. For this example, select **Public access**.
78+
1. On the **Networking** tab, you can choose the endpoints that devices use to connect to your Device Update instance. For this example, you can select **Public access**. Public access is acceptable for development and testing purposes, but for production scenarios, you should choose **Private access** and [configure private endpoint connections](onfigure-private-endpoints.md).
7979

8080
1. Select **Review**.
8181

@@ -131,7 +131,7 @@ You can also configure diagnostics logging as part of the instance creation proc
131131
132132
## Configure access
133133
134-
Device Update setup automatically assigns **IoT Hub Data Contributor** role to the Device Update service principal. This role allows the Device Update instance to connect and write to the linked IoT hub to run deployment, device management, and diagnostic operations. Only this Device Update service principal can access this IoT hub.
134+
Device Update setup automatically assigns **IoT Hub Data Contributor** role to the Device Update service principal. This role allows only this Device Update instance to connect and write to the linked IoT hub to run update deployment, device management, and diagnostic operations.
135135
136136
If you have the required **Owner** or **User Access Administrator** permissions in your Azure subscription, you can configure access control to your Device Update resources by using a combination of roles to provide users and applications the right level of access. For more information, see [Configure access control roles for Device Update resources](configure-access-control-device-update.md).
137137
-75 Bytes
Loading
-152 Bytes
Loading
-81 Bytes
Loading

0 commit comments

Comments
 (0)