Skip to content

Commit 017a597

Browse files
Merge pull request #223209 from timwarner-msft/timwarner-denyaction
Remove Preview tags from DenyAction
2 parents 75840ab + 3133a56 commit 017a597

File tree

2 files changed

+3
-6
lines changed

2 files changed

+3
-6
lines changed

articles/governance/policy/concepts/effects.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ These effects are currently supported in a policy definition:
1818
- [Audit](#audit)
1919
- [AuditIfNotExists](#auditifnotexists)
2020
- [Deny](#deny)
21-
- [DenyAction (preview)](#denyaction-preview)
21+
- [DenyAction](#denyaction)
2222
- [DeployIfNotExists](#deployifnotexists)
2323
- [Disabled](#disabled)
2424
- [Manual (preview)](#manual-preview)
@@ -453,7 +453,7 @@ location of the Constraint template to use in Kubernetes to limit the allowed co
453453
}
454454
}
455455
```
456-
## DenyAction (preview)
456+
## DenyAction
457457

458458
`DenyAction` is used to block requests on intended action to resources. The only supported action today is `DELETE`. This effect will help prevent any accidental deletion of critical resources.
459459

@@ -464,9 +464,6 @@ assignment.
464464

465465
`Microsoft.Authorization/policyAssignments`, `Microsoft.Authorization/denyAssignments`, `Microsoft.Blueprint/blueprintAssignments`, `Microsoft.Resources/deploymentStacks`, and `Microsoft.Authorization/locks` are all exempt from DenyAction enforcement to prevent lockout scenarios.
466466

467-
> [!NOTE]
468-
> Under preview, assignments with `denyAction` effect will show a `Not Started` compliance state.
469-
470467
#### Subscription deletion
471468
Policy won't block removal of resources that happens during a subscription deletion.
472469

articles/governance/policy/concepts/evaluate-impact.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ reviews the request. When the policy definition effect is [Modify](./effects.md#
1212
[Append](./effects.md#deny), or [DeployIfNotExists](./effects.md#deployifnotexists), Policy alters
1313
the request or adds to it. When the policy definition effect is [Audit](./effects.md#audit) or
1414
[AuditIfNotExists](./effects.md#auditifnotexists), Policy causes an Activity log entry to be created
15-
for new and updated resources. And when the policy definition effect is [Deny](./effects.md#deny) or [DenyAction](./effects.md#denyaction-preview), Policy stops the creation or alteration of the request.
15+
for new and updated resources. And when the policy definition effect is [Deny](./effects.md#deny) or [DenyAction](./effects.md#denyaction), Policy stops the creation or alteration of the request.
1616

1717
These outcomes are exactly as desired when you know the policy is defined correctly. However, it's
1818
important to validate a new policy works as intended before allowing it to change or block work. The

0 commit comments

Comments
 (0)