Skip to content

Commit d2720f1

Browse files
Update device-update-resources.md
1 parent 9a2318a commit d2720f1

File tree

1 file changed

+0
-14
lines changed

1 file changed

+0
-14
lines changed

articles/iot-hub-device-update/device-update-resources.md

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,6 @@ you can select the region where your Device Update account will be created. You
2323
After an account has been created, you need to create a Device Update instance. An instance is a logical container that contains
2424
updates and deployments associated with a specific IoT hub. Device Update uses IoT Hub as a device directory and a communication channel with devices.
2525

26-
During public preview, two Device update accounts can be created per subscription. Additionally, two device update instance can be created per account.
27-
2826
## Configure the linked IoT hub
2927

3028
In order for Device Update to receive change notifications from IoT Hub, Device Update integrates with the built-in Event Hubs. The IoT Hub will be configured automatically as part of the resource creation process with the required message routes, consumer groups, and access policy required to communicate with IoT devices.
@@ -49,18 +47,6 @@ The following Message Routes are automatically configured in your linked IoT hub
4947

5048
:::image type="content" source="media/device-update-resources/consumer-group.png" alt-text="Screenshot of consumer groups." lightbox="media/device-update-resources/consumer-group.png":::
5149

52-
### Configuring access for Azure Device Update service principal in the IoT Hub
53-
54-
Device Update for IoT Hub communicates with the IoT Hub for deployments and manage updates at scale. In order to enable Device Update to do this, users need to set IoT Hub Data Contributor access for Azure Device Update Service Principal in the IoT Hub permissions.
55-
56-
Deployment, device and update management and diagnostic actions will not be allowed if these permissions are not set. Operations that will be blocked will include:
57-
* Create Deployment
58-
* Cancel Deployment
59-
* Retry Deployment
60-
* Get Device
61-
62-
The permission can be set from IoT Hub Access Control (IAM). Refer to [Configure Access for Azure Device update service principal in linked IoT hub](configure-access-control-device-update.md#configure-access-for-azure-device-update-service-principal-in-linked-iot-hub)
63-
6450
## Next steps
6551

6652
[Create device update resources](./create-device-update-account.md)

0 commit comments

Comments
 (0)