Skip to content

Commit 4f7cb5a

Browse files
authored
Added MDC Premium tier to Note and clarified 'applicable' resources
1 parent c947820 commit 4f7cb5a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/governance/policy/concepts/effects.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -754,7 +754,7 @@ you'll need to create an attestation for that compliance state.
754754

755755
> [!NOTE]
756756
> 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.
758758
759759
The following example targets Azure subscriptions and sets the initial compliance state to `Unknown`.
760760

@@ -779,7 +779,7 @@ The `defaultState` property has three possible values:
779779
- **Compliant**: Resource is compliant according to your manual policy standards
780780
- **Non-compliant**: Resource is non-compliant according to your manual policy standards
781781

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
783783
in the definition (`Unknown` if not specified). An `Unknown` compliance state indicates that you
784784
must manually attest the resource compliance state. If the effect state is unspecified, it defaults
785785
to `Unknown`. The `Unknown` compliance state indicates that you must attest the compliance state yourself.

0 commit comments

Comments
 (0)