Copilot for Legal drafts from your SharePoint precedents. Six lessons for in-house teams on cleaning up templates and playbooks before rollout.

On October 15, Microsoft launched Copilot for Legal. LawSites reported that it makes Microsoft the fourth AI giant in five months to build a legal vertical, after Anthropic (May), Google (August) and OpenAI (September). The headline features are what you'd expect: more than 20 legal skills in Word and Cowork, playbook-based review, redlines as native tracked changes, and plugins from more than two dozen legal tech partners.
The detail that matters most to an in-house team got less attention. According to LawSites, drafting can draw on approved precedents stored in SharePoint, and a feature called Work IQ connects Copilot to matter and standards context beyond the open document.
Translation: the AI is only as good as the folder it reads from. If your SharePoint looks like most legal department SharePoints, that's not great news.
For years, "the precedent folder" was where good intentions went to retire. It held four versions of the NDA, a 2019 MSA someone swore was "the clean one," and a file called FINAL_v7_use-this-one.docx. Humans worked around the mess because humans know which file is the real one.
An AI drafting assistant doesn't. Point it at a messy library and it will confidently draft from the wrong template, in perfectly formatted tracked changes. That's arguably worse than a blank page, because it looks finished.
Artificial Lawyer ran a piece the same day, "Old Problems, New Tools," making the broader point: AI hasn't changed the core problems of knowledge management. It has exposed how fragmented knowledge already was. The author argues you need a knowledge strategy, not just an AI strategy, and lists "recording why a document was deemed final" among the problems no new tool will fix for you.
Pick one approved template per agreement type and archive the rest. Not "move to an Old folder." Archive. If it's in the library, the AI will treat it as fair game.
Playbook review only works if the playbook exists outside your senior counsel's head. Fallback positions, walk-away points and approval thresholds need to be written, versioned and owned by a named person.
A clause with no rationale is a clause the AI can't apply with judgment. Add a one-line note to each playbook position explaining why you hold it. Your future self, and your future AI, will thank you.
Legal IT Insider notes that partner plugins pull in information subject to your organization's existing access controls. That's reassuring only if those controls are right. Before rollout, confirm that privileged matter folders aren't readable by half the company because someone shared a link in 2022.
Microsoft reports that its Legal Agent early-access program had more than 1,800 users and that roughly seven in ten suggestions were kept. LawSites also notes Microsoft hasn't published results on an independent legal benchmark. Run your own test on ten real contracts before you tell the CFO anything.
"Copilot vs. our specialist tool" is the wrong question. Map tasks instead. First-pass review of a vendor NDA in Word? Maybe Copilot. Portfolio analytics, obligation tracking at scale, or litigation workflows? Your specialist tools may still win. Legal IT Insider's write-up of a Legal Geek talk the same week put it well: the question has shifted from which tool to buy to whose stack to rely on.
None of this is exciting. Nobody gets a standing ovation at the leadership offsite for archiving 400 duplicate templates. But it's the work that decides whether a Word-native AI makes your team faster or just makes your mistakes faster.
Good news: cleaning up your precedents pays off no matter which AI wins. Microsoft, Anthropic, Google, OpenAI and every specialist vendor will all read from the same library.
If you're rethinking where approved content lives, start with document management and drafting and clause management tools on CorporateLegal.tech. Then compare generative AI legal assistants against the tasks you actually do.