Govern Agent Access Azure Postgresql
In brief
The Azure PostgreSQL agent access documentation now links to guidance explaining identifiers for your scenario.
What Entra admins need to know
Administrators can use the new link to better understand the identifiers used in this configuration.
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.
- Change to the Overview (Preview) tab, and record the blueprint app ID and blueprint principal object ID.
- Change to the Linked agent identities (Preview) tab, select the agent identity. Record the object ID.
For identifier meanings, see Record the identifiers for your scenario.
For more information on other options for how agent identities are created in Microsoft Entra, see How are agent identities created?.
Authorize the agent identity using Microsoft Entra entitlement management
@@ -144,6 +144,8 @@ In this section, you'll create the representation of the agent in Microsoft Entr 1. Change to the **Overview (Preview)** tab, and record the blueprint app ID and blueprint principal object ID. 1. Change to the **Linked agent identities (Preview)** tab, select the agent identity. Record the object ID. +For identifier meanings, see [Record the identifiers for your scenario](key-concepts.md#record-the-identifiers-for-your-scenario).+ For more information on other options for how agent identities are created in Microsoft Entra, see [How are agent identities created?](agent-id-creation-channels.md). ## Authorize the agent identity using Microsoft Entra entitlement management 