GOVERNATLAS / PRODUCT DOSSIER

Microsoft Dragon Copilot

Microsoft describes Dragon Copilot as an AI assistant for drafting clinical documentation. Its documentation discusses HIPAA support, up-to-90-day retention for specified data and de-identification or pseudonymization for model improvement.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate Microsoft Dragon Copilot for the specific documentation and clinician-review workflow you intend to use. Define who may handle the data and approve the result before considering efficiency claims.

What this record does not establish

Microsoft documents HIPAA-supporting environments, retention and model-improvement data handling. The sources reviewed here do not establish the buyer's applicable BAA; confirm Dragon-specific licensing and contractual coverage. The public statements remain vendor attributed; no executed customer agreement, clinical validation or independent security testing is established.

2 current sources · 3 published assertions
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Use a fictional dictated encounter and a correction. Inspect the generated draft and approval process, then ask the administrator to show the actual tenant, service entitlement, data lifecycle and agreement applying to that configuration.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. Retain the synthetic scenario, generated draft, corrections and clinical reviewer decision.
  2. Obtain the applicable agreement version, service and integration boundary before sharing PHI.
  3. Assign owners and dates for unresolved consent, retention, training-use and exit questions.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

The Dragon Copilot FAQ describes de-identified or pseudonymized data being used for AI model improvement. This is not a blanket no-training statement; buyers should reconcile the current product documentation with their agreement and data settings.

Source, dates & preserved provenanceMicrosoft — Product and account FAQ ↗

Authority: vendor owned
Observed 2026-11-02 · Reviewed 2026-11-02 · current until 2026-12-02

Artifact SHA-256: 21555fe5ee04130e51fa78db3294e4a722e662449c3ebecb0d1e85edd4791b38

The hash identifies the preserved capture. The live source may have changed.

02
vendor asserted

Microsoft's Dragon Copilot FAQ says its environments are built to support HIPAA and other listed privacy standards, and that specified audio, recognized text, transcript and flowsheet data may be retained for up to 90 days. These are vendor-documented practices, not a deletion test.

Source, dates & preserved provenanceMicrosoft — Product and account FAQ ↗

Authority: vendor owned
Observed 2026-11-02 · Reviewed 2026-11-02 · current until 2026-12-02

Artifact SHA-256: 21555fe5ee04130e51fa78db3294e4a722e662449c3ebecb0d1e85edd4791b38

The hash identifies the preserved capture. The live source may have changed.

03
vendor asserted

Microsoft describes Dragon Copilot as an AI assistant that drafts clinical documentation. Scope: this healthcare product, not general Microsoft 365 Copilot or every service branded Copilot; clinical output has not been independently validated by GovernAtlas.

Source, dates & preserved provenanceMicrosoft — Official product overview ↗

Authority: vendor owned
Observed 2026-11-02 · Reviewed 2026-11-02 · current until 2026-12-02

Artifact SHA-256: 47a611d69081bb6bf1a0bd8e44ea24a49b1dbb29cf828b4c9357a1029a1ee6b7

The hash identifies the preserved capture. The live source may have changed.

Source register

Microsoft — Official product overview ↗vendor owned · captured 2026-11-02
Microsoft — Product and account FAQ ↗vendor owned · captured 2026-11-02
Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Which service, plan, region and integrations does the proposed BAA cover?

02

What retention, deletion and model-training terms apply to our exact workflow?

03

Who validates outputs and owns the clinical or operational decision?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

COMPLIANCE / CLAIMS, SCOPE & GAPS

Start with the requirement.
Inspect the support.

Prepare your vendor review ↗

These labels describe this dossier’s current evidence coverage. A published mention may be a framework mapping, a qualified assertion or a limitation; it is not a compliance finding.

HIPAA

Published mention available

US healthcare privacy & security

BAA availability not established

Microsoft documents HIPAA-supporting environments, retention and model-improvement data handling. The sources reviewed here do not establish the buyer's applicable BAA; confirm Dragon-specific licensing and contractual coverage.

Read the source-attributed statement

Microsoft's Dragon Copilot FAQ says its environments are built to support HIPAA and other listed privacy standards, and that specified audio, recognized text, transcript and flowsheet data may be retained for up to 90 days. These are vendor-documented practices, not a deletion test.

vendor asserted

Microsoft — Product and account FAQ ↗

Explore HIPAA evidence ↗

For HIPAA-regulated use, request service-specific BAA eligibility, processing scope and responsibility details. Missing evidence here does not establish noncompliance. Payment cannot alter these evidence labels.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