In development MRC 577185

Microsoft Dataverse: Enable semantic data understanding for agentic use

Give AI agents and Copilot a true understanding of your business data — not just raw schema — so they can answer questions accurately with less manual configuration. Learns from the systems you already run — Automatically extracts semantic knowledge from views, forms, and metadat

Microsoft Copilot (Microsoft 365)Microsoft Dataverse 03 Horizon05 GRC04 Security09 Work & Skills

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure November CY2026
Preview June CY2026
Platforms Web

What it is

Microsoft Dataverse: Enable semantic data understanding for agentic use is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

What it does

Give AI agents and Copilot a true understanding of your business data — not just raw schema — so they can answer questions accurately with less manual configuration. Learns from the systems you already run — Automatically extracts semantic knowledge from views, forms, and metadata already defined in your Dataverse environment, reducing agent deployment from days of manual setup to near-zero effort. Full visibility for makers — View generated semantic knowledge per entity — including name, description, and sample questions — directly in the Power Apps maker portal. Search for understanding gaps and enrich missing context with a built-in glossary for domain-specific terms. Governance and privacy built in — Enable or disable semantic signals at the org level, or at the individual signal-type or table level, giving makers and admins granular control to meet compliance and privacy requirements without sacrificing agent quality. No manual schema mapping. No custom query logic. No disambiguation between what your data is called and what your business actually means.

Why you should care

Board

Agents change operating risk. Ask for registry coverage and owner accountability first.

CISO

Treat agents as privileged actors: least privilege, owner, lifecycle, and audit before scale.

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 · 05 GRC · 04 Security · 09 Work & Skills

Communication needed

  • Security: Assess exposure, Conditional Access, and agent/tool permissions.
  • 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: 577185
  • Status: In development
  • Products: Microsoft Copilot (Microsoft 365), Microsoft Dataverse
  • GA / disclosure: November CY2026
  • Preview: June CY2026
  • Platforms: Web
  • Cloud instances: Worldwide (Standard Multi-Tenant)
  • 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