Skip to content

Commit 2aa3b16

Browse files
authored
Added links to summary bullets at top
1 parent 66a9f73 commit 2aa3b16

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

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

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -19,17 +19,17 @@ resource properties with different needs for compliance.
1919
2020
You use JavaScript Object Notation (JSON) to create a policy assignment. The policy assignment contains elements for:
2121

22-
- display name
23-
- description
24-
- metadata
25-
- enforcement mode
26-
- excluded scopes
27-
- policy definition
28-
- non-compliance messages
29-
- parameters
30-
- identity
31-
- resource selectors (preview)
32-
- overrides (preview)
22+
- [display name](#display-name-and-description)
23+
- [description](#display-name-and-description)
24+
- [metadata](#metadata)
25+
- [resource selectors (preview)](#resource-selectors-preview)
26+
- [overrides (preview)](#overrides-preview)
27+
- [enforcement mode](#enforcement-mode)
28+
- [excluded scopes](#excluded-scopes)
29+
- [policy definition](#policy-definition-id)
30+
- [non-compliance messages](#non-compliance-messages)
31+
- [parameters](#parameters)
32+
- [identity](#identity)
3333

3434
For example, the following JSON shows a policy assignment in _DoNotEnforce_ mode with dynamic
3535
parameters:

0 commit comments

Comments
 (0)