Skip to content

Commit 1bc0c1b

Browse files
authored
public repo edits
1 parent 5ee4886 commit 1bc0c1b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.topic: conceptual
66
---
77
# Azure Policy definition structure
88

9-
Azure Policies establish conventions for resources. Policy definitions describe resource compliance condition and the effect to take if the condition is met. This [condition](#conditions) compares a resource property [field](#fields) to a required value. Resource property fields are accessed using [aliases](#aliases) and are either single valued field or an [array](#understanding-the--alias) of multiple values. The condition evaluation is different on arrays - see [condition](#conditions) for details.
9+
Azure Policy establishes conventions for resources. Policy definitions describe resource compliance [conditions](#conditions) and the effect to take if a condition is met. A condition compares a resource property [field](#fields) to a required value. Resource property fields are accessed by using [aliases](#aliases). A resource property field is either a single-valued field or an [array](#understanding-the--alias) of multiple values. Condition evaluation is different on arrays. Learn more about [conditions](#conditions).
1010

1111
By defining conventions, you can control costs and more easily manage your resources. For example,
1212
you can specify that only certain types of virtual machines are allowed. Or, you can require that
@@ -310,8 +310,8 @@ letter, `.` to match any character, and any other character to match that actual
310310
**match** and **notMatch** are case-sensitive. Case-insensitive alternatives are available in
311311
**matchInsensitively** and **notMatchInsensitively**. For examples, see [Allow several name patterns](../samples/allow-multiple-name-patterns.md).
312312

313-
When working with **\[\*\] alias** array field values, every element of the
314-
array is evaluated individually with logical AND between them. For details see
313+
In an **\[\*\] alias** array field value, every element in the
314+
array is evaluated individually, with logical AND between elements. For more information, see
315315
[Evaluating the \[\*\] alias](../how-to/author-policies-for-arrays.md#evaluating-the--alias).
316316

317317
### Fields

0 commit comments

Comments
 (0)