Skip to content

Commit 321f967

Browse files
committed
touchups
1 parent 70acee1 commit 321f967

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

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

Lines changed: 6 additions & 4 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: 12/02/2024
6+
ms.date: 12/03/2024
77
ms.topic: how-to
88
ms.service: azure-iot-hub
99
ms.subservice: device-update
@@ -55,7 +55,9 @@ A Device Update instance contains updates and deployments associated with its Io
5555
- **Name**: Provide a name for your Device Update account.
5656
- **Location**: Select the Azure region for your account. For more information, see [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
5757
- **SKU**: Select **Standard**.
58-
- **Grant Access to Account**: If you have **Owner** or **User Access Administrator** permissions in your Azure subscription, you can select the **Assign Device Update Administrator role** checkbox to assign yourself the **Device Update Administrator** role for this account. If you don't have these permissions, contact your administrator after resource creation to get the necessary permissions to do device updates, management, and diagnostics.
58+
- **Grant Access to Account**
59+
- If you have **Owner** or **User Access Administrator** permissions in your Azure subscription, you can select the **Assign Device Update Administrator role** checkbox to assign yourself the **Device Update Administrator** role for this account.
60+
- If you don't have these permissions, contact your administrator after resource creation to get the necessary permissions to work with these resources. For more information, see [Configure access control roles for Device Update resources](configure-access-control-device-update.md).
5961
- **Instance Name**: Provide a name for your Device Update instance.
6062
- **IoT Hub Name**: Select the IoT Hub you want to link to your Device Update instance.
6163
- **Grant Access to IoT Hub**: Device Update setup automatically assigns IoT Hub Data Contributor role to the Device Update service principal.
@@ -72,7 +74,7 @@ A Device Update instance contains updates and deployments associated with its Io
7274

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

75-
1. Select **Next: Networking**.
77+
1. Select the **Networking** tab or **Next: Networking**.
7678

7779
1. On the **Networking** tab, you can choose the endpoints that devices use to connect to your Device Update instance. For this example, 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](configure-private-endpoints.md).
7880

@@ -132,7 +134,7 @@ You can also configure diagnostics logging as part of the instance creation proc
132134
133135
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.
134136
135-
If you have **Owner** or **User Access Administrator** permissions in your Azure subscription, you can configure access control to the Device Update resources you created by using a combination of roles to provide users and applications the right level of access. If you don't have **Owner** or **User Access Administrator** permissions, ask your Device Update administrator to grant you the access and permissions you need to do Device Update operations. For more information, see [Configure access control roles for Device Update resources](configure-access-control-device-update.md).
137+
If you have **Owner** or **User Access Administrator** permissions in your Azure subscription, you can configure access control by providing users and applications the necessary level of access to the Device Update resources you created. If you don't have **Owner** or **User Access Administrator** permissions, ask your Device Update administrator to grant you the access and permissions you need to perform Device Update update, management, and diagnostic operations. For more information, see [Configure access control roles for Device Update resources](configure-access-control-device-update.md).
136138
137139
## Related content
138140

0 commit comments

Comments
 (0)