Resource Policy Concepts
In brief
The custom policy description now links “Rego” to Open Policy Agent’s policy-language documentation.
What Entra admins need to know
Administrators can access Rego guidance while authoring or managing custom policies; no action is required.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
A policy definition describes a configuration requirement and the requests to which it applies.
- A built-in policy provides Microsoft-managed, read-only logic that you can assign without authoring Rego. Use the
builtInDefinitionscollection to discover available definitions and versions. - A custom policy contains
RegoRego that you author and manage.
A custom definition has a uniqueName that identifies it across versions. Its Rego package uses graph.<uniqueName>["X.Y.Z"] to identify the name and version. Metadata describes the policy, and __metadata__.selector identifies its target resource type or action and operations.
@@ -16,7 +16,7 @@ Microsoft Entra resource policy separates the logic that identifies noncompliant A policy definition describes a configuration requirement and the requests to which it applies. - A **built-in policy** provides Microsoft-managed, read-only logic that you can assign without authoring Rego. Use the `builtInDefinitions` collection to discover available definitions and versions.-- A **custom policy** contains Rego that you author and manage.+- A **custom policy** contains [Rego](https://www.openpolicyagent.org/docs/policy-language) that you author and manage. A custom definition has a `uniqueName` that identifies it across versions. Its Rego package uses `graph.<uniqueName>["X.Y.Z"]` to identify the name and version. Metadata describes the policy, and `__metadata__.selector` identifies its target resource type or action and operations. 