You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/governance/policy/concepts/policy-applicability.md
+4-15Lines changed: 4 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Azure Policy applicability logic
3
3
description: Describes the rules Azure Policy uses to determine whether the policy is applied to its assigned resources.
4
-
ms.date: 05/19/2022
4
+
ms.date: 05/20/2022
5
5
ms.topic: conceptual
6
6
ms.author: timwarner
7
7
author: timwarner-msft
@@ -21,28 +21,17 @@ Following are special cases to the previously described applicability logic:
21
21
- Any invalid aliases in the ****If**** conditions
22
22
- The policy is not applicable
23
23
- When the **If** conditions consist of only type conditions
24
-
- The policy is applicable to all resources. (Legacy logic. Configurable)
24
+
- The policy is applicable to all resources.
25
25
- When the **If** conditions consist of only name conditions
26
26
- The policy is applicable to all resources.
27
27
- When the **If** conditions consist of only type and name conditions
28
-
- It depends on which field the first condition in the **If** refers to. It applies the applicability logic with conditions with that field only. E.g. when "type" field appears in the first condition of the **If**, only type conditions are considered when deciding applicability. When "name" field appears in the first condition of the **If**, only name conditions are considered when deciding applicability.
28
+
- It depends on which field the first condition in the **If** refers to. It applies the applicability logic with conditions with that field only. E.g. when **type** field appears in the first condition of the **If**, only type conditions are considered when deciding applicability. When **name** field appears in the first condition of the **If**, only name conditions are considered when deciding applicability.
29
29
- When any conditions (including deployment parameters) include a location condition
30
30
- Will not be applicable to subscriptions
31
31
32
32
## Applicability logic for AuditIfNotExists and DeployIfNotExists policy effects
0 commit comments