Launched MRC 576843

Microsoft Dataverse: Activate Enterprise Data in Copilot - Create Dataverse agent users with Microsoft Entra agent identity

Organizations can securely deploy AI agents to access and interact with Dataverse data by using enterprise‑managed Microsoft Entra agent identities. This feature enables agents to be provisioned as Dataverse agent users with dedicated, least‑privileged security roles based on the

Microsoft Copilot (Microsoft 365)Microsoft Dataverse 03 Horizon04 Security05 GRC08 Adoption09 Work & Skills

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure August CY2026
Preview June CY2026
Platforms Web

What it is

Microsoft Dataverse: Activate Enterprise Data in Copilot - Create Dataverse agent users with Microsoft Entra agent identity is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: Launched.

What it does

Organizations can securely deploy AI agents to access and interact with Dataverse data by using enterprise‑managed Microsoft Entra agent identities. This feature enables agents to be provisioned as Dataverse agent users with dedicated, least‑privileged security roles based on their intended capabilities. This feature ensures agents have only the access required to perform tasks autonomously or on behalf of users. By using identity‑based role assignment and full auditing of agent‑driven actions, organizations can enforce security and compliance policies across both human users and AI agents while maintaining traceability of data access and changes within Dataverse environments. Business Value: This feature enables secure, compliant management of AI agents in Microsoft Dataverse, which reduces risk and improves governance for autonomous and interactive agents. Enabled for: Enabled for admins/makers/marketers automatically

Why you should care

Board

Security/compliance control — fund Steady before more seats.

CISO

Prioritise as Steady control; wire into IR and GRC evidence paths.

CFO

Map licence or consumption impact to the frozen value case; avoid seat spray.

Adoption

Pilot with a named cohort and measure changed work, not vanity clicks.

Suggested action

Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Put this on the agent register with a named owner. Do not enable broadly until permissions, DLP, and reclaim rules exist.

12 Panes: 03 Horizon · 04 Security · 05 GRC · 08 Adoption · 09 Work & Skills

Communication needed

  • Security: Lead review; confirm control mapping before enablement.
  • GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
  • FinOps: Forecast seat or credit impact; align to frozen value case.
  • Adoption: Plan cohort messaging, clinics, and success measures.
  • Comms: One story for board and staff — what changes, what does not, who owns risk.

Benefits

  • May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
  • Roadmap visibility helps Horizon planning without guessing dates.
  • Agents can automate multi-step work inside existing Microsoft 365 permissions.

Risks

  • Status and dates change; treat MRC as directional, not a contract.
  • Enabling without Steady controls can amplify overshare or cost leakage.
  • Agents act; over-privilege and ownerless agents create lasting exposure.

Source

Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.

Back to roadmap intel