Merge pull request #250144 from shanhix1/patch-4

Clarified applicability logic

Author: prmerger-automator[bot]

articles/governance/policy/concepts/policy-applicability.md

@@ -14,6 +14,7 @@ Applicability is determined by several factors:
 - **Conditions** in the `if` block of the [policy rule](../concepts/definition-structure.md#policy-rule).
 - **Mode** of the policy definition.
 - **Excluded scopes** specified in the assignment. 
+- **Resource selectors** specified in the assignment. 
 - **Exemptions** of resources or resource hierarchies.
 
 Condition(s) in the `if` block of the policy rule are evaluated for applicability in slightly different ways based on the effect.
@@ -34,7 +35,10 @@ Following are special cases to the previously described applicability logic:
 |Any invalid aliases in the `if` conditions     |The policy isn't applicable |
 |When the `if` conditions consist of only `kind` conditions     |The policy is applicable to all resources |
 |When the `if` conditions consist of only `name` conditions     |The policy is applicable to all resources |
-|When the `if` conditions consist of only `type` and `kind` or `type` and `name` conditions     |Only type conditions are considered when deciding applicability |
+|When the `if` conditions consist of only `type` and `kind` conditions     |Only `type` conditions are considered when deciding applicability |
+|When the `if` conditions consist of only `type` and `name` conditions     |Only `type` conditions are considered when deciding applicability |
+|When the `if` conditions consist of `type`, `kind`, and other conditions |Both `type` and `kind` conditions are considered when deciding applicability |
+|When the `if` conditions consist of `type`, `name`, and other conditions |Both `type` and `name` conditions are considered when deciding applicability |
 |When any conditions (including deployment parameters) include a `location` condition     |Won't be applicable to subscriptions |
 
 ### AuditIfNotExists and DeployIfNotExists policy effects