Microsoft says Dataverse data in Microsoft 365 Copilot has launched. Our Dynamics 365 and Power Apps environments hold customer, case and HR-adjacent records. Will people suddenly be able to ask Copilot Chat about any account or case, and what do we need to check before we let it loose?

Dataverse data in Microsoft 365 Copilot: tenant setting, environment switches and security roles — the Steady way to open business data to Copilot.

Will Microsoft 365 Copilot now show everyone our Dataverse and CRM data?

You’re right to stop and ask before anyone types “summarise every open complaint for this customer” into Copilot Chat. Business data is a different animal from documents, and the question is a good one.

Here’s what’s going on. Roadmap 560539, Dataverse data connected to Microsoft 365 Copilot, is now marked Launched (preview from June, general availability in the September 2026 window; verify for your cloud). It lets people search and ask questions over Dataverse tables, the data behind Dynamics 365 and model-driven Power Apps, from Copilot Chat, the Power Apps side panel, Outlook, Word and Teams. Learn’s Dataverse data in Microsoft Copilot page is clear on the important bit: Copilot searches the Dataverse tables the user already has access to, follows table relationships to pull in related records, and answers from that. It does not invent a new permission. If someone can see a record in the app, they can now get at it in plain English. If they can’t, Copilot shouldn’t either.

That’s reassuring and worrying at the same time. Reassuring because the model respects your security roles and business units. Worrying because most Dataverse estates have a few roles with Organization-level read that were granted “for now” years ago, and natural-language search makes that over-reach far easier to stumble into.

It also isn’t one switch. Learn’s prerequisite list for Dataverse intelligence has several layers: the tenant setting Dataverse data available in Microsoft 365 Copilot in the Microsoft 365 admin center (Copilot, then Settings; All users or specific Entra security groups; AI administrator or Global administrator), then per environment in the Power Platform admin center: Copilot enabled, Dataverse search on, Allow data availability in M365 Copilot, Search for records in Microsoft 365 apps, and the model-driven app’s own Copilot setting. Message Center MC1278715 notes that tenants in the European Economic Area have to opt in through that admin setting. On data handling, the Power Platform compliance page says only minimal, derived search queries go to Dataverse with user and tenant identifiers removed, and admins can switch Dataverse search off.

This is a Steady-before-scale moment for the Security and GRC panes. Schofield’s Third Law (historically attributed) applies neatly: the easier it is for you to get at the data, the easier it is for everyone else who shouldn’t.

Options that actually work:

Group-scoped pilot, one environment. Set the tenant setting to a specific security group, enable only one production environment whose security roles you’ve reviewed, and leave the rest off. Best Steady default.
Role review first, then broaden. List every role with Organization-level read on sensitive tables (cases, contacts, anything HR or health-adjacent), tighten to Business Unit or User where you can, and use column-level security for the fields that matter. Then widen the group.
Leave the tenant setting at All users and assume app permissions are fine. It works until a sales rep asks Copilot about a colleague’s disciplinary case that sat in a mis-scoped table.
Turn Dataverse search off everywhere and wait. Safe, but it also degrades in-app search and Copilot Studio agents that rely on that index, so it’s a blunt instrument.

12 Panes action / comms: Tell Power Platform admins: No environment goes into Copilot until its security roles have had a look. Tell data owners: If it’s readable in the app, it’s askable in Copilot. Tell pilot users: Check answers against the record; Copilot summarises, it doesn’t own the truth. Leadership: This is high value for account and case work, and it’s gated by permissions we already own.

Benefits / risks: People get account context in Outlook, Teams and Word without switching apps; existing role design gets stress-tested in public; preview-era setting quirks in Outlook and Word (Learn notes Default mode and Chat only settings during preview); extra storage from Dataverse search indexing. Verify Learn and Message Centre for your region.

I’d suggest starting this week with the role review on your most sensitive environment, then switching the tenant setting to a small pilot group rather than everyone. Once you’ve done that, opening it wider becomes a calm decision rather than a leap of faith.

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