Dynamics 365 data in Copilot Cowork workflows
Dynamics 365

Dynamics 365 data in Copilot Cowork workflows

by HubSite 365 about Microsoft Events

Copilot Cowork can combine Dynamics 365 records with Microsoft 365 context to prepare analysis and actions for business users to review.

Key insights

  • Cowork can use Dynamics 365 plugins alongside Microsoft 365 context from Outlook, Teams, Excel, OneDrive, and SharePoint.
  • The ERP demo combines RFQ criteria and vendor records with supplier bids from Outlook to create a scored dashboard.
  • Cowork follows the signed-in user’s Dynamics 365 permissions; the demo’s customer service role is read-only.
  • The demonstrated workflow pauses for approval before changing an RFQ or sending supplier emails.

Copilot Cowork can bring Dynamics 365 business data into multi-step workflows, combining it with Microsoft 365 context to prepare analysis, communications, and proposed actions. This approach matters to sourcing, sales, and customer service teams whose work spans business records and everyday productivity apps. Microsoft Events demonstrates the approach with ERP, customer service, and sales scenarios using Dynamics 365 plugins.

What's new

The change is from asking AI for a fact to giving it an outcome to pursue. In the example, instead of asking which purchase orders are late and then manually exporting data, a user asks Cowork to chase late purchase orders. Cowork can read the records, assemble an impact workbook, draft supplier emails, and prepare a follow-up.

The demonstrations frame Cowork as a coordinator across Microsoft 365 and Dynamics 365. Work IQ provides context from Microsoft 365, including email, Teams, and files, while enabled Dynamics 365 plugins provide business records and actions. Cowork plans the steps, selects tools, shows its work, and pauses for approval before consequential actions.

That distinction matters operationally: the business system remains where its data and processes live, while Cowork can gather context and prepare work across applications. Possible outputs shown include comparisons, plans, emails, proposals, dashboards, and actions in a business application. The aim is to reduce manual copying between systems without removing the user’s decision-making role.

Who it is for and what you need

The approach is relevant to people who work across Dynamics 365 and Microsoft 365, including sourcing staff evaluating supplier bids, customer service representatives investigating orders, and sales teams coordinating with operations. The examples use Dynamics 365 ERP, Customer Service, and Sales plugins, together with Outlook and other Microsoft 365 apps.

For the demonstrated ERP connection, the user turns on the plugin in Cowork, signs in, and selects a Dynamics 365 environment. An administrator can also deploy the plugin for users. Cowork acts with the signed-in person’s Dynamics 365 permissions, rather than granting access beyond their role.

Microsoft offers 30 prebuilt CRM skills for Dynamics 365 Sales, Customer Service, and Customer Insights as generally available in Copilot Cowork. That status describes those CRM skills; it should not be taken as a general availability claim for every plugin or workflow shown in the ERP demonstration.

How it works

The RFQ example shows how Cowork can combine business records with information in email. Maya, a sourcing manager, asks it to evaluate RFQ 000110 using the latest supplier bid emails and the scoring criteria in Dynamics 365, flag discrepancies, recommend the best value, and create an HTML dashboard. Her prompt also says not to change records or send messages.

  1. In Cowork, open Customize, enable the Dynamics 365 ERP apps plugin, and choose the Dynamics 365 environment. The demonstration shows the user signing in with their own identity.
  2. Describe the intended outcome and specify the records or context to use. Cowork reads the RFQ and its weighted criteria, finds the latest supplier bids in Outlook, and checks vendor records.
  3. Review the plan and resulting analysis. In the example, Cowork scores the three bids and creates a dashboard showing scores, trade-offs, and discrepancies.
  4. Choose any follow-up actions. Cowork prepares the RFQ change and supplier emails, but holds both for Maya’s approval before applying or sending them.

The evaluation does not simply name the highest-scoring supplier as the winner. It flags that no bid meets the December 14 need-by date and that a supplier’s stated 45-day delivery conflicts with a seven-week completion timeline. The recommendation is to hold the award and seek renewed delivery confirmation, leaving the decision with Maya.

A second scenario applies the same permissions principle to customer service. Sam asks why a customer’s orders are late and what date can honestly be promised. Cowork follows the case and orders into ERP, identifies a delayed purchase order and available stock, then drafts a request to Priya, who owns the stock. Sam’s read-only ERP role means Cowork does not move the stock for him.

Limitations and alternatives

Cowork’s work is bounded by the signed-in user’s Dynamics 365 permissions. A read-only role can support investigation, but it does not authorize a record change. The customer service scenario routes a stock decision to the person who has responsibility for it.

Review remains part of the workflow, not an optional polish step. In the RFQ example, the dashboard surfaces delivery and payment discrepancies that affect the recommendation; the user chooses whether to reopen the RFQ and contact suppliers. Approval gates also apply to the prepared record change and outbound emails.

Organizations considering these workflows should check that users have the appropriate Dynamics 365 access and that the relevant plugin and environment are configured. They should also decide which actions require human review and make prompts clear about whether Cowork should only analyze information or prepare changes. The scenarios show that asking for an outcome does not mean delegating the final business decision.

Sources

Frequently asked questions

How does Copilot Cowork use Dynamics 365 data?

Cowork can use enabled Dynamics 365 plugins to read business records and, where the user has permission, prepare actions. It can combine that data with Microsoft 365 context such as Outlook email.

Does Cowork make Dynamics 365 changes without approval?

In the demonstrated workflow, Cowork prepares consequential actions and waits for user approval before changing the RFQ or sending supplier emails.

Does Copilot Cowork use the user's Dynamics 365 permissions?

Yes. The demonstrated setup uses the signed-in user's access, and Cowork sees only what that person's Dynamics 365 role allows.

Are Dynamics 365 CRM skills generally available in Copilot Cowork?

The 30 prebuilt skills for Dynamics 365 Sales, Customer Service, and Customer Insights are generally available in Copilot Cowork. That status does not establish the availability of every plugin or workflow shown.