You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Create an Azure Device Update for Iot Hub account and instance by using the Azure portal or Azure CLI.
4
4
author: eshashah-msft
5
5
ms.author: eshashah
6
-
ms.date: 11/27/2024
6
+
ms.date: 12/02/2024
7
7
ms.topic: how-to
8
8
ms.service: azure-iot-hub
9
9
ms.subservice: device-update
10
10
---
11
11
12
12
# Create Azure Device Update for IoT Hub resources
13
13
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.
15
15
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.
17
17
18
18
A Device Update instance contains updates and deployments associated with its IoT hub. For more information, see [Device Update resources](device-update-resources.md).
19
19
20
20
## Prerequisites
21
21
22
22
# [Azure portal](#tab/portal)
23
23
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.
27
26
28
27
# [Azure CLI](#tab/cli)
29
28
30
-
-**Owner** or **User Access Administrator** role permissions in an Azure subscription
31
29
- A Standard (S1) or higher instance of [Azure IoT Hub](/azure/iot-hub/create-hub?tabs=portal)
32
30
- 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.
33
31
@@ -65,17 +63,19 @@ A Device Update instance contains updates and deployments associated with its Io
65
63
66
64
:::image type="content" source="media/create-device-update-account/account-details.png" alt-text="Screenshot of account details for a new Device Update account.":::
67
65
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.
69
67
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.
71
69
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**.
73
71
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.
75
73
76
74
:::image type="content" source="media/create-device-update-account/account-diagnostics.png" alt-text="Screenshot of diagnostic details.":::
77
75
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).
0 commit comments