Skip to content

Commit 47e3a43

Browse files
Update device-update-control-access.md
1 parent 3e44b00 commit 47e3a43

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/iot-hub-device-update/device-update-control-access.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: iot-hub-device-update
1010

1111
# Azure Role-based access control (RBAC) and Device Update
1212

13-
Device Update uses Azure RBAC to provide authentication and authorization for users and service APIs. In order for other users and applications to have access to Device Update, users or applications must be granted access to this resource. It is also necessary to [configure access for Azure Device Update service principal](./device-update-control-access.md.md) for successfully deploying updates and managing your devices.
13+
Device Update uses Azure RBAC to provide authentication and authorization for users and service APIs. In order for other users and applications to have access to Device Update, users or applications must be granted access to this resource. It is also necessary to [configure access for Azure Device Update service principal](https://docs.microsoft.com/en-us/rest/api/deviceupdate/2021-06-01-preview/device-management) for successfully deploying updates and managing your devices.
1414

1515
## Configure access control roles
1616

@@ -31,13 +31,13 @@ A combination of roles can be used to provide the right level of access. For exa
3131

3232
Device Update for IoT Hub uses [Automatic Device Management](https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-automatic-device-management) for deployments and uses ADM configs to perform device management operations like updates at scale. In order to enable Device Update to do this, users need to set Contributor access for Azure Device Update Service Principal in the IoT Hub permissions.
3333

34-
Below actions will be blocked if these permissions are not set:
34+
Below actions will be blocked (after 9/28/22) if these permissions are not set:
3535
* Create Deployment
3636
* Cancel Deployment
3737
* Retry Deployment
3838
* Get Device
3939

40-
1. Go to the **IoT Hub** connected to your Device Update Instance and click **Access Control(IAM)**
40+
1. Go to the **IoT Hub** connected to your Device Update Instance. Click **Access Control(IAM)**
4141
2. Click **+ Add** -> **Add role assignment**
4242
3. Under Role tab, select **Contributor**
4343
4. Click **Next**. For **Assign access to**, select **User, group, or service principal**. Click **+ Select Members**, search for '**Azure Device Update**'

0 commit comments

Comments
 (0)