Microsoft Dragon Copilot Pricing: What It Actually Costs

Dragon Copilot is a named user subscription, which means one licence per clinician regardless of how many encounters that clinician records. SAMexpert's licensing guide describes three role specific options as of late 2025: Physician Per User, a flat monthly fee covering speech, ambient capture and note generation; Physician Flex, a cheaper speech only subscription where the AI features are metered through Azure consumption at 300 units, or 3 US dollars, per ambient structured note; and Nursing Per User, a US only licence for nursing workflows including flowsheet capture. There is no Nursing Flex option.

The Flex model matters because it turns a seat cost into a usage cost. A clinician who sees 20 patients a day and wants an ambient note for every one would generate about 60 US dollars a day in consumption on the published unit rate, which is far more than a flat licence. A clinician who uses ambient capture twice a week would pay far less. The right licence depends on real encounter volume, which is why you should count it before the sales call rather than after.

Purchasing runs through standard Microsoft channels: the Microsoft Customer Agreement, Cloud Solution Provider partners, Enterprise Agreements and their subscription and education variants. If your organisation already holds an Enterprise Agreement, Dragon Copilot is usually added to it, which changes who you negotiate with and when. It is a separate product from Microsoft 365 Copilot with its own licence, and the two are not interchangeable. The Microsoft licensing guidance for this is summarised on our Dragon Copilot vendor page.

The licence covers the application: speech recognition, ambient capture, note generation and the clinician facing tools. The things that most often land outside it are the ones that determine whether the product works in your chart.

• Implementation. DictationOne listed a one time per user implementation fee alongside the subscription. Larger deployments are scoped as professional services, either by Microsoft or by a partner. Ask for it as a separate line.
• EHR integration. Dragon Copilot is embedded in Epic, athenahealth, MEDITECH and others through the vendor programmes, but your EHR side build, interface testing and analyst time are yours. Epic customers should read our Dragon Copilot and Epic integration page before assuming the marketplace listing means zero work.
• Consumption. On a Flex licence, every ambient note is metered. On a per user licence after May 2026, Plaud reports a per encounter consumption component too. Ask for the unit rate, the estimation method and a cap.
• Training and change management. Not in the licence. Budget it internally or buy it from a partner.
• Nursing and specialty modules. Nursing is a separate licence. Radiology and other role specific packaging is described in datasheets rather than priced.

A quote that lists only a per user figure is incomplete. Ask for the licence, the consumption estimate at your volume, the implementation fee and the partner services as four separate lines so you can compare them with other vendors' quotes line by line.

None of Dragon Copilot's enterprise competitors publish either, so the comparison is between reported ranges and contract structures rather than list prices.

Two things stand out. First, if the 150 dollar reseller figure survives into the current licence, Dragon Copilot is priced closer to the self serve tier than to Abridge or Suki, which is consistent with Microsoft using its distribution to compete on price. Second, the consumption component means the comparison only holds at a specific encounter volume. Convert every quote to cost per clinician per month at your real volume, then again at one and a half times that volume, as we recommend in the pricing comparison.

For a health system already inside a Microsoft Enterprise Agreement, the effective price can also be shaped by what else is in the agreement. That is a negotiating advantage if you use it and a lock in risk if you do not notice it.

Work it through with the reported figure and your own numbers rather than the vendor's case study. Take 150 US dollars per user per month, which is 1,800 a year. A clinician on 200,000 US dollars a year working 2,000 hours costs 100 dollars an hour. If ambient documentation saves that clinician 30 minutes a day across 220 clinic days, that is 110 hours, or 11,000 dollars of clinician time a year, against 1,800 in licence. Even if only a third of the saved time becomes something the organisation can use, whether extra encounters, earlier finish times or fewer late notes, the licence pays for itself.

Now add the costs the licence does not show. A one time implementation fee per user, a two to three week productivity dip during adoption, internal analyst time on the EHR side, and note review minutes every day for as long as the tool is in use. If review takes three minutes a note across 20 notes, that is an hour a day, which consumes much of the saving. The tool is worth it when the net of those two columns is positive at your volume, and that is a measurement question, not a belief.

The AI scribe ROI calculator takes your documentation minutes, clinician cost and encounter volume and produces a break even licence price. Run it before the demo, and bring the number to the negotiation. Our ambient scribe use case page covers how to baseline the documentation minutes in the first place.

Six items move the price or the risk, and all are easier to fix before signature.

1. Licence type by role. Do not put every clinician on the same licence. Model per user against Flex at each clinician's real encounter volume and put the low volume users on Flex.
2. Consumption cap. If any part of the fee is metered, ask for a monthly cap or a committed volume band with a true up, so the finance team is not surprised.
3. Term. Reseller listings show a 12 month minimum. Ask for pilot months to be credited against the first year, and ask before the pilot starts rather than after.
4. Enterprise Agreement co-terming. If Dragon Copilot joins an existing EA, align renewal dates and make sure the scribe can be dropped at renewal without disturbing the rest of the agreement.
5. Implementation scope. Get the per user implementation fee, partner services and EHR build responsibilities in writing, with named deliverables.
6. Data terms. Retention, model training use and subprocessors. The BAA is standard; the annex on data use is where the negotiation is. Our HIPAA and AI compliance page lists the clauses to ask for.

Name your ceiling early. Vendors price against perceived willingness to pay, and a buyer who arrives with a break even figure from their own model negotiates a different deal from one who arrives with a feature list.

Dragon Copilot pricing is unusual in that the licence structure changed mid 2026 and the public record has not caught up. Most buyers are now comparing a quote for a licence that has no published reference point against competitors that also publish nothing. That is exactly the situation in which a vendor's own framing wins by default.

An independent review does three things. It builds the cost model from your encounter volume and documentation baseline, so the quote is judged against a number that is yours. It reads the consumption, implementation and data terms line by line against the alternatives, including whether an existing Microsoft agreement helps or traps you. And it sequences the pilot so that the metrics you agree with the vendor are the ones that decide the contract.

Clunic takes no commissions or referral fees from Microsoft or any other vendor. If you are about to sign, our vendor selection service runs the comparison and the negotiation support, and you can book a call to talk through where you are in the process.