Skip to content

Commit eb48c81

Browse files
Merge pull request #278245 from shanhix1/shannonhicks/clarify-initiative
Clarified why you might want to create an initiative even for a single policy definition
2 parents dae6dca + 51fda08 commit eb48c81

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/governance/policy/overview.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -179,12 +179,11 @@ Here are a few pointers and tips to keep in mind:
179179
the assignment can be scoped down to a subscription or resource group within that management
180180
group.
181181

182-
- We recommend creating and assigning initiative definitions even for a single policy definition.
183-
For example, you have policy definition _policyDefA_ and create it under initiative definition
184-
_initiativeDefC_. If you create another policy definition later for _policyDefB_ with goals
185-
similar to _policyDefA_, you can add it under _initiativeDefC_ and track them together.
182+
- We recommend creating and assigning initiative definitions even if starting with a single policy definition. This enables you to add policy definitions to the initiative later without increasing the number of assignments to manage.
186183

187-
- Once you've created an initiative assignment, policy definitions added to the initiative also
184+
- For example, imagine you create policy definition _policyDefA_ and add it to initiative definition _initiativeDefC_. If you later create another policy definition _policyDefB_ with goals similar to _policyDefA_, you can add it under _initiativeDefC_ and track them together.
185+
186+
- Once you've created an initiative assignment, policy definitions added to the initiative also
188187
become part of that initiative's assignments.
189188

190189
- When an initiative assignment is evaluated, all policies within the initiative are also evaluated.

0 commit comments

Comments
 (0)