Merge pull request #110980 from DCtheGeek/dmc-policy-comparisontypes

Clarifying types on conditions

Author: PRMerger12

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

@@ -314,12 +314,16 @@ supported conditions are:
 - `"notIn": ["stringValue1","stringValue2"]`
 - `"containsKey": "keyName"`
 - `"notContainsKey": "keyName"`
-- `"less": "value"`
-- `"lessOrEquals": "value"`
-- `"greater": "value"`
-- `"greaterOrEquals": "value"`
+- `"less": "dateValue"` | `"less": "stringValue"` | `"less": intValue`
+- `"lessOrEquals": "dateValue"` | `"lessOrEquals": "stringValue"` | `"lessOrEquals": intValue`
+- `"greater": "dateValue"` | `"greater": "stringValue"` | `"greater": intValue`
+- `"greaterOrEquals": "dateValue"` | `"greaterOrEquals": "stringValue"` | `"greaterOrEquals": intValue`
 - `"exists": "bool"`
 
+For **less**, **lessOrEquals**, **greater**, and **greaterOrEquals**, if the property type doesn't
+match the condition type, an error is thrown. String comparisons are made using
+`InvariantCultureIgnoreCase`.
+
 When using the **like** and **notLike** conditions, you provide a wildcard `*` in the value.
 The value shouldn't have more than one wildcard `*`.