Skip to content

Commit 2e57aab

Browse files
authored
Update Azure RBAC considerations for clarity
Clarified the description of role assignment and access needs in Azure RBAC.
1 parent 8bc4deb commit 2e57aab

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

learn-pr/wwl-azure/design-governance/includes/8-design-for-role-based-access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Suppose you need to manage access to resources in Azure for Tailwind Traders Dev
2020

2121
You have a plan for how to apply Azure Policy settings to your Tailwind Traders applications. Now consider how to integrate Azure RBAC to control user privileges and resource access.
2222

23-
- **Consider the highest scope level for each requirement**. Your first step is to accurately define each role definition and its permissions. Next, assign the roles to specific users, groups, and service principles. Lastly, scope the roles to management groups, subscriptions, resource groups, and resources. Assign each role at the highest scope level that meets the requirements.
23+
- **Consider the highest scope level for each requirement**. Your first step is to accurately define each role definition and its permissions. Next, assign the roles to specific users, groups, and service principals. Lastly, scope the roles to management groups, subscriptions, resource groups, and resources. Assign each role at the highest scope level that meets the requirements.
2424

2525
:::image type="content" source="../media/role-definition-assignment-scope.png" alt-text="Diagram that shows how a role definition is assigned to a resource and then scoped." border="false":::
2626

0 commit comments

Comments
 (0)