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/effects.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -754,7 +754,7 @@ you'll need to create an attestation for that compliance state.
754
754
755
755
> [!NOTE]
756
756
> During Public Preview, support for manual policy is available through various Microsoft Defender
757
-
> for Cloud regulatory compliance initiatives.
757
+
> for Cloud regulatory compliance initiatives. If you are a Microsoft Defender for Cloud [Premium tier](https://azure.microsoft.com/pricing/details/defender-for-cloud/) customer, refer to their experience overview.
758
758
759
759
The following example targets Azure subscriptions and sets the initial compliance state to `Unknown`.
760
760
@@ -779,7 +779,7 @@ The `defaultState` property has three possible values:
779
779
-**Compliant**: Resource is compliant according to your manual policy standards
780
780
-**Non-compliant**: Resource is non-compliant according to your manual policy standards
781
781
782
-
The Azure Policy compliance engine evaluates all tracked resources to the default state specified
782
+
The Azure Policy compliance engine evaluates all applicable resources to the default state specified
783
783
in the definition (`Unknown` if not specified). An `Unknown` compliance state indicates that you
784
784
must manually attest the resource compliance state. If the effect state is unspecified, it defaults
785
785
to `Unknown`. The `Unknown` compliance state indicates that you must attest the compliance state yourself.
0 commit comments