Skip to content

Commit b236b8d

Browse files
committed
Added error state
1 parent e5cc296 commit b236b8d

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

articles/governance/policy/concepts/compliance-states.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,10 @@ Policy assignments with `manual` effects are considered compliant under two circ
4040
1. The policy definition has a default compliance state of compliant and there is no active [attestation](./attestation-structure.md) for the applicable resource stating otherwise.
4141
1. The resource has been attested as compliant.
4242

43+
### Error
44+
45+
The error compliance state is given to policy assignments that generate a system error, such as template or evaluation error.
46+
4347
### Conflicting
4448

4549
A policy assignment is considered conflicting when there are two or more policy assignments existing in the same scope with contradicting or conflicting rules. For example, two definitions that append the same tag with different values.
@@ -105,7 +109,8 @@ There are several ways to view aggregated compliance results in the portal:
105109
So how is the aggregate compliance state determined if multiple resources or policies have different compliance states themselves? Azure Policy ranks each compliance state so that one "wins" over another in this situation. The rank order is:
106110
1. Non-compliant
107111
1. Compliant
108-
1. Conflict
112+
1. Error
113+
1. Conflicting
109114
1. Exempted
110115
1. Unknown (preview)
111116

0 commit comments

Comments
 (0)