Dynamics 365 ERP lands in Copilot Cowork: NZ checks before switch-on

By DataForge team22 November 20265 min read

Microsoft's Dynamics 365 ERP plugin for Copilot Cowork is now GA, so AI can change ERP records. Here's what NZ firms should check before switching it on.

What Microsoft released

At Ignite on 17 November, Microsoft announced that the Dynamics 365 ERP apps plugin is generally available as part of a wider push it calls Dynamics 365 in Copilot. Jeff Teper, Microsoft's executive vice president for apps and agents, wrote that the plugin carries more than 39 finance and operations skills and adds expanded connectivity to Excel. Microsoft's Ignite Book of News says the plugin brings ERP context and actions into Copilot Cowork and Excel. MSDynamicsWorld reports the same skill counts, alongside 57 CRM skills in the Sales and Customer Service plugins.

The plugin had been rolling out through Microsoft's plugin registry since late October. Ignite moved the plugin to general availability, and that's the signal many IT teams wait for before letting a feature near production finance data.

What the plugin can do inside your ERP

Microsoft's own documentation shows the plugin goes well past reporting. Copilot Cowork connects to a Dynamics 365 Finance or Supply Chain environment through Microsoft's ERP Model Context Protocol (MCP) server. According to Microsoft Learn, the server offers data tools that can read, create, update and delete records in data entities. It also offers form tools that navigate pages and set field values as a user would, plus action tools that call business logic developers have exposed.

Microsoft's worked example is a sourcing manager asking Cowork to evaluate bids on a request for quote. Cowork reads vendor emails and PDF attachments in Outlook, updates the RFQ replies in the ERP, scores the bids, and then creates the purchase order and drafts the award email once the manager approves. Cowork asks for approval before acting. Staff can also click "Always allow", which skips later prompts for similar actions for the rest of that conversation.

Permissions follow the user. The Learn page says the MCP server filters entities, forms, fields and actions according to each person's security roles, so nobody can reach anything through Cowork that they can't already reach in the application.

Who can use it

The licensing and environment rules will shut out a fair share of NZ Microsoft ERP customers. The enablement guide requires each user to hold a Microsoft 365 Copilot licence and a qualifying finance and operations licence, such as Finance, Supply Chain Management, Commerce, Project Operations or a Team Member variant. Licences for Dynamics 365 products outside finance and operations don't qualify. Business Central customers, who make up much of the Microsoft ERP base among NZ mid-sized firms, therefore aren't covered by this plugin.

The environment also needs to run version 10.0.47, 10.0.46 PQU-2 or 10.0.45 PQU-7 or later, at Tier 2 or above. On-premises and cloud-hosted development environments aren't supported. Microsoft adds that the older MCP server with 13 fixed tools retired on 1 October 2026, so any internal pilot built on that server needs rework.

Cost is harder to pin down. Usage-based billing and Copilot Credits must be configured for each user, and Learn says calls to the ERP MCP server can consume credits, with exemptions for some premium licences. Teper's announcement didn't include plugin pricing, so the credit burn of a multi-step task such as bid evaluation is unknown until a firm measures its own usage.

Why it matters for NZ firms

The approval prompt is the main control between a natural-language request and a posted transaction. Most NZ finance teams already design segregation of duties around who can raise, approve and pay a purchase order. Once Cowork can create the order from an email thread, the person approving the prompt becomes the effective preparer. Auditors will want to know how that person checked the AI's extraction from a vendor PDF. The "Always allow" option weakens that control further, because a long conversation can then post several records with a single human check.

Data handling deserves a look too. The enablement guide notes that Cowork uses Anthropic models as a subprocessor for some capabilities, and that this setting is off by default only in the EU, EFTA and UK. NZ tenants will have it switched on unless an administrator has changed it. IDM's March analysis reported that Anthropic-routed requests sit outside Microsoft's in-country processing commitments for Australia, and that NZ has no equivalent commitment either. Firms with contractual or sector obligations about where financial data is processed should confirm their position with Microsoft before connecting the ERP.

Two smaller details will catch local users out. Learn states that MCP guidance is in US English and that dates and numbers use ISO formats regardless of locale, so a prompt mentioning "3/12" is ambiguous to the tool. The plugin is also limited to regions where Copilot Cowork is deployed, and Microsoft points customers to its product availability list instead of naming countries.

Practical next steps

  • Check eligibility before anyone builds a business case. List which users hold both Microsoft 365 Copilot and a qualifying finance and operations licence, and confirm your production environment's version and tier.
  • Start in a Tier 2 sandbox with a narrow read-only use case, such as open purchase order queries or customer credit checks, and watch Copilot Credit consumption for a few weeks.
  • Review security roles before enabling write access. Any user whose role is broader than their actual job will see that excess exposed through a much faster interface.
  • Decide whether "Always allow" is acceptable for your finance processes, and write the answer into your delegated authority and AP procedures.
  • Ask your Microsoft partner or account team in writing where Anthropic-processed Cowork requests are handled for NZ tenants, and record the answer against your privacy and data governance obligations.
  • Teach pilot users to write dates as 2026-12-03 and to name the legal entity in every prompt when the environment holds more than one company.
  • If you're on Business Central, treat this release as a sign of where Microsoft is heading and watch for an equivalent, without planning around one that hasn't been announced.

We expect most NZ organisations on Dynamics 365 Finance and Supply Chain to run a pilot within the next year, because the bid evaluation example maps closely to procurement work that currently takes hours of copying between Outlook and the ERP. Firms that sort out roles, approvals and data handling first will find the pilot easier to approve. If you're working out how an AI layer fits your ERP environment, or need a governance model for agents that can post transactions, our AI consultancy team can help you scope the controls.

Want to know what this means for your organisation? Our team in Auckland can show you your top three opportunities in a free 30 minute assessment.

Get my free assessment How we help
Get new articles by RSS