Our agents need Dataverse access — do we give them a service account or an Entra agent user?

You’re right to push back on “just give it System Administrator”. An agent with full rights in Dataverse is a very fast way to make a very large mistake, and nobody will be able to tell afterwards whether the agent or a person did it.

Here’s what’s going on. Roadmap 576843 (Create Dataverse agent users with Microsoft Entra agent identity) shows as Launched on the MRC, with preview from June 2026 and GA listed as August 2026 (Worldwide; Web). The idea is that agents get enterprise-managed Microsoft Entra agent identities, are added to Dataverse as agent users, and are given dedicated, least-privileged security roles for what they need to do, with agent-driven actions audited alongside human ones.

Learn is more cautious than the roadmap. The Create users and Create Entra agent users pages still label agent users as preview, “not meant for production use”. Copilot Studio agents can automatically receive an Entra agent identity; if one needs Dataverse data, an admin adds it as an agent user in the Power Platform admin center (Environments > your environment > Settings > Users + permissions > Agents > Add agent) and picks a security role. Learn also says creating Entra agent application users from agent identities isn’t supported yet, so not every pattern has moved over.

Compare that with what makers usually ask for. Learn notes that adding an app user through the admin API always adds it as System Administrator. That’s fine for a tightly owned integration, but it’s the opposite of least privilege for an agent that talks to staff.

On the Entra side, agent identities are a distinct identity type with owners and sponsors, and Learn lists Conditional Access (Entra ID P1) and ID Protection risk reports (P2 during preview) among the controls. That’s the governance you don’t get from a shared service account.

This is the Third Law with a service account: the easier you make it for an agent to reach your data, the easier it is for a bad prompt, a bug or an attacker to reach it too. And if the only record of what the agent did sits under a shared admin account, you don’t really have a record.

Options that actually work:

1. Make agent users the default for new Copilot Studio agents that touch Dataverse, in a non-production environment first given Learn’s preview label, with a custom security role scoped to the tables the agent needs. Best Steady path.
2. Write the role before the agent. Ask makers for a one-line “reads X, updates Y” statement and build the security role from that; no statement, no Dataverse access.
3. Leave existing app users in place but review them. Find agents running on System Administrator app users, and plan to move them once the agent-user path is GA in Learn for your scenario.
4. Keep issuing System Administrator app users because it’s quicker. It works until an agent bulk-updates the wrong records and the audit trail points at a shared account.

12 Panes action / comms: Tell Power Platform admins: 576843 / Learn: Dataverse agent users tie an Entra agent identity to a scoped security role; Learn still says preview, so pilot outside production. Tell IAM: Agent identities need owners and sponsors; include them in Conditional Access and access reviews. Tell makers: Bring a “reads/updates” statement; we’ll build the role. Leadership: Agents get their own identities and only the access they need.

Benefits / risks: Per-agent identity and audit trail; least-privilege roles; fits Entra Conditional Access and lifecycle tooling; roadmap says Launched while Learn says preview; application-user creation from agent identities isn’t available yet; custom roles take time to design, which makers will feel as friction.

I’d suggest this month: pick one Copilot Studio agent that already needs Dataverse, give it an agent user with a custom read-only role in a test environment, and check that its actions show up under its own identity in the audit log. Then make that the pattern before the next “please can I have System Administrator” ticket arrives.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer