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
This article describes how to create and manage IoT hubs using the [Azure portal](https://portal.azure.com).
18
18
19
+
To use the steps in this tutorial, you need an Azure subscription. If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
@@ -32,29 +34,29 @@ You can change the settings of an existing IoT hub after it's created from the I
32
34
33
35
### Shared access policies
34
36
35
-
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.
36
38
37
-
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.
42
44
43
-
* 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.
44
46
45
-
* 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.
46
48
47
-
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.
48
50
49
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.
59
+
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.
58
60
59
61
### Routes
60
62
@@ -80,7 +82,7 @@ You return to the **Add a route** page. For **Data source**, select Device Telem
80
82
81
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.
82
84
83
-
85
+
84
86
85
87
Select **Save** to save the routing rule. You return to the **Message routing** pane, and your new routing rule is displayed.
86
88
@@ -89,8 +91,7 @@ Select **Save** to save the routing rule. You return to the **Message routing**
89
91
Select the **Custom endpoints** tab. You see any custom endpoints already created. From here, you can add new endpoints or delete existing endpoints.
90
92
91
93
> [!NOTE]
92
-
> 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.
93
-
>
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**.
94
95
95
96
You can read more about custom endpoints in [Reference - IoT hub endpoints](iot-hub-devguide-endpoints.md).
96
97
@@ -102,17 +103,17 @@ To see a full example of how to use custom endpoints with routing, see [Message
102
103
103
104
Here are two ways to find a specific IoT hub in your subscription:
104
105
105
-
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.
106
107
107
-
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.
108
109
109
110
## Delete the IoT hub
110
111
111
-
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**.
112
113
113
114
## Next steps
114
115
115
116
Follow these links to learn more about managing Azure IoT Hub:
116
117
117
118
*[Message routing with IoT Hub](tutorial-routing.md)
0 commit comments