Dynamics 365 Data in Copilot: Your Work IQ Plan Before December 1

TL;DR: Microsoft 365 Copilot can now reason over your Dynamics 365 Sales, Dynamics 365 Customer Service and Power Apps data, in public preview, through Business Applications in Work IQ. Nothing flows until admins switch it on in two admin centers. Use the preview window to fix security roles, scope a pilot group and set a credits policy before usage-based billing becomes the default for new Copilot Business licenses on December 1, 2026.

For two years the most common Copilot complaint we hear from sales and service leaders is simple: “It knows my email, but it does not know my customers.” That gap is closing. Microsoft has extended Work IQ, the intelligence layer behind Copilot, from productivity data into business applications. A seller can now ask Copilot Chat for everything about an account and get the emails, the proposal deck and the open opportunities from Dataverse in one answer.

The timing matters. The feature is in preview today, Microsoft says the separate Dataverse intelligence service will no longer be available soon, and from December 1, 2026 new Microsoft 365 Copilot Business licenses bought through CSP switch on usage-based billing by default. That gives IT leaders about five weeks to decide who gets access, which data is in scope and how spend will be governed. This guide explains what changed, what it means for CIOs, CHROs and IT leaders, and a seven-step plan to pilot it with control.

What is changing with Dynamics 365 and Power Platform data in Copilot?

Business Applications in Work IQ lets Copilot, Copilot Cowork and your agents discover, read and act on Dataverse data alongside Microsoft Graph content, while each application keeps its own data model, permissions and governance. Here is the short version, based on Microsoft’s official Business Applications in Work IQ documentation.

Two capabilities sit underneath the experience. Business skills let you define reusable business context, such as how your organization qualifies a lead or escalates a case, once for every agent. The Dataverse semantic model gives Copilot a shared, business-aware understanding of your tables and relationships, so “my top accounts” means the same thing in every answer.

Why does Copilot grounding in Dynamics 365 matter for IT leaders?

It matters because it moves Copilot from summarizing documents to answering questions about customers, cases and revenue, which is where the measurable value has always been. It also means your Dataverse security model now shapes what Copilot says, not just what a form displays.

For CIOs, the question is readiness: are security roles, business units and field security tight enough that a natural-language question cannot surface records people technically have access to but never looked at? For CHROs, it is trust and workload: if HR case management or employee services run on Dataverse, those tables need a deliberate in or out decision. For IT leaders, it is cost and capacity: Dataverse search indexing increases capacity use, and agentic actions in Cowork bring consumption costs that need a policy.

Nonprofit: many nonprofits run donor and program data on Dataverse through Dynamics 365 or Power Apps. Keep donor and beneficiary tables out of the first pilot, and start with a program or volunteer app where the data is low risk and the time savings are easy to see.

Education: student information, advising and admissions apps built on Power Apps often have broad maker-era security roles. Audit those roles before any staff group gets Copilot access to the environment, and keep student records out of scope until the audit is done.

Government: check feature availability for your cloud before planning. In GCC and GCC High, some Copilot capabilities in Dynamics 365 need admins to install apps or enable Bing search and data movement explicitly, so confirm each setting against your data residency rules.

How should IT leaders prepare for Dynamics 365 data in Copilot?

Work through seven steps over the next five weeks: pick the right environment, fix permissions, turn on settings for a small group, measure, then decide. Steps 1 to 4 usually fit before December 1.

1. Pick one environment and one question. Choose a production Dynamics 365 Sales or Customer Service environment with good data quality, and one question users ask every day, such as “What is happening with this account?” Our guide to everyday Copilot workflows for HR, finance and sales has more starting points.
2. Review security roles before anything else. Copilot respects existing permissions, so broad roles become broad answers. Remove organization-level read on sensitive tables, check business unit assignments and confirm field security on salary, health and donor fields.
3. Decide which tables are in scope. Include only the tables your pilot question needs in Dataverse search and in each model-driven app’s settings. Fewer tables means better answers and lower capacity use.
4. Turn it on for a security group, not the tenant. In the Microsoft 365 admin center, set Business Applications data in Work IQ to specific groups, then enable the environment settings in the checklist below.
5. Set a credits and capacity policy. Review your Copilot cost management policy and Dataverse capacity before Cowork actions and agents start consuming. Our Microsoft 365 Copilot licensing changes guide explains the December 1 billing changes.
6. Register agents that use business data. Any Copilot Studio or Agent Builder agent that reads or writes Dataverse records needs an owner, a purpose and a review date. Our explainer on Agent Builder vs. Copilot Studio helps you choose where each one belongs, and an Agent PMO keeps them accountable.
7. Test for prompt injection and oversharing. Case notes and email-to-case content are untrusted input. Test how agents handle instructions hidden in records, using our guide to defending Copilot and Copilot Studio agents from prompt injection.

