The Avvoka connector for Microsoft 365 Copilot is now available, built on the Model Context Protocol.

Lawyers draft in Word, and increasingly with Microsoft 365 Copilot alongside them. With the Avvoka connector, Copilot can now draft from your own templates, your clause library and the logic your firm has agreed.

The connector uses the Model Context Protocol, the open standard Copilot uses to reach other systems to give Copilot a controlled route into your Avvoka workspace. An administrator enables it once, each user authenticates their own Avvoka account, and Avvoka becomes something Copilot can query and act through, inside the conversation the lawyer is already having.

Copilot brings the speed and the interface lawyers are already working in. Avvoka brings the drafting accuracy through the templates, logic and approved positions the firm has built. Together they cover a piece of legal work neither could complete alone.

For anyone already drafting alongside Copilot, it removes the round trip: no exporting a draft to check it against the precedent bank, no pasting a clause back in, no second window open to find the fallback the firm agreed last year.

What a lawyer can do

• Draft from a firm template. Copilot works through the Avvoka questionnaire in conversation and Avvoka generates the document from your template's logic, so the output is accurate and follows your firm's rules.

• Pull and amend an existing document. Retrieve something already in Avvoka, make the changes, keep them tracked.

• Query the clause library. Ask for the approved position or the agreed fallback and get it, rather than reconstructing it from memory or from the last deal that looked similar.

• Keep the work where it belongs. Everything lands back in Avvoka with the audit trail, permissions and version history intact.

The connector inherits the permissions the user already has. If a lawyer can't see a matter in Avvoka, they can't reach it through Copilot either.

How it works in practice

A client wants a shareholders' agreement out by Friday.

The associate opens Word and asks Copilot to start it. Copilot works through the Avvoka questionnaire in the chat, and Avvoka generates the draft from the firm's template – in your firms style, same logic, same approved wording that the knowledge team maintains.

Whilst drafting there's a question on drag-along thresholds. The associate asks Copilot, and the firm's approved fallback comes straight back from the clause library.

The counterparty's markup arrives on Tuesday. The associate pulls the document out of Avvoka, works through the changes, and it lands back with the version history intact.

The lawyer stays in Word throughout. The document stays the firm’s.

Why this matters

Until now, firms have had two good things that didn’t quite meet in the middle: a general assistant that drafts quickly, and an automation platform holding the templates, house style and approved fallbacks the firm has invested years in. Each has done its own job well. What hasn’t been possible is using them together.

Connecting the two means the lawyer stays in the tool their firm has already rolled out. The document still comes out of the template your knowledge team maintains, with the fallbacks they approved, in the format your clients expect. The AI handles the conversation. Avvoka handles the drafting.

For firms already running Avvoka, this is not a new system to buy or a new place to work. It is a route into the one you have.

Getting started

The connector is available to Avvoka customers on Microsoft 365 Copilot. Setup is handled once by an administrator, after which each user authenticates their own Avvoka account. Get in touch with your Avvoka contact to enable it.