What Legora announced
Legora's headline claim is that legal teams can act on requests with Microsoft 365 context and Legora's legal intelligence while keeping existing user permissions intact. The announcement lists four items:
- Legal intake in Teams (new, generally available). A user mentions "@Legora" to submit a request to the legal team. That request connects to Legora's legal capabilities.
- Agentic search across Outlook and Calendar (new, generally available). Legal teams can use email and calendar context to find the information behind a task. They can also use it to support drafting a response and to prepare follow-up actions. Legora says the lawyer stays in control throughout.
- SharePoint agreement review (beta). The Legora Agent can draw on documents stored in SharePoint to support agreement review. It saves edits back to SharePoint as a new version.
- The Legora plugin in Copilot for Legal (generally available). Users can start legal work from Microsoft 365 Copilot and reach Legora's capabilities from there.
These sit on top of Legora's existing SharePoint and OneDrive integrations and its MCP-powered Copilot plug-in. In Legora's example workflow, a request starts in Teams and emails, meetings and document context inform the work. The lawyer then checks the underlying sources and carries on in Word.
Why this matters to Microsoft 365 admins
Legora describes the problem as scattered inputs. Requests arrive by chat, email and meetings, while the context sits in inboxes, calendars and SharePoint libraries. Its argument is that re-entering requests, forwarding attachments and exporting files creates extra steps. It also says those steps can create document copies outside the original permission controls.
That is a real concern for any tenant that handles privileged material. If the integration works as described, there are fewer shadow copies of sensitive documents. Note that this is Legora's description of the problem and its claimed benefit, not an independently measured result.
The Teams piece has a Slack precedent
The Teams launch follows a plan Legora stated in October. On October 13 it announced Intake, a front door for in-house legal teams, available at launch in Slack. It said then that it planned to extend Intake to Microsoft Teams, email and MCP. The November 16 announcement delivers the Teams part of that plan.
The October announcement also described how Intake works in Slack. The agent asked for missing details in the thread and routed the request to the right legal team as a tracked task with an owner and a due date. Legora's October description said a lawyer reviews work by default, and that teams could pre-approve routine requests such as a standard NDA for automatic completion.
Treat those Slack details as background. The November announcement does not say the Teams version behaves identically.
Permissions: the claim and the gaps
The permission claim is the most important point for IT, and it is the least documented. The announcement does not explain:
- how authorization works, or what is logged for audit;
- what data is stored or retained, and where;
- which mailbox and calendar items the search can reach;
- which follow-up actions the agent can take without approval;
- how access differs across Teams, Outlook, Calendar and SharePoint.
An earlier WindowsForum report on Legora's integration rollout said it pairs Microsoft 365 integrations with live per-request permission checks and runs on Azure OpenAI Service. That is context on how the company has described its architecture. It does not verify the behavior of these new features.
Treat "permissions intact" as a vendor commitment to test in a pilot, not as a guarantee. Corroboration so far is limited to quotes in the release. Linklaters partner Tom Quoroll endorsed the integration, and Microsoft EMEA president Samer Abu-Ltaif said it ensures enterprise security and governance. Neither quote is a disclosed security assessment, and the release gives no measured outcomes.
Don't confuse Legora with Microsoft's own legal plugins
Microsoft's admin documentation covers its own legal plugins for Copilot in Word and Copilot Cowork. Each is managed differently:
- Copilot in Word. The legal plugin is enabled by default for Microsoft 365 Copilot commercial subscribers in Word desktop. Admins can govern it through the Microsoft 365 Apps admin center with a policy named "Legal Skills in M365 Copilot in Word."
- Copilot Cowork. End users add the plugin themselves. Admins control access on the Agent Tools page of the Microsoft 365 admin center, under the plugin name "Legal for Cowork."
That documentation does not explain how to configure or govern the Legora plugin. It would be a mistake to assume those controls apply to Legora's offering. Ask Legora and your Microsoft account team how the Legora plugin is administered. Legora's release also doesn't say whether its "MCP-powered Copilot plug-in" and the "Legora plugin in Copilot for Legal" are technically the same thing.
Practical checklist before piloting
- Confirm prerequisites. The announcement gives no licensing, tenant or geography requirements, and it doesn't say whether availability is universal or phased.
- Treat SharePoint as beta. The review-and-save-as-new-version workflow is not generally available. Test it on non-critical libraries first.
- Map the consent and permission model. Find out what Entra consent Legora asks for, and whether searches run with the user's own rights.
- Check audit and retention. Establish what gets logged in Microsoft Purview or in Legora itself, and what Legora retains.
- Define human review. The release supports a lawyer-in-control expectation for search-supported drafting. It does not say every output or action needs approval, so set your own approval rules.
Analysis
The strategic logic is sound. Lawyers live in Outlook, Teams and Word, and a tool that meets them there avoids the copy-and-paste habit the release warns about. The competitive context is real too. LawFuel reported that Harvey launched its own "Intake" product within a day of Legora's October announcement.
The caveats are also clear. This is a vendor press release, and its figures are company-reported: more than 140,000 legal professionals, more than 2,500 law firms and in-house teams, and over 80 markets. Legora's own site shows a different customer count on another page. There are no independent performance data, and an analyst profile published this week notes that no independent source confirms Legora's return on investment.
Legora is also exhibiting at Microsoft Ignite from November 17 to 20 in San Francisco, at booth 1726. Expect more detail there, and ask the hard permission and audit questions before you deploy.
References
- Legora extends offering with legal intake in Microsoft Teams and agentic search across Microsoft 365 - Legora Legora · 2026-11-16T13:00:00+00:00
- Legora launches Intake: an agentic front door for in-house legal teams - Legora legora.com
- Manage Copilot for legal - Microsoft 365 admin | Microsoft Learn learn.microsoft.com