Integration: Microsoft Entra ID

Argent with Microsoft Entra ID

Microsoft Entra Agent ID gives AI agents their own identities in your Microsoft directory. Argent Strategic Intelligence reads those agents, finds the person who sponsors each one and makes that person its owner.

01 / INTEGRATION: MICROSOFT ENTRA ID

What Argent does with Microsoft Entra ID

If you already register agents in Microsoft Entra, Argent governs them from that list instead of building a second inventory.

  • Agent identities. Argent reads the agent identities in your directory from Microsoft Graph (Microsoft Entra Agent ID).
  • A human owner. When you turn on sponsor mapping, Argent reads each agent's human sponsors (agentIdentity in Microsoft Graph) and makes the sponsor its owner in Argent. An agent with no active owner is refused. See Identity Tethering.
  • No key until an admin issues one. A mirrored agent arrives without an Argent key; an admin issues its first key. See Keyless Agents.
  • Disabled in Entra, held in Argent. Argent re-reads disabled agents between full syncs. If Argent cannot read Entra for longer than its staleness window, it holds the keys of every agent it mirrored from that directory rather than risk missing a disable. That hold is on unless you turn it off.
  • Sign-in too. Entra ID can sign people in to the Argent console over OpenID Connect or SAML 2.0; both were proven live with Entra.
02 / INTEGRATION: MICROSOFT ENTRA ID

How it connects

A read-only pull from Microsoft Graph with an app-only token. Argent never writes to your directory.

  1. In the Argent console, open Integrations, Identity sources and choose Add connector, type Microsoft Entra.
  2. Give it a display name and enter the settings below.
  3. Connect, then Test: Argent reads a sample from Microsoft Graph to prove the link works end to end.
  4. Open Attribute mapping, review the proposal and save it. Saving the first mapping version turns the connector on.
  5. The mirrored agents appear in Argent, each waiting for an admin to issue its first key.

The sign-in and data addresses are fixed (login.microsoftonline.com for the token, graph.microsoft.com for data). No setting can point your secret or token anywhere else, and every next page of results must stay on the Graph address.

03 / INTEGRATION: MICROSOFT ENTRA ID

What you configure

SettingWhat to enter
Directory (tenant) IDYour Microsoft Entra directory ID.
Application (client) IDAn app registration for Argent with the Microsoft Graph application permission AgentIdentity.Read.All.
Client secretStored in your vault; Argent is given only its path.
Sponsor mappingOptional, off by default. Microsoft documents AgentIdentity.ReadWrite.All as the least-privileged permission for listing sponsors, so grant it only if you turn this on.
  • The secret stays in your vault. Argent's configuration holds only the vault path of the credential, never the credential itself. Argent works with HashiCorp Vault and OpenBao, AWS Secrets Manager, CyberArk Conjur and Infisical.
  • Guarded dial-out. Every identity connector dials out through a guarded client that refuses private, loopback, link-local and cloud-metadata addresses. Turn on the egress allowlist and only the addresses you list are reachable (list login.microsoftonline.com and graph.microsoft.com when the allowlist is on).
04 / INTEGRATION: MICROSOFT ENTRA ID

When an agent or its owner goes away

Argent decides from its own record, which it keeps in step with Entra.

  • Owner leaves. When the sponsor is no longer an active person in Argent, the agent's next request is refused before it reaches a model.
  • Agent disabled in Entra. The agent is held in Argent on its next check.
  • Every change signed. Each decision lands in the signed audit record. See Owner Offboarding and One-Click Audit Evidence.
05 / INTEGRATION: MICROSOFT ENTRA ID

Where it fits in Argent

Identity sources Argent connects to

Microsoft Entra ID and the other identity vendors Argent connects to. Open any logo for its page. SailPoint's mark opens IdentityIQ. Also see SailPoint Identity Security Cloud.

  • Microsoft Entra ID
  • Okta
  • Auth0
  • Keycloak
  • SailPoint
  • Saviynt
  • Ping Identity