Identity Providers (IDP)
Bind every discovered agent to a real user or service identity so ownership, access policy, and audit trails are identity-aware.
What is an identity provider integration
An agent by itself is just a process. An identity provider (IDP) integration is what connects that process back to the person or service account responsible for it. Without identity binding, "who owns this agent" is a manual lookup; with it, ownership, risk scoring, and access policy all resolve automatically to a real identity.
Why identity binding matters
- Access policies can be written against real users and groups, not just raw agent IDs.
- When a user account is disabled or offboarded, every agent they own can be flagged or reassigned automatically.
- Audit trails and compliance reports show a named owner instead of an anonymous service principal.
Vendor integrations
| Platform | Purpose | Credential required |
|---|---|---|
| Microsoft Entra ID | Binds discovered agents to Entra ID (Azure AD) users and service principals, and enables identity-based access policy across Agent Identity Security. | Microsoft Entra ID (Azure AD) app registration credentials. |
