Dynamics 365 in Copilot brings sales tasks into the flow of work, so a seller can review account context, act on a renewal and update CRM records without moving between applications for each step. It matters to sales teams that want to spend less time assembling account information and recording routine work. Microsoft Events demonstrates the experience as part of a broader session on agentic business applications.
The central change is that Copilot can serve as an interface to Dynamics 365 business processes, rather than leaving users to do every task inside the CRM application. In the demonstrated scenario, the seller starts from Copilot’s Today page, sees pipeline information and a renewal needing attention, and starts a task from that view.
Copilot then brings together business-process context and information from the employee’s work environment, including emails, meetings, chats and documents. The result is not just a summary: it identifies issues that may affect the renewal and suggests next actions. The session presents Dynamics 365 Sales and Service, alongside Work IQ, as components supplying context for the experience.
The goal is to let people work with business applications through a familiar interface while the underlying business system remains part of the process. Existing Dynamics 365 experiences are not presented as going away. Instead, the session describes a future where users can choose native app experiences or work through Copilot and other connected applications.
The demonstrated workflow is aimed at sellers managing customer accounts and renewals. It may also matter to sales operations teams and Dynamics 365 administrators evaluating how CRM work could appear inside Copilot. The example depends on customer and opportunity information in the business application, together with relevant work context such as email, chat and meeting information.
The presentation describes Dynamics 365 as part of Microsoft’s AI stack and shows it connected to Copilot. It also positions Microsoft IQ as the layer for business knowledge and process context, with Agent 365 as a governance layer. These are the session’s architectural framing; the example does not provide a licensing or tenant setup checklist.
For teams considering this approach, the useful starting point is a repeatable process with clear records and next steps, such as reviewing a renewal, identifying risks and coordinating follow-up. The example is a demonstration, not a complete deployment guide, so organizations should assess their own data, permissions and process requirements before relying on similar actions in production.
The session also shows a separate recurring task using Autopilot. A salesperson can create a routine for Monday morning at 8:00 AM to receive updates on priority accounts and competitive intelligence. The presenter describes this as work that had previously taken several hours each week in that example.
The demonstration focuses on a sales renewal and does not walk through every Dynamics 365 workload or every configuration an organization would need. It should not be read as a guarantee that every seller, tenant or process has the same Copilot experience. The practical value depends on the context available to the workflow and on whether the suggested actions fit the organization’s process.
There is also a choice of working style. Users can continue in Dynamics 365’s native experiences, which the session says remain in place, or use Copilot as a more connected interface. Teams evaluating the approach should decide which actions can be prepared or suggested and which require a person to review them. The demo itself shows messages being reviewed and editable before sending, rather than treating customer communication as invisible background work.
The larger session includes custom agents and customer engagement, but the demonstrated renewal flow is the clearest practical example of Dynamics 365 work in Copilot. It shows a direction for reducing application switching; it does not provide a detailed setup procedure for connecting data or governing an organization’s agents.
In the demonstrated renewal workflow, sellers can review account context, see recommended actions, prepare and send follow-up messages, and log updates to CRM from Copilot.
No. The session says users can continue working in native Dynamics 365 experiences while also using Copilot and other connected interfaces.
The demonstration shows an Autopilot routine scheduled for Monday at 8:00 AM to provide updates on priority accounts and competitive intelligence.