What it does

Copilot drafts and rewrites customer emails inside the Dynamics 365 rich text email editor on lead and opportunity records. Sellers pick a prompt or type their own, then adjust length, tone or language before the text goes into the email body.

Key facts

• Switched on per app, not per environment: Power Apps > Apps > your app > Settings > Features > Contextual email drafting with AI set to Yes, then save and publish the app.
• Supported only for lead and opportunity records through the Dynamics 365 email experience. It isn't a general-purpose email assistant across every table.
• No Microsoft 365 Copilot licence is required. This is the in-app Dynamics feature, distinct from Copilot for Sales in Outlook and Teams.
• Two commands in the editor toolbar: Draft with Copilot to generate from a prompt, and Adjust with Copilot to rework text the seller has already selected.
• Generated content offers Keep it, Start over, Discard, Adjust and Translate. Adjust covers length (Short, Medium, Long) and tone (Friendly, Professional, Formal).
• Translate is limited to the languages supported by your environment, and Show original returns the text to the language it was generated in.
• The responsible AI FAQ for Copilot for emails states English-only support, and that email thread summaries and follow-up reminders inside Dynamics 365 Sales were released to public preview while the equivalent Outlook capabilities were already generally available. Watch this one — the FAQ page lags the product.
• The FAQ is explicit that there are no end-user settings to tune the model's behaviour. What sellers get is the prompt, the tone and the length, and nothing else.
• Copilot email features are separate from the outreach emails the Sales Qualification Agent generates. Those are configured on the agent and follow the agent's own language and signature settings.
• Data goes to Azure OpenAI for generation, which may mean processing outside your geographic region depending on your data movement consent.

When to use / skip

Turn it on. It costs one app setting, needs no extra licence, and drafting is the one Copilot capability sellers use without being nagged. The quality is fine for a first draft and the tone control is the part people actually keep using.

Where it disappoints is any org that has invested in email templates and a house style. Copilot writes competent, generic B2B prose; if the client's marketing team has strong opinions about voice, expect friction. It also assumes sellers send email from inside Dynamics. If your sellers live in Outlook — which most do — the in-app editor is the wrong surface and the Outlook-side experience is the conversation to have instead.

Configuration decisions

• Which apps get the feature toggle. It's app-scoped, so a custom sales app needs it enabling separately from Sales Hub.
• Whether sellers are expected to send email from inside Dynamics at all, or from Outlook. That decides whether this feature matters on the project.
• How the feature sits alongside existing email templates — replacement, starting point, or template first then Adjust with Copilot.
• Whether translation is in scope, which depends on the languages provisioned in the environment.
• What the review-before-send expectation is, and whether that goes into a written policy or just into training.
• Whether any of this overlaps with agent-generated outreach, so sellers understand which emails they wrote and which the agent did.

Gotchas

• Publishing the app is part of the enablement step, not an optional extra. Toggle set, app not published, feature invisible — and the toggle still reads Yes.
• The scope is genuinely lead and opportunity only. Sellers who try it on a contact or a case will report it as broken.
• The English-only statement in the responsible AI FAQ sits awkwardly next to a Translate command in the editor. Test the languages your client needs rather than trusting either page.
• Nothing stops a seller sending an unreviewed draft. Copilot will happily assert facts about pricing or delivery that nobody in the business has agreed.
• This is not Copilot for Sales in Outlook, and clients conflate the two constantly. Different surface, different licensing, different capabilities — be precise in writing.
• Because generation calls Azure OpenAI, the same data movement consent conversation applies here as everywhere else in Copilot. It's not exempt because it's "just an email".

Consultant notes

• Demo Adjust with Copilot on a scrappy draft rather than Draft with Copilot on a blank page. Turning a seller's own rushed email into a formal short one lands better than generating one from nothing.
• Say clearly which Copilot you're demonstrating. Write it into the workshop notes so the client's licensing conversation doesn't get muddled later.
• Agree a review-before-send line with the client and get it into seller training. It's the cheapest risk control on the whole Copilot workstream.
• Check the feature toggle in every environment on the promotion path — it's an app setting, so it doesn't necessarily travel the way people expect.
• If the client's sellers work in Outlook, be honest that this feature will see little use, and spend the effort where the emails are actually written.

---

Worth another look if the responsible AI FAQ drops the English-only limitation, or if email drafting moves under the Sales agent.