Legal work moves beyond general prompts

Microsoft has made more than 20 legal skills generally available in Microsoft Copilot. Announced on 15 October, the capabilities build on the former Legal Agent and now appear as legal plugins. They support deeper work inside Word, multi-file workflows in Cowork and connections to specialist systems and sources used by legal teams.

The distinction from a prompt library matters. Legal answers depend on precedent, defined terms, organisational standards and changing regulation. Microsoft says each skill combines legal-specific reasoning with native Microsoft 365 features so output appears in the format lawyers already review, rather than as detached chat text that must be copied into a document.

Word keeps edits native and reviewable

For contract redlining, Copilot can propose clause changes while Word applies them as tracked changes and preserves formatting. When drafting, it can draw on approved precedents in SharePoint and use Word content controls for structured placeholders. A preview later this month is intended to help users move between defined terms and their definitions across a document.

Other skills turn research into structured guidance, build case chronologies, surface dates and unanswered questions, and convert meeting records into formal minutes or resolutions. Native edits preserve the comparison tools legal professionals rely on. Copilot proposes language, but a user must approve it before it becomes part of the working document.

Plugins connect specialist legal systems

The plugin registry is beginning to add tools across legal research, matter management, transactions, signatures, specialist legal AI and e-discovery. Named partners include Bloomberg Law, iManage, NetDocuments, Docusign, Harvey, Legora, Everlaw and Relativity. Availability will expand over time, so administrators should confirm which connector and data region applies to their tenant.

Connections can reduce context switching, but each one extends the data and permission surface. Legal teams should understand what a plugin can read, create and transmit, how source citations appear and whether an action is reversible. A familiar Copilot interface does not make every connected provider part of the same contractual or technical boundary.

Early usage shows acceptance, not final accuracy

Since an April Frontier release, more than 1,800 users have generated nearly 100,000 edits and retained about seven in ten suggestions, according to Microsoft. Internal evaluations report more than 90 per cent fluency, 95 per cent conciseness and 85 per cent relevance. These measures describe language quality and user acceptance rather than legal correctness in every jurisdiction.

Firms should build evaluation sets from their own clauses, playbooks and risk positions. Useful measures include missed issues, inappropriate precedent, reviewer corrections and time to an accepted draft. An edit that reads fluently can still change liability or conflict with a negotiated commercial position, so substantive review remains essential.

Enterprise controls follow the document

Microsoft says prompts and responses remain within the Microsoft 365 service boundary with enterprise data protection. Copilot uses only content the user can access, honours sensitivity labels and does not use customer prompts, responses or documents to train foundation models. Approved templates and playbooks help teams apply consistent standards.

The global release gives legal teams a more integrated starting point for AI-assisted work, but governance should begin with selected matters and clearly approved sources. Organisations need plugin approval, audit retention, privilege guidance and escalation for uncertain output. The benefit is faster first-pass work inside familiar tools; legal judgement, client duty and responsibility for the final text stay with professionals.

What to watch next

Legal teams should also plan for disagreement between a plugin’s source and an internal precedent. Copilot should expose both rather than silently choosing one. Matter-level access, ethical walls and retention requirements may be stricter than ordinary Microsoft 365 permissions. A pilot should therefore involve information governance and security alongside practising lawyers, with clear rules for client consent and prohibited data.

Practical implications

Citation and provenance are especially important when research enters drafting. A lawyer should be able to distinguish a clause drawn from an approved precedent, a statement returned by a research plugin and language generated by the model. That trail supports verification and prevents a polished document from concealing an unsupported legal proposition.

The keep rate reported by Microsoft should not be interpreted as a measure of legal safety. Users may accept minor stylistic edits more often than consequential risk language, and the aggregate does not show performance by document type or jurisdiction. Local evaluations should weight errors by consequence instead of treating every suggested edit equally.

Pricing and licence eligibility also affect adoption. The announcement says capabilities are available to Microsoft Copilot customers worldwide, while individual plugins may have their own subscriptions and terms. Administrators should map the full cost and data path for each workflow before presenting the experience as a single integrated legal platform. They should document which provider answers each request, where matter data is processed and how an organisation can disable a plugin without breaking an approved workflow.