Microsoft Entra Agent ID
General

Govern Agent Access Azure Postgresql

In brief

The access package section heading now correctly spells “identities.”

What Entra admins need to know

No administrator 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.

  1. In the Microsoft Entra Admin Center, go to Microsoft Entra ID, select Groups, and select New group.
  2. Set Group type to Security.
  3. Enter a Group name such as pg-employees-readers. Keep the name short; you will use it verbatim inside PostgreSQL.
  4. Leave membership type as Assigned, as Entitlement Management will be used to assign membership. Do not add any members yet.
  5. Select Create.
  6. After creation, open the group and note the name and Object ID, which you'll use when creating the principal and role assignment in the PostgreSQL database.

Create a table in the database

Connect to your Azure Database for PostgreQL server using the Entra admin account you just configured.

Once connected, confirm you have an employees table. If you don't have a table with that name in your PostgreSQL database, connect to PostgreSQL and create that table.

Create the database role for the security group to read from that database

You should see pg-employees-readers listed with r (SELECT) privileges on the employees table.

Create an access package to assign agent identitesidentities to the security group

Entitlement Management lets you define an access package that bundles the security group membership and attach a policy describing how identities, including agent identities, can request access.

  • Conditional Access policies assigned to the blueprint principal are satisfied.
  • The Fmi_Path value resolves to a known agent identity within the tenant.
  1. If the checks were successful, Microsoft Entra ID provides a response to the agent with the intermediate token.

    This token consists of a short-lived JWT, the intermediate token, issued for the api://AzureADTokenExchange audience.

  2. The agent obtains from Microsoft Entra ID a PostgreSQL access token.

  3. If the checks are successful, Microsoft Entra ID provides a response with a token for the resource.

    The response includes a short-lived JWT access token issued for the https://ossrdbms-aad.database.windows.net audience.

  4. The agent connects to the database.

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…