Microsoft announced an expansion of the connections between Dynamics 365, Copilot and Copilot Studio on 17 November 2026. The update includes plugins for sales, customer service and ERP operations, integration of business data with Work IQ, and general availability of application creation on Copilot Managed Runtime. For businesses, the relevant change is access to context and certain commercial operations from the Copilot working environment, while retaining the organisation's permissions and administration as part of the process.

Available plugins for sales, service and ERP

The updated Sales plugin is announced as generally available. Microsoft describes it for account planning, meeting preparation, opportunity follow-up and pipeline prioritisation. Deal information can track progress against a quarterly forecast, decision makers and gaps in customer engagement. The functions are connected to the sales data and processes accessible in the system, rather than to a generic description of a prospect or customer.

The Customer Service plugin is also generally available. Microsoft describes more than 57 business skills across the two customer-experience plugins. That count refers to functions in the announced products, not a measurement of a company's performance. For users, the practical distinction is between selling, managing customer requests and having permission to access the information needed for those activities in their own organisation.

The Dynamics 365 ERP apps plugin is updated with more than 39 finance and operations skills and expanded connectivity to Excel. Published examples include purchase requisitions, requests for quotations and purchase-order management. ERP refers to systems managing processes such as finance and procurement. These functions concern different business records and responsibilities from drafting a message or creating a sales presentation for a customer.

For sales, the announcement also includes creating PowerPoint presentations, adapting existing material for other customers and refreshing slide data. It mentions approval and sharing requirements. These operations connect business records with documents used in meetings, while keeping the review of who can receive the material within the same process.

Component roles in a connected business process

  1. Copilot

    The interface where a user makes a request

  2. Work IQ

    Business context and accessible information

  3. Plugins and agents

    Operations available for the particular task

  4. Dynamics 365

    Business records and processes

A team discussing data displayed on a laptop
Yan Krukau

Work IQ connects business data with organisational context

Microsoft presents Work IQ as part of the broader Microsoft IQ context layer. Dynamics 365 data is natively integrated with Work IQ, combining productivity information and business-process data. The announcement gives examples of updating customer records and preparing journal entries through natural language. Microsoft states that this access respects the organisation's existing permissions and governance, rather than replacing those controls with the conversation itself.

Business context extends beyond the text inside a document. It includes relationships between a customer, opportunity, order, activity and responsible employee where those are recorded in the system. An implementation needs to understand these relationships before connecting another workflow. If two applications use different identifiers for the same customer, displaying a shared conversation does not itself define how their underlying records correspond to one another.

This distinction explains the role of integration design. The conversational interface is where a request starts; the business system remains where an operation must be authorised and recorded. In a business automation project, the path between the request, consulted data and executed action is defined for the specific process. User identity and access rules are part of that path, alongside the information supplied to the model.

Copilot Studio expands application creation and operation

Microsoft announces general availability of application creation in Copilot Studio, running on Copilot Managed Runtime. The environment is described in terms of identity and lifecycle management within the organisation's tenant, its administered Microsoft environment. For a business, building an application's interface and operating it with users, permissions and versions are parts of the same project, although each involves a different set of responsibilities.

The announcement mentions building directly in Copilot Studio, through natural language in Copilot Cowork or Code, and through the Copilot Studio command-line interface. The resulting artifacts appear in Copilot Studio and run in the tenant under IT control. These different creation paths do not remove the need to define the application's data, permitted operations and the people who may use the resulting application.

The new Microsoft Copilot harness in Copilot Studio is also presented as generally available. Here, harness means the framework organising agent execution and tool use. Microsoft publishes results from its internal evaluations, but those are not results from a WebHat implementation. Selecting a business solution depends on the company's task and data, rather than automatically transferring a percentage from a supplier's evaluation into a promised business outcome.

Availability stages presented at Ignite

FunctionAnnounced statusDate or condition
Sales, Customer Service, ERP appsGenerally available17 November 2026 announcement
App creation and new harnessGenerally availableCopilot Studio and Managed Runtime
Agent AccountsPublic preview plannedDecember 2026
Activate ERP for SAP ECCPrivate previewAccess limited to the preview stage

Released functions and previews follow different schedules

Agent Accounts is announced for public preview in December 2026. Those accounts, memory and triggers are presented in the context of agents continuing work within shared processes. At the November announcement, the December stage is still in the future. A project depending on it needs to distinguish the current availability of the plugins from the separate schedule for these additional agent capabilities.

Microsoft Contact Center Intelligence is generally available and described as a layer of voice and digital-channel agents over existing contact-centre infrastructure. Separately, Dynamics 365 Activate for CRM is generally available, while the extension of Activate for ERP, beginning with SAP ECC, is in private preview. These products address different problems: customer interaction, CRM migration and assessment of ERP migration work involving existing processes and data.

For entrepreneurs assessing custom applications with AI integration, a useful comparison starts with existing systems, the process to improve and the availability stage of the required function. Integration services can connect applications and data around that process. Microsoft's announcement supplies concrete functions to assess. Choosing between a configurable product and custom development depends on the company's requirements and infrastructure, rather than on the product announcement alone.