You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/governance/policy/concepts/compliance-states.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,10 @@ Policy assignments with `manual` effects are considered compliant under two circ
40
40
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.
41
41
1. The resource has been attested as compliant.
42
42
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
+
43
47
### Conflicting
44
48
45
49
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:
105
109
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:
0 commit comments