Skip to content

Commit 3d65190

Browse files
authored
Update scenario-comparison.md
1 parent 84d6ae2 commit 3d65190

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/governance/includes/scenario-comparison.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ ms.author: kenieva
1616
|Create separate groupings that allow for separate aggregations of metrics|Not Supported|Supported|Supported|Supported|Supported**|
1717
|Enforce enterprise-wide restrictions or organizational configurations across many resources|Supported*|Supported*|Supported*|Not Supported|Supported***|
1818

19-
*: When a policy is applied to a scope, the enforcement is to all of the members within the scope Ex. On a Resource Group, it only applies to the resources under it.
19+
*: When a policy is applied to a scope, the enforcement is to all of the members within the scope. For example, on a Resource Group it only applies to the resources under it.
2020

2121
**: Tags can be applied across scopes and are added to resources individually. Azure Policy has built-in policies that can help manage tags.
2222

23-
***: Azure tags can be used as criteria within Azure Policy to apply policies to certain resources. Azure tags are subject to limitations.
23+
***: Azure tags can be used as criteria within Azure Policy to apply policies to certain resources. Azure tags are subject to limitations.

0 commit comments

Comments
 (0)