Skip to content

Commit 26c84fd

Browse files
Acrolinx may
1 parent 3d0c4da commit 26c84fd

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/governance/policy/concepts/effects.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ manages the evaluation and outcome and reports the results back to Azure Policy.
5050

5151
- **Disabled** is checked first to determine whether the policy rule should be evaluated.
5252
- **Append** and **Modify** are then evaluated. Since either could alter the request, a change made
53-
may prevent an audit or deny effect from triggering. These effects are only available with a
53+
might prevent an audit or deny effect from triggering. These effects are only available with a
5454
Resource Manager mode.
5555
- **Deny** is then evaluated. By evaluating deny before audit, double logging of an undesired
5656
resource is prevented.
@@ -322,7 +322,7 @@ related resources to match.
322322
complete, regardless of outcome. If provisioning takes longer than 6 hours, it's treated as a
323323
failure when determining _AfterProvisioning_ evaluation delays.
324324
- Default is `PT10M` (10 minutes).
325-
- Specifying a long evaluation delay may cause the recorded compliance state of the resource to
325+
- Specifying a long evaluation delay might cause the recorded compliance state of the resource to
326326
not update until the next
327327
[evaluation trigger](../how-to/get-compliance-data.md#evaluation-triggers).
328328
- **ExistenceCondition** (optional)
@@ -626,7 +626,7 @@ related resources to match and the template deployment to execute.
626626
complete, regardless of outcome. If provisioning takes longer than 6 hours, it's treated as a
627627
failure when determining _AfterProvisioning_ evaluation delays.
628628
- Default is `PT10M` (10 minutes).
629-
- Specifying a long evaluation delay may cause the recorded compliance state of the resource to
629+
- Specifying a long evaluation delay might cause the recorded compliance state of the resource to
630630
not update until the next
631631
[evaluation trigger](../how-to/get-compliance-data.md#evaluation-triggers).
632632
- **ExistenceCondition** (optional)
@@ -1020,7 +1020,7 @@ To learn more, go to [Understand Azure Policy for Kubernetes clusters](./policy-
10201020

10211021
## Layering policy definitions
10221022

1023-
A resource may be affected by several assignments. These assignments may be at the same scope or at
1023+
A resource can be affected by several assignments. These assignments might be at the same scope or at
10241024
different scopes. Each of these assignments is also likely to have a different effect defined. The
10251025
condition and effect for each policy is independently evaluated. For example:
10261026

0 commit comments

Comments
 (0)