Skip to content

Commit e14fbee

Browse files
authored
Merge pull request #102876 from DCtheGeek/dmc-bp-excludedactions
Add info for excludedActions
2 parents 3381add + 32a2cd9 commit e14fbee

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

articles/governance/blueprints/concepts/resource-locking.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -127,6 +127,32 @@ request body that includes **excludedPrincipals**:
127127
}
128128
```
129129

130+
## Exclude an action from a deny assignment
131+
132+
Similar to [excluding a principal](#exclude-a-principal-from-a-deny-assignment) on a
133+
[deny assignment](../../../role-based-access-control/deny-assignments.md) in a blueprint assignment,
134+
you can exclude specific
135+
[RBAC operations](../../../role-based-access-control/resource-provider-operations.md). Within the
136+
**properties.locks** block, in the same place that **excludedPrincipals** is, an **excludedActions**
137+
can be added:
138+
139+
```json
140+
"locks": {
141+
"mode": "AllResourcesDoNotDelete",
142+
"excludedPrincipals": [
143+
"7be2f100-3af5-4c15-bcb7-27ee43784a1f",
144+
"38833b56-194d-420b-90ce-cff578296714"
145+
],
146+
"excludedActions": [
147+
"Microsoft.ContainerRegistry/registries/push/write",
148+
"Microsoft.Authorization/*/read"
149+
]
150+
},
151+
```
152+
153+
While **excludedPrincipals** must be explicit, **excludedActions** entries can make use of `*` for
154+
wildcard matching of RBAC operations.
155+
130156
## Next steps
131157

132158
- Follow the [protect new resources](../tutorials/protect-new-resources.md) tutorial.

0 commit comments

Comments
 (0)