Microsoft 365 E7 and a new wave of role-based agents mean your Dynamics 365 sales, service, and finance intelligence now lives inside Microsoft 365 Copilot, in Outlook, Teams, and Excel, and not only inside the CRM window. Microsoft made E7 generally available on 1 May 2026, the first new enterprise tier since E5 arrived in 2015, bundling Microsoft 365 E5, Microsoft 365 Copilot, and Agent 365 at around 99 dollars per user each month. Alongside it, a Sales Agent, a Finance Agent, and a growing family of role-based agents now surface where people already work.
For organisations running Dynamics 365, this is a genuinely good moment. Capability that once sat behind a specialist CRM seat is becoming something far more of your workforce can reach, and the opportunity is large. Sellers, service managers, and finance teams can now get a useful answer without learning a new application first. The more interesting question, the one worth getting right early, is where your system of record sits once the intelligence stops living only in the CRM.
What is Microsoft 365 E7?
Microsoft 365 E7, sometimes called the Frontier suite, is Microsoft’s AI-first enterprise licence, generally available from 1 May 2026 at roughly 99 dollars per user each month. It bundles Microsoft 365 E5, Microsoft 365 Copilot, and Agent 365, the governance layer for deploying and monitoring AI agents, together with expanded Microsoft Entra identity controls and unified Defender and Purview security. Bought separately the components run close to 105 dollars, so the suite rewards organisations that were heading towards full Copilot and agent adoption anyway.
That bundle tells you where Microsoft is heading. For the past decade the enterprise conversation centred on E5 and security. The new centre of gravity is agents: software that does not just surface information but takes steps on your behalf. For Dynamics customers the headline is not the price, it is that the licence most of your knowledge workers may already sit under is becoming the delivery vehicle for business-application AI.
What are role-based agents in Microsoft 365 Copilot?
Role-based agents are task-specific assistants Microsoft has built for particular business functions and surfaced inside Microsoft 365 Copilot rather than only inside Dynamics 365. The Sales Agent acts as a seller’s daily command centre, pulling deal and account context from CRM data and from Microsoft 365 sources such as email and meeting summaries. The Finance Agent handles reconciliation, variance analysis, Excel data preparation, and customer communications from Outlook. A Scheduling Operations Agent supports field service. Because they meet people in Outlook, Teams, and Excel, adoption no longer depends on someone opening the CRM first.
The adoption implication is the part to get excited about. CRM has always had a last-mile problem: the insight is in the system, but the seller is in their inbox. When the Sales Agent drafts follow-ups inside Outlook and briefs a representative in Teams before a call, the friction that kept people out of the CRM starts to fall away. You are no longer asking busy people to change where they work, you are bringing the intelligence to them.
Do you still need Dynamics 365 if Copilot has a Sales Agent?
Yes. The Sales Agent in Microsoft 365 Copilot is an interface and a reasoning layer, not a system of record. It reads from Dynamics 365 and writes back to it; the structured pipeline, the entitlements, the audit trail, and the integrations with ERP and finance still live in the CRM platform. Think of Copilot as widening the doorway into Dynamics rather than replacing the building behind it. The pairing is complementary: Dynamics 365 holds the governed truth, and Copilot brings that truth to people who would never have logged into the application.
This distinction matters commercially too. Some teams will look at a capable Sales Agent and ask whether they can trim Dynamics seats. For light-touch users who only ever consumed information, that conversation is fair and worth having. For the people who build pipeline, manage entitlements, and rely on the deeper automation, the full application still earns its keep. The smart move is to match the licence to the role rather than assume the agent replaces the platform.
Where should your system of record stay?
Your system of record should stay exactly where your governed, auditable customer data already lives, which for most Dynamics organisations is Dataverse and the Dynamics 365 applications built on top of it. When a Sales Agent drafts an email from a meeting summary, or a Finance Agent prepares a reconciliation, the question is which version of the truth it trusts and where its output lands. Good design keeps the CRM authoritative: agents read widely, but write back into structured records rather than leaving conclusions stranded in chat threads.
In practice this is a design choice you make once and benefit from for years. Define the CRM as the place where decisions become durable records, and treat Copilot as the surface that gathers context and proposes actions. When an agent writes an updated close date or a logged interaction straight back into Dynamics, the audit trail strengthens your data. When it leaves that conclusion in a chat window, you have created shadow knowledge that no one can govern or trust.
How do you govern agents across CRM and email?
This is where Agent 365, bundled into E7, earns its place. Governing cross-application agents means giving each one a managed identity, scoping what it can read and write, restricting which destinations it may reach, and logging every action so you can answer who did what later. Microsoft has extended Entra controls to Copilot Studio agents and to agents running on user devices, with the ability to flag unsanctioned use and block prompt-based attacks. The practical work is deciding, per agent, what good behaviour looks like and what is off limits.
None of this needs to slow you down. The organisations that move fastest are the ones that set sensible guardrails early, then let teams experiment inside them. A clear policy on what each agent may read, where it may write, and which actions need a human in the loop turns governance from a blocker into the thing that lets you say yes to more use cases, not fewer.
How should Dynamics 365 customers prepare?
Preparation is mostly about readiness rather than procurement. Start by checking that the Dynamics data these agents will read is clean, current, and well structured, because an agent surfacing a stale opportunity in Outlook is more visible, and more damaging, than the same record buried in the CRM. Map which roles gain most from agents meeting them in Teams and Outlook, and pilot there first. Clarify your write-back rules so agent output lands in governed records. Then model the cost honestly: E7 at around 99 dollars per user is compelling where people will use Copilot and agents daily, and harder to justify where they will not.
There is a satisfying knock-on effect here. The data hygiene work that makes agents trustworthy, deduplicated accounts, current ownership, consistent stages, is the same work that improves forecasting, reporting, and everyday CRM life. Preparing for role-based agents is rarely wasted effort. It is the CRM housekeeping many teams have meant to do anyway, now with a clear and visible payoff.
The Sirocco perspective
We see E7 and the role-based agents as one of the more genuinely useful shifts Microsoft has shipped in a while, because it takes intelligence that was locked behind specialist seats and brings it to the people who actually talk to customers. Our advice to clients is to embrace the reach and stay deliberate about the foundations. Keep Dynamics 365 as the authoritative system of record, decide your write-back rules before you scale, and use Agent 365 to govern from day one rather than retrofitting control later.
As an independent, vendor-agnostic CRM partner, we help organisations judge where Copilot agents add value, where a full Dynamics seat still pays for itself, and how to keep one trusted version of the truth as AI spreads across the stack. Get this right and the upside is substantial. If you are weighing how E7 and the new role-based agents fit your Dynamics 365 estate, we are happy to talk it through. You can schedule a consultation whenever the timing suits.
Get in Touch
If you are mapping how Microsoft 365 E7 and the new role-based agents change your Dynamics 365 setup, tell us where you are heading and we will help you keep your CRM the single source of truth.
