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
Copy file name to clipboardExpand all lines: articles/iot-hub/iot-hub-create-through-portal.md
+25-22Lines changed: 25 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,61 +34,64 @@ You can change the settings of an existing IoT hub after it's created from the I
34
34
35
35
### Shared access policies
36
36
37
-
You can also view or modify the list of shared access policies by clicking**Shared access policies** in the **Security settings** section. These policies define the permissions for devices and services to connect to IoT Hub.
37
+
You can also view or modify the list of shared access policies by choosing**Shared access policies** in the **Security settings** section. These policies define the permissions for devices and services to connect to IoT Hub.
38
38
39
-
Click**Add shared access policy** to open the **Add shared access policy** blade. You can enter the new policy name and the permissions that you want to associate with this policy, as shown in the following figure:
39
+
Select**Add shared access policy** to open the **Add shared access policy** blade. You can enter the new policy name and the permissions that you want to associate with this policy, as shown in the following figure:
* The **Registry Read** and **Registry Write** policies grant read and write access rights to the identity registry. These permissions are used by back-end cloud services to manage device identities. Choosing the write option automatically chooses the read option.
44
44
45
-
* The **Service Connect** policy grants permission to access service endpoints. This permission is used by back-end cloud services to send and receive messages from devices as well as to update and read device twin and module twin data.
45
+
* The **Service Connect** policy grants permission to access service endpoints. This permission is used by back-end cloud services to send and receive messages from devices. It's also used to update and read device twin and module twin data.
46
46
47
-
* The **Device Connect** policy grants permissions for sending and receiving messages using the IoT Hub device-side endpoints. This permission is used by devices to send and receive messages from an IoT hub, update and read device twin and module twin data, and perform file uploads.
47
+
* The **Device Connect** policy grants permissions for sending and receiving messages using the IoT Hub device-side endpoints. This permission is used by devices to send and receive messages from an IoT hub or update and read device twin and module twin data. It's also used for file uploads.
48
48
49
-
Click**Add** to add this newly created policy to the existing list.
49
+
Select**Add** to add this newly created policy to the existing list.
50
50
51
51
For more detailed information about the access granted by specific permissions, see [IoT Hub permissions](./iot-hub-dev-guide-sas.md#access-control-and-permissions).
Click **Message Routing** under **Messaging** to see the Message Routing pane, where you define routes and custom endpoints for the hub. [Message routing](iot-hub-devguide-messages-d2c.md) enables you to manage how data is sent from your devices to your endpoints. The first step is to add a new route. Then you can add an existing endpoint to the route, or create a new one of the types supported, such as blob storage.
Select **Message Routing** under **Messaging** to see the Message Routing pane, where you define routes and custom endpoints for the hub. [Message routing](iot-hub-devguide-messages-d2c.md) enables you to manage how data is sent from your devices to your endpoints. The first step is to add a new route. Then you can add an existing endpoint to the route, or create a new one of the types supported, such as blob storage.
62
60
63
61
### Routes
64
62
65
-
Routes is the first tab on the Message Routing pane. To add a new route, click +**Add**. You see the following screen.
63
+
**Routes** is the first tab on the **Message Routing** pane. To add a new route, select **+ Add**.
64
+
65
+
66
66
67
-
67
+
You see the following screen.
68
+
69
+
:::image type="content" source="./media/iot-hub-create-through-portal/iot-hub-add-route-storage-endpoint.png" alt-text="Screenshot showing how to add an endpoint to a route." lightbox="./media/iot-hub-create-through-portal/iot-hub-add-route-storage-endpoint.png":::
68
70
69
71
Name your route. The route name must be unique within the list of routes for that hub.
70
72
71
-
For **Endpoint**, you can select one from the dropdown list, or add a new one. In this example, a storage account and container are already available. To add them as an endpoint, click +**Add** next to the Endpoint dropdown and select **Blob Storage**. The following screen shows where the storage account and container are specified.
73
+
For **Endpoint**, select one from the dropdown list or add a new one. In this example, a storage account and container are already available. To add them as an endpoint, choose **+ Add** next to the Endpoint dropdown and select **Blob Storage**.
74
+
75
+
The following screen shows where the storage account and container are specified.
72
76
73
-
77
+
74
78
75
-
Click **Pick a container** to select the storage account and container. When you have selected those fields, it returns to the Endpoint pane. Use the defaults for the rest of the fields and **Create** to create the endpoint for the storage account and add it to the routing rules.
79
+
Add an endpoint name in **Endpoint name** if needed. Select **Pick a container** to select the storage account and container. When you've chosen a container then **Select**, the page returns to the **Add a storage endpoint**pane. Use the defaults for the rest of the fields and **Create** to create the endpoint for the storage account and add it to the routing rules.
76
80
77
-
For **Data source**, select Device Telemetry Messages.
81
+
You return to the **Add a route** page. For **Data source**, select Device Telemetry Messages.
78
82
79
83
Next, add a routing query. In this example, the messages that have an application property called `level` with a value equal to `critical` are routed to the storage account.
80
84
81
85
82
86
83
-
Click**Save** to save the routing rule. You return to the Message Routing pane, and your new routing rule is displayed.
87
+
Select**Save** to save the routing rule. You return to the **Message routing** pane, and your new routing rule is displayed.
84
88
85
89
### Custom endpoints
86
90
87
-
Click the **Custom endpoints** tab. You see any custom endpoints already created. From here, you can add new endpoints or delete existing endpoints.
91
+
Select the **Custom endpoints** tab. You see any custom endpoints already created. From here, you can add new endpoints or delete existing endpoints.
88
92
89
93
> [!NOTE]
90
-
> If you delete a route, it does not delete the endpoints assigned to that route. To delete an endpoint, click the Custom endpoints tab, select the endpoint you want to delete, and click Delete.
91
-
>
94
+
> If you delete a route, it does not delete the endpoints assigned to that route. To delete an endpoint, select the Custom endpoints tab, select the endpoint you want to delete, and choose **Delete**.
92
95
93
96
You can read more about custom endpoints in [Reference - IoT hub endpoints](iot-hub-devguide-endpoints.md).
94
97
@@ -100,13 +103,13 @@ To see a full example of how to use custom endpoints with routing, see [Message
100
103
101
104
Here are two ways to find a specific IoT hub in your subscription:
102
105
103
-
1. If you know the resource group to which the IoT hub belongs, click**Resource groups**, then select the resource group from the list. The resource group screen shows all of the resources in that group, including the IoT hubs. Click on the hub for which you're looking.
106
+
1. If you know the resource group to which the IoT hub belongs, choose**Resource groups**, then select the resource group from the list. The resource group screen shows all of the resources in that group, including the IoT hubs. Select your hub.
104
107
105
-
2.Click**All resources**. On the **All resources** pane, there is a dropdown list that defaults to `All types`. Click on the dropdown list, uncheck `Select all`. Find `IoT Hub` and check it. Click on the dropdown list box to close it, and the entries will be filtered, showing only your IoT hubs.
108
+
2.Choose**All resources**. On the **All resources** pane, there's a dropdown list that defaults to `All types`. Select the dropdown list, uncheck `Select all`. Find `IoT Hub` and check it. Select the dropdown list box to close it, and the entries will be filtered, showing only your IoT hubs.
106
109
107
110
## Delete the IoT hub
108
111
109
-
To delete an Iot hub, find the IoT hub you want to delete, then click the **Delete** button below the IoT hub name.
112
+
To delete an IoT hub, find the IoT hub you want to delete, then choose **Delete**.
Copy file name to clipboardExpand all lines: includes/iot-hub-include-create-device.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,23 +11,23 @@
11
11
---
12
12
<!-- put the ## header in the file that includes this file -->
13
13
14
-
In this section, you create a device identity in the identity registry in your IoT hub. A device cannot connect to a hub unless it has an entry in the identity registry. For more information, see the [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md#identity-registry-operations).
14
+
In this section, you create a device identity in the identity registry in your IoT hub. A device can't connect to a hub unless it has an entry in the identity registry. For more information, see the [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md#identity-registry-operations).
15
15
16
16
1. In your IoT hub navigation menu, open **Devices**, then select **Add Device** to add a device in your IoT hub.
17
17
18
-
:::image type="content" source="./media/iot-hub-include-create-device/create-identity-portal-vs2019.png" alt-text="Screen capture that shows how to create a device identity in the portal" border="true":::
18
+
:::image type="content" source="./media/iot-hub-include-create-device/create-identity-portal.png" alt-text="Screen capture that shows how to create a device identity in the portal." border="true":::
19
19
20
20
1. In **Create a device**, provide a name for your new device, such as **myDeviceId**, and select **Save**. This action creates a device identity for your IoT hub. Leave **Auto-generate keys** checked so that the primary and secondary keys will be generated automatically.
21
21
22
-
:::image type="content" source="./media/iot-hub-include-create-device/create-a-device-vs2019.png" alt-text="Screen capture that shows how to add a new device" border="true":::
22
+
:::image type="content" source="./media/iot-hub-include-create-device/create-device.png" alt-text="Screen capture that shows how to add a new device." border="true":::
1. After the device is created, open the device from the list in the **Devices** pane. Copy the **Primary Connection String**. This connection string is used by device code to communicate with the hub.
27
27
28
-
By default, the keys and connection strings are masked as they are sensitive information. If you click the eye icon, they are revealed. It is not necessary to reveal them to copy them with the copy button.
28
+
By default, the keys and connection strings are masked as they're sensitive information. If you click the eye icon, they're revealed. It's not necessary to reveal them to copy them with the copy button.
29
29
30
-
:::image type="content" source="./media/iot-hub-include-create-device/device-details-vs2019.png" alt-text="Screen capture that shows the device connection string" border="true":::
30
+
:::image type="content" source="./media/iot-hub-include-create-device/device-details.png" alt-text="Screen capture that shows the device connection string." border="true" lightbox="./media/iot-hub-include-create-device/device-details.png":::
31
31
32
32
> [!NOTE]
33
33
> The IoT Hub identity registry only stores device identities to enable secure access to the IoT hub. It stores device IDs and keys to use as security credentials, and an enabled/disabled flag that you can use to disable access for an individual device. If your application needs to store other device-specific metadata, it should use an application-specific store. For more information, see [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md).
Copy file name to clipboardExpand all lines: includes/iot-hub-include-create-hub-cli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ If you already have a device registered in your IoT hub, you can skip this secti
55
55
56
56
To create a device identity:
57
57
58
-
1. Run the [az iot hub device-identity create](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-create) command in your CLI shell. This creates the device identity.
58
+
1. Run the [az iot hub device-identity create](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-create) command in your CLI shell. This command creates the device identity.
59
59
60
60
*YourIotHubName*. Replace this placeholder below with the name you chose for your IoT hub.
Copy file name to clipboardExpand all lines: includes/iot-hub-include-create-hub.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,14 +23,14 @@ This section describes how to create an IoT hub using the [Azure portal](https:/
23
23
-**Subscription**: Select the subscription to use for your hub.
24
24
25
25
-**Resource group**: Select a resource group or create a new one. To create a new one, select **Create new** and fill in the name you want to use. To use an existing resource group, select that resource group. For more information, see [Manage Azure Resource Manager resource groups](../articles/azure-resource-manager/management/manage-resource-groups-portal.md).
26
+
27
+
-**IoT hub name**: Enter a name for your hub. This name must be globally unique, with a length between 3 and 50 alphanumeric characters. The name can also include the dash (`'-'`) character.
26
28
27
29
-**Region**: Select the region in which you want your hub to be located. Select the location closest to you. Some features, such as [IoT Hub device streams](../articles/iot-hub/iot-hub-device-streams-overview.md), are only available in specific regions. For these limited features, you must select one of the supported regions.
28
30
29
-
-**IoT hub name**: Enter a name for your hub. This name must be globally unique, with a length between 3 and 50 alphanumeric characters. The name can also include the dash (`'-'`) character.
:::image type="content" source="./media/iot-hub-include-create-hub/iot-hub-create-screen-basics.png" alt-text="Create a hub in the Azure portal.":::
33
+
:::image type="content" source="./media/iot-hub-include-create-hub/iot-hub-create-screen-basics.png" alt-text="Screenshot that shows how to create an IoT hub in the Azure portal.":::
34
34
35
35
1. Select **Next: Networking** to continue creating your hub.
36
36
@@ -46,14 +46,14 @@ This section describes how to create an IoT hub using the [Azure portal](https:/
46
46
47
47
-**Pricing and scale tier**: Your selected tier. You can choose from several tiers, depending on how many features you want and how many messages you send through your solution per day. The free tier is intended for testing and evaluation. It allows 500 devices to be connected to the hub and up to 8,000 messages per day. Each Azure subscription can create one IoT hub in the free tier.
48
48
49
-
If you are working through a quickstart, select the free tier.
49
+
If you're working through a quickstart, select the free tier.
50
50
51
51
-**IoT Hub units**: The number of messages allowed per unit per day depends on your hub's pricing tier. For example, if you want the hub to support ingress of 700,000 messages, you choose two S1 tier units.
52
52
For details about the other tier options, see [Choosing the right IoT Hub tier](../articles/iot-hub/iot-hub-scaling.md).
53
53
54
-
-**Microsoft Defender for IoT**: Turn this on to add an extra layer of threat protection to IoT and your devices. This option is not available for hubs in the free tier. Learn more about [security recommendations for IoT Hub in Defender for IoT](../articles/defender-for-iot/device-builders/concept-recommendations.md).
54
+
-**Microsoft Defender for IoT**: Turn Defender on to add an extra layer of threat protection to IoT and your devices. This option isn't available for hubs in the free tier. Learn more about [security recommendations for IoT Hub in Defender for IoT](../articles/defender-for-iot/device-builders/concept-recommendations.md).
55
55
56
-
-**Role-based access control**: Choose how access to the IoT hub is managed, whether shared access policies are allowed or only role-based access control is supported. For more information, see [Control access to IoT Hub by using Azure Active Directory](../articles/iot-hub/iot-hub-dev-guide-azure-ad-rbac.md).
56
+
-**Role-based access control**: Choose how to manage access to the IoT hub. Allow shared access policies or choose only role-based access control. For more information, see [Control access to IoT Hub by using Azure Active Directory](../articles/iot-hub/iot-hub-dev-guide-azure-ad-rbac.md).
57
57
58
58
-**Device-to-cloud partitions**: This property relates the device-to-cloud messages to the number of simultaneous readers of the messages. Most hubs need only four partitions.
0 commit comments