Quick answer
Microsoft’s public preview connects an Entra agent identity to a Dataverse agent user. The Entra identity makes the agent a distinct, governable nonhuman actor. The Dataverse agent user becomes its security principal inside a target environment, where an administrator assigns purpose-built security roles.
This is prerelease functionality. Microsoft says preview features are not meant for production and can have restricted functionality. Validate current availability, licensing, regional support, documentation, and supplemental terms before evaluation.
Identity-enabled flow
| Step | Evidence required |
|---|---|
| Define scenario | Business purpose, environment, tables, rows, columns, operations, and data owner |
| Create identity | Supported creation path, distinct agent identity, sponsor, security owner, and retirement owner |
| Add to Dataverse | Correct identity-to-environment association and agent-user record |
| Assign role | Dedicated Dataverse role with only required data and operations |
| Test | Expected actions succeed; out-of-scope reads, writes, deletes, exports, and admin actions fail |
| Observe | Agent changes are distinguishable from humans and conventional application users |
| Retire | Disable access, revoke tokens, remove roles, preserve audit evidence, and delete when appropriate |
Do not assign a broad existing role simply because it unblocks the preview. Model the smallest useful unit of work, separate read from write, and gate bulk or high-impact changes independently.
Start with a bounded non-production scenario
Microsoft’s example is a sales development agent with access only to eligible leads and approved outreach operations. Apply the same pattern to any scenario: define allowed records and columns, actions, rate, time window, downstream integrations, and exception owner before assigning a role.
Test denial as carefully as success. Verify that the agent cannot read unrelated tables or sensitive fields, elevate its role, delete or export unexpectedly, operate in another environment, or act after retirement. Confirm every mutation is attributable to the agent and correlated to the originating workflow.
Keep identity layers distinct
The Dataverse agent user is not a human account and does not automatically grant Microsoft 365 collaboration. The optional Entra agent’s user account is a separate construct for systems requiring a user identity. Read the identity comparison before choosing it.
Use the security-role and lifecycle guide for control design and the readiness checker before evaluation.
Frequently asked questions
What is a Dataverse agent user?
It is a security principal inside a Dataverse environment that is associated with an Entra agent identity and can receive dedicated, least-privileged Dataverse security roles.
Is Entra Agent ID for Dataverse generally available?
No. Microsoft’s August 6 announcement and Power Platform documentation label the Dataverse agent-user integration a public preview not meant for production use.
Where should teams evaluate the preview?
Microsoft recommends a non-production environment and one well-bounded scenario with predefined data, operations, owners, denied-operation tests, audit checks, and retirement plan.
Official sources
Source check: August 12, 2026. Recheck preview status, supported creation paths, availability, licensing, regions, security roles, audit, and terms.