Skip to content

Commit d4d04d9

Browse files
authored
Update policy-effects.md
updated deployIfNotExists properties details for ExistenceCondition property
1 parent 9cd7d38 commit d4d04d9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-policy/policy-effects.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -204,9 +204,9 @@ related resources to match.
204204
- For _Subscription_, queries the entire subscription for the related resource.
205205
- Default is _ResourceGroup_.
206206
- **ExistenceCondition** (optional)
207-
- If not specified, any related resource of **type** satisfies the effect and does not trigger the audit.
207+
- If not specified, any related resource of **type** satisfies the effect and does not trigger the deployment.
208208
- Uses the same language as the policy rule for the **if** condition, but is evaluated against each related resource individually.
209-
- If any matching related resource evaluates to true, the effect is satisfied and does not trigger the audit.
209+
- If any matching related resource evaluates to true, the effect is satisfied and does not trigger the deployment.
210210
- Can use [field()] to check equivalence with values in the **if** condition.
211211
- As an example, this could be used to validate that the parent resource (in the **if** condition) is in the same resource location as the matching related resource.
212212

@@ -347,4 +347,4 @@ not, then a deployment to enable it is executed.
347347

348348
Now that you have a deeper understanding of policy definition effects, review the policy samples:
349349

350-
- Review more examples at [Azure Policy samples](json-samples.md).
350+
- Review more examples at [Azure Policy samples](json-samples.md).

0 commit comments

Comments
 (0)