|
1 | 1 | ---
|
2 | 2 | title: Details of the policy definition structure
|
3 | 3 | description: Describes how policy definitions are used to establish conventions for Azure resources in your organization.
|
4 |
| -ms.date: 08/15/2023 |
| 4 | +ms.date: 03/21/2024 |
5 | 5 | ms.topic: conceptual
|
6 | 6 | ---
|
7 | 7 |
|
@@ -76,19 +76,19 @@ Azure Policy built-ins and patterns are at [Azure Policy samples](../samples/ind
|
76 | 76 |
|
77 | 77 | ## Display name and description
|
78 | 78 |
|
79 |
| -You use **displayName** and **description** to identify the policy definition and provide context |
80 |
| -for when it's used. **displayName** has a maximum length of _128_ characters and **description** |
| 79 | +You use `displayName` and `description` to identify the policy definition and provide context |
| 80 | +for when it's used. `displayName` has a maximum length of _128_ characters and `description` |
81 | 81 | a maximum length of _512_ characters.
|
82 | 82 |
|
83 | 83 | > [!NOTE]
|
84 |
| -> During the creation or updating of a policy definition, **id**, **type**, and **name** are defined |
| 84 | +> During the creation or updating of a policy definition, `id`, `type`, and `name` are defined |
85 | 85 | > by properties external to the JSON and aren't necessary in the JSON file. Fetching the policy
|
86 |
| -> definition via SDK returns the **id**, **type**, and **name** properties as part of the JSON, but |
| 86 | +> definition via SDK returns the `id`, `type`, and `name` properties as part of the JSON, but |
87 | 87 | > each are read-only information related to the policy definition.
|
88 | 88 |
|
89 |
| -## Type |
| 89 | +## Policy type |
90 | 90 |
|
91 |
| -While the **type** property can't be set, there are three values that are returned by SDK and |
| 91 | +While the `policyType` property can't be set, there are three values that are returned by SDK and |
92 | 92 | visible in the portal:
|
93 | 93 |
|
94 | 94 | - `Builtin`: These policy definitions are provided and maintained by Microsoft.
|
@@ -143,7 +143,7 @@ The following Resource Provider modes are fully supported:
|
143 | 143 | [Integrate Azure Key Vault with Azure Policy](../../../key-vault/general/azure-policy.md).
|
144 | 144 | - `Microsoft.Network.Data` for managing [Azure Virtual Network Manager](../../../virtual-network-manager/overview.md) custom membership policies using Azure Policy.
|
145 | 145 |
|
146 |
| -The following Resource Provider modes are currently supported as a **[preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/)**: |
| 146 | +The following Resource Provider modes are currently supported as a [preview](https://azure.microsoft.com/support/legal/preview-supplemental-terms/): |
147 | 147 |
|
148 | 148 | - `Microsoft.ManagedHSM.Data` for managing [Managed HSM](../../../key-vault/managed-hsm/azure-policy.md) keys using Azure Policy.
|
149 | 149 | - `Microsoft.DataFactory.Data` for using Azure Policy to deny [Azure Data Factory](../../../data-factory/introduction.md) outbound traffic domain names not specified in an allow list. This RP mode is enforcement only and does not report compliance in public preview.
|
|
0 commit comments