Merge pull request #273463 from davidsmatlak/ds-update-policy-effect-basics-20240425

Edit Azure Policy effect and fixes typos

Author: prmerger-automator[bot]

articles/governance/policy/concepts/definition-structure-policy-rule.md

@@ -1,17 +1,17 @@
 ---
 title: Details of the policy definition structure policy rules
 description: Describes how policy definition policy rules are used to establish conventions for Azure resources in your organization.
-ms.date: 04/01/2024
+ms.date: 04/25/2024
 ms.topic: conceptual
 ---
 
 # Azure Policy definition structure policy rule
 
 The policy rule consists of `if` and `then` blocks. In the `if` block, you define one or more conditions that specify when the policy is enforced. You can apply logical operators to these conditions to precisely define the scenario for a policy.
 
-For complete details on each effect, order of evaluation, properties, and examples, see [Understanding Azure Policy Effects](effects.md).
+For complete details on each effect, order of evaluation, properties, and examples, see [Azure Policy definitions effect basics](effect-basics.md).
 
-In the `then` block, you define the effect that happens when the `if conditions are fulfilled.
+In the `then` block, you define the effect that happens when the `if` conditions are fulfilled.
 
 ```json
 {

articles/governance/policy/concepts/effect-basics.md

@@ -1,13 +1,13 @@
 ---
 title: Azure Policy definitions effect basics
 description: Azure Policy definitions effect basics determine how compliance is managed and reported.
-ms.date: 04/08/2024
+ms.date: 04/25/2024
 ms.topic: conceptual
 ---
 
 # Azure Policy definitions effect basics
 
-Each policy definition in Azure Policy has a single `effect`. That `effect` determines what happens when the policy rule is evaluated to match. The effects behave differently if they are for a new resource, an updated resource, or an existing resource.
+Each policy definition in Azure Policy has a single `effect` in its `policyRule`. That `effect` determines what happens when the policy rule is evaluated to match. The effects behave differently if they are for a new resource, an updated resource, or an existing resource.
 
 The following are the supported Azure Policy definition effects:
 
@@ -25,13 +25,13 @@ The following are the supported Azure Policy definition effects:
 
 ## Interchanging effects
 
-Sometimes multiple effects can be valid for a given policy definition. Parameters are often used to specify allowed effect values so that a single definition can be more versatile. However, it's important to note that not all effects are interchangeable. Resource properties and logic in the policy rule can determine whether a certain effect is considered valid to the policy definition. For example, policy definitions with effect `auditIfNotExists` require other details in the policy rule that aren't required for policies with effect `audit`. The effects also behave differently. `audit` policies assess a resource's compliance based on its own properties, while `auditIfNotExists policies assess a resource's compliance based on a child or extension resource's properties.
+Sometimes multiple effects can be valid for a given policy definition. Parameters are often used to specify allowed effect values (`allowedValues`) so that a single definition can be more versatile during assignment. However, it's important to note that not all effects are interchangeable. Resource properties and logic in the policy rule can determine whether a certain effect is considered valid to the policy definition. For example, policy definitions with effect `auditIfNotExists` require other details in the policy rule that aren't required for policies with effect `audit`. The effects also behave differently. `audit` policies assess a resource's compliance based on its own properties, while `auditIfNotExists` policies assess a resource's compliance based on a child or extension resource's properties.
 
 The following list is some general guidance around interchangeable effects:
 
 - `audit`, `deny`, and either `modify` or `append` are often interchangeable.
 - `auditIfNotExists` and `deployIfNotExists` are often interchangeable.
-- `Manual` isn't interchangeable.
+- `manual` isn't interchangeable.
 - `disabled` is interchangeable with any effect.
 
 ## Order of evaluation