Skip to content

Commit 711257e

Browse files
authored
Merge pull request #223486 from maud-lv/ml-ac-rbac
Update role assignments
2 parents d052726 + 449c5dc commit 711257e

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed
Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,22 +1,23 @@
11
---
2-
author: AlexandraKemperMS
3-
ms.author: alkemper
2+
author: maud-lv
3+
ms.author: malev
44
ms.service: azure-app-configuration
55
ms.topic: include
6-
ms.date: 05/03/2021
6+
ms.date: 01/10/2023
7+
ms.custom: engagement-fy23
78
---
89

910
Assign the proper App Configuration role assignments to the credentials being used within the task so that the task can access the App Configuration store.
1011

11-
1. Go to your target App Configuration store.
12+
1. Go to your target App Configuration store.
1213
1. In the left menu, select **Access control (IAM)**.
1314
1. In the right pane, select **Add role assignments**.
14-
15+
1516
:::image type="content" source="./media/azure-app-configuration-role-assignment/add-role-assignment-button.png" alt-text="Screenshot shows the Add role assignments button.":::
1617

17-
1. For **Role**, select **App Configuration Data Owner**. This role allows the task to read from and write to the App Configuration store.
18+
1. For **Role**, select **App Configuration Data Owner**. This role allows the task to read from and write to the App Configuration store.
1819
1. Select the service principal associated with the service connection that you created in the previous section.
1920

2021
:::image type="content" source="./media/azure-app-configuration-role-assignment/add-role-assignment.png" alt-text="Screenshot shows the Add role assignment dialog.":::
2122

22-
1. If the store contains Key Vault references, go to relevant Key Vault and assign **Key Vault Secret User** role to the service principal created in the previous step. From the Key Vault menu, select **Access policies** and ensure [Azure role-based access control](../articles/key-vault/general/rbac-guide.md) is selected as the permission model.
23+
1. If the store contains Key Vault references, go to relevant Key Vault and assign **Key Vault Secret User** role to the service principal created in the previous step. From the Key Vault menu, select **Access configuration** and ensure [Azure role-based access control](../articles/key-vault/general/rbac-guide.md) is selected as the permission model.

0 commit comments

Comments
 (0)