Skip to content

Commit 2888320

Browse files
committed
changes
1 parent dd828de commit 2888320

File tree

3 files changed

+12
-12
lines changed

3 files changed

+12
-12
lines changed

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

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -3,31 +3,29 @@ 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/27/2024
6+
ms.date: 12/02/2024
77
ms.topic: how-to
88
ms.service: azure-iot-hub
99
ms.subservice: device-update
1010
---
1111

1212
# Create Azure Device Update for IoT Hub resources
1313

14-
To get started with Azure Device Update for IoT Hub, you create a Device Update account and instance, and then set access control roles as necessary. This article describes how to create and configure Device Update resources by using the Azure portal or Azure CLI.
14+
To get started with Azure Device Update for IoT Hub, you create a Device Update account and instance, and then [assign access control roles and permissions](configure-access-control-device-update.md) as necessary. This article describes how to create and configure Device Update resources by using the Azure portal or Azure CLI.
1515

16-
A Device Update account is a resource in your Azure subscription. A Device Update instance is a logical container within the account that's associated with a specific IoT hub. You can create multiple Device Update instances within an account.
16+
A Device Update *account* is a resource in your Azure subscription. A Device Update *instance* is a logical container within the account that's associated with a specific IoT hub. You can create multiple Device Update instances within an account.
1717

1818
A Device Update instance contains updates and deployments associated with its IoT hub. For more information, see [Device Update resources](device-update-resources.md).
1919

2020
## Prerequisites
2121

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

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
24+
- A Standard (S1) or higher instance of [Azure IoT Hub](/azure/iot-hub/create-hub?tabs=portal).
25+
- If you opt to store diagnostic logs, an Azure Storage account to store diagnostics logs for your Device Update instance.
2726

2827
# [Azure CLI](#tab/cli)
2928

30-
- **Owner** or **User Access Administrator** role permissions in an Azure subscription
3129
- A Standard (S1) or higher instance of [Azure IoT Hub](/azure/iot-hub/create-hub?tabs=portal)
3230
- 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.
3331

@@ -65,17 +63,19 @@ A Device Update instance contains updates and deployments associated with its Io
6563

6664
:::image type="content" source="media/create-device-update-account/account-details.png" alt-text="Screenshot of account details for a new Device Update account.":::
6765

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.
66+
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.
6967

70-
1. To enable diagnostics logging, on the **Diagnostics** tab, slide the toggle to **Microsoft diagnostics logging Enabled**.
68+
If you don't want to enable diagnostics logging now, select the **Networking** tab.
7169

72-
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.
70+
1. On the **Diagnostics** tab, slide the toggle to **Microsoft diagnostics logging Enabled**.
7371

74-
1. Select **Next: Networking**.
72+
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.
7573

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

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).
76+
1. Select **Next: Networking**.
77+
78+
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).
7979

8080
1. Select **Review**.
8181

594 Bytes
Loading
-55 Bytes
Loading

0 commit comments

Comments
 (0)