Skip to content

Commit 66560cf

Browse files
Merge pull request #215216 from timwarner-msft/timwarner-dis
Add clarifying note for Disabled effect
2 parents b15d870 + b44f6c0 commit 66560cf

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

articles/governance/policy/concepts/effects.md

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Understand how effects work
33
description: Azure Policy definitions have various effects that determine how compliance is managed and reported.
44
author: timwarner-msft
5-
ms.date: 09/23/2022
5+
ms.date: 10/20/2022
66
ms.topic: conceptual
77
ms.author: timwarner
88
---
@@ -613,8 +613,11 @@ This effect is useful for testing situations or for when the policy definition h
613613
effect. This flexibility makes it possible to disable a single assignment instead of disabling all
614614
of that policy's assignments.
615615

616-
An alternative to the Disabled effect is **enforcementMode**, which is set on the policy assignment.
617-
When **enforcementMode** is _Disabled_, resources are still evaluated. Logging, such as Activity
616+
> [!NOTE]
617+
> Policy definitions that use the **Disabled** effect have the default compliance state **Compliant** after assignment.
618+
619+
An alternative to the **Disabled** effect is **enforcementMode**, which is set on the policy assignment.
620+
When **enforcementMode** is **Disabled**_**, resources are still evaluated. Logging, such as Activity
618621
logs, and the policy effect don't occur. For more information, see
619622
[policy assignment - enforcement mode](./assignment-structure.md#enforcement-mode).
620623

0 commit comments

Comments
 (0)