Skip to content

Commit 91599f1

Browse files
authored
clarified manual policy best practice in effect article
1 parent 773b70a commit 91599f1

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

articles/governance/policy/concepts/effects.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -747,10 +747,7 @@ Example: Gatekeeper v2 admission control rule to allow only the specified contai
747747

748748
## Manual (preview)
749749

750-
The new `manual` (preview) effect enables you to define and track your own custom attestation
751-
resources. Unlike other Policy definitions that actively scan for evaluation, the Manual effect
752-
allows for manual changes to the compliance state. To change the compliance for a manual policy,
753-
you'll need to create an attestation for that compliance state.
750+
The new `manual` (preview) effect enables you to self-attest the compliance of resources or scopes. Unlike other policy definitions that actively scan for evaluation, the Manual effect allows for manual changes to the compliance state. To change the compliance of a resource or scope targeted by a manual policy, you'll need to create an [attestation](attestation-structure.md). The [best practice](attestation-structure.md#best-practices) is to design manual policies that target the scope which defines the boundary of resources whose compliance need attesting.
754751

755752
> [!NOTE]
756753
> During Public Preview, support for manual policy is available through various Microsoft Defender

0 commit comments

Comments
 (0)