Sales in Microsoft 365 Copilot (formerly Copilot for Sales)

What it does

Brings CRM context and AI assistance into Outlook, Teams and Microsoft 365 Copilot chat — email summaries and drafts, meeting preparation and recaps, and saving activities back to Dynamics 365 without opening it. It is the Microsoft 365-side companion to the Copilot inside the Sales app, deployed and administered by M365 admins rather than CRM admins.

Key facts

Every user needs a Microsoft 365 Copilot licence plus an eligible CRM licence — Dynamics 365 Sales, or Salesforce Sales Cloud Professional and above. There is no standalone purchase route; it comes as part of the M365 Copilot offering.
Deployment runs through the Microsoft 365 admin center for the Outlook and Copilot surfaces, and the Teams admin center for Teams. It can take up to 48 hours for the app to appear after deployment.
A Teams app setup policy is used to install and pin it for users, covering the personal app and user-created meetings.
Meeting features depend on Transcription being enabled in the Teams meeting policy — check the Global (Org-wide default) policy under Recording & transcription.
Server-side synchronisation for email and appointments must be configured for sellers to save Outlook activities to Dynamics 365.
Salesperson, Sales Manager, System Administrator and System Customizer roles carry the required privileges out of the box. Custom security roles need them added manually.
Administrator settings are reached from inside the app itself — open the Sales personal app in Outlook or Teams, sign in as an admin, then Sales > Settings. Some settings are tenant-level (who can use Copilot AI at all), others are per CRM environment.
Environment-level settings cover access, Save to CRM field mapping for emails and meetings, which forms and fields appear, and custom AI instructions for account and opportunity summaries.
Admin changes take up to 15 minutes to reflect, and users have to sign out and back in to pick up permission changes.
Single tenant only, using Microsoft Entra ID. Guest users cannot use it.
Not supported on Dynamics 365 or Exchange on-premises, and not for Dataverse or Power Apps customers without a Dynamics 365 licence.
Not available in US GCC, GCC High, DoD or other sovereign clouds, and not in local-region data residency geographies.
Minimum Outlook versions: Windows build 2206 (15330.20196) or later, Mac 16.78 or later.

When to use / skip

If the client has bought Microsoft 365 Copilot and runs Dynamics 365 Sales, deploy it. The incremental cost is admin time, and the email and meeting surfaces are where sellers actually spend their day.

If they have not bought M365 Copilot, this is not a Dynamics decision at all and you should not let it become one in your scope. The licence is per user and it is not cheap; a Sales project cannot carry that business case on its own. Point the client at the in-app Copilot in Dynamics 365 Sales, which they already have, and treat this as a separate initiative.

Be honest about the naming churn. Clients have heard Viva Sales, then Copilot for Sales, now Sales in Microsoft 365 Copilot and Sales agent. It is broadly the same lineage, and quoting old documentation at them makes it worse.

Configuration decisions

Whether meeting transcription goes on tenant-wide or via a targeted policy. This is a legal and works-council question in most UK and EU organisations, and it gates the meeting features entirely.
Which fields the Save to CRM experience shows and writes for emails and meetings — the default set rarely matches a customised opportunity model.
Whether custom AI instructions are used to shape account and opportunity summaries, and who signs off on the wording.
Tenant-level versus environment-level enablement, particularly where the client has sandbox and production environments and does not want summaries generated against test data.
Which security roles get the privileges, and whether the client's custom seller role is one of them.
Teams pinning: pin for everyone, or make it opt-in. Pinning for everyone drives adoption and irritates people who do not have CRM.

Gotchas

The 48-hour appearance delay is real and catches out anyone who scheduled a demo for the afternoon of deployment.
Meeting features silently do nothing when transcription is off. There is no message explaining why.
Custom security roles are the usual failure: the roles listed as supported are the out-of-the-box ones, and most clients replaced those years ago.
Guest users get nothing. Clients with contractors on guest accounts will report it as a bug.
Save to CRM depends on server-side sync being healthy. If mailboxes are not enabled, activities quietly do not land.
Sovereign cloud and local data residency exclusions are absolute. Confirm the tenant's geography before committing anything to a statement of work.
The 15-minute settings delay plus the sign-out requirement makes admin changes feel broken during testing.

Consultant notes

Establish the M365 Copilot licence position before the first workshop. It determines whether this is in scope at all.
Get the Teams admin and the M365 admin named early — you cannot deploy this from the CRM side, and waiting on a ticket queue will cost you a sprint.
Demo the meeting recap saving into Dynamics. That is what buyers respond to; the email drafting demo is now unremarkable.
Push back on requirements that assume it works for guests, on-premises Exchange, or a sovereign tenant, and say no early rather than investigating.
Before go-live, verify Save to CRM field mapping against the client's customised forms, with a real seller's role rather than an admin account.

Worth another look after the next wave — this one has been renamed more than most.