In development MRC 571677

Dynamics 365 Finance and Operations cross-app: Role-based access controls for ERP agents

Dynamics 365 ERP security administrators can apply additional, agent-specific security restrictions that take effect when a user accesses the ERP through an agent. Administrators define these restrictions using the existing security model — assigning roles, duties, and privileges

Dynamics 365 Finance and Operations cross-app 03 Horizon04 Security08 Adoption05 GRC09 Work & Skills

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure December CY2026
Preview October CY2026
Platforms Web

What it is

Dynamics 365 Finance and Operations cross-app: Role-based access controls for ERP agents is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

What it does

Dynamics 365 ERP security administrators can apply additional, agent-specific security restrictions that take effect when a user accesses the ERP through an agent. Administrators define these restrictions using the existing security model — assigning roles, duties, and privileges that apply only to agent-initiated requests, scoped by legal entity — so that a user's agent session can operate with narrower permissions than the same user holds when working directly in the ERP.

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 · 08 Adoption · 05 GRC · 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.
  • Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.

Source

  • MRC id: 571677
  • Status: In development
  • Products: Dynamics 365 Finance and Operations cross-app
  • GA / disclosure: December CY2026
  • Preview: October CY2026
  • Platforms: Web
  • Cloud instances: Worldwide (Standard Multi-Tenant), GCC, GCC High
  • moreInfoUrls: —
  • Open on Microsoft 365 Roadmap

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