Save this checklist. Every setting must be on before Copilot can use Dataverse data, which also makes it a reliable way to switch the pilot off.

If you already restricted Fabric IQ from Copilot for Power BI, use the same decision record here: who approved the data source, for which group and when it will be reviewed.

How do you tie Dynamics 365 grounding to measurable value?

Measure time returned on one recurring business question before and after the pilot, then compare that value with the licenses, credits and Dataverse capacity it consumes. A single well-chosen workflow tells you more than a usage dashboard.

Here is a simple worked example with illustrative numbers. Replace them with your own.

• 25 account managers each spend 5 hours a week preparing for customer meetings by searching Dynamics 365, email and files.
• With Copilot answering “Brief me on this account” from all three sources, prep drops to 2 hours. That is 3 hours saved per person, or 75 hours a week.
• At a loaded cost of $85 an hour, 75 hours is worth about $6,400 a week, or roughly $330,000 a year.
• Compare that with the Copilot licenses those 25 people already hold, any credits Cowork actions use and the added Dataverse capacity. If the value is several times the cost, extend to service agents next. If not, fix the data or the question before you add users.

Track two quality measures alongside time: the share of answers users rate as correct, and the number of answers that surfaced a record the user should not have seen. The first should rise each week. The second should be zero. For a fuller scorecard, see our guide to Copilot adoption metrics that prove value.

What do IT leaders ask about Dynamics 365 data in Copilot?

These four questions come up in almost every briefing on this change.

Is Dynamics 365 and Power Platform grounding in Copilot generally available?

No. Business Applications in Work IQ is in public preview. Preview features are provided as is, are subject to supplemental terms and can change, so use a scoped pilot on real but non-critical work rather than a full rollout.

Can Copilot show users Dynamics 365 records they should not see?

Copilot works within each user’s existing Dataverse permissions, so it does not grant new access. It does make existing access far easier to use, which means broad security roles and stale business unit assignments become visible quickly. Review roles before you widen the pilot.

What licenses do users need?

Microsoft documents that the full Work IQ experience needs a Microsoft 365 Copilot license. Inside Dynamics 365 apps, users also need a Dynamics 365 Enterprise or Premium license, and inside Power Apps they need a Power Apps premium license. Check the Work IQ licensing requirements for consumption costs before you scale.

We piloted Dataverse intelligence. What happens to that work?

Microsoft has folded Dataverse intelligence into Business Applications in Work IQ and says the separate service will no longer be available soon. Your environment settings and business context carry the same intent, so plan to move pilots to Work IQ now rather than after the service ends.

How can 2toLead help you bring business data into Copilot safely?

2toLead helps organizations across nonprofit, education, government, healthcare, financial services and professional services turn Microsoft 365 and Power Platform changes into governed, measurable outcomes. In a fixed-scope, three-week Work IQ Business Data Readiness Sprint, our Microsoft MVP team will:

• Review Dataverse security roles, business units and field security for the pilot environment
• Agree in-scope tables and configure the tenant, environment and app settings for a pilot group
• Set a Copilot credits and Dataverse capacity policy with your finance and IT owners
• Register pilot agents with owners and review dates, as part of tackling agent sprawl
• Measure one business question before and after, and hand you a simple value scorecard

Find more practical guidance on the 2toLead Insights hub, or book a Work IQ Business Data Readiness Sprint.

No hype. Just practical, governed AI that actually gets adopted.