Skip to main content
Connect Case.dev to Microsoft 365 Copilot so teams can create matters, search vaults, run OCR, and launch legal workflows from the Microsoft 365 tools they already use.
Microsoft 365 Copilot setup usually happens through an IT or platform team. Start in a test tenant, confirm sign-in and tool access, then roll it out more broadly.
Use Microsoft 365 Agents Toolkit or Copilot Studio to connect Case.dev as an action source for your Copilot agent.
Remote MCP endpoint
https://api.case.dev/mcp

​
High-level setup

  1. Create a new Declarative Agent in Microsoft 365 Agents Toolkit.
  2. Choose Add an Action and start with an existing MCP server.
  3. Enter https://api.case.dev/mcp.
  4. Fetch the available operations and choose the actions you want to make available.
  5. Configure authentication for the agent.
  6. Provision and sideload the agent into your Microsoft 365 tenant.
  7. Enable the agent for the users or groups who should have Case.dev access.

​
Authentication

Case.dev supports the OAuth authorization-code flow used by Microsoft Copilot integrations. For the smoothest rollout:
  • Use discovery-based OAuth when your Copilot environment supports it.
  • Test sign-in and approval in a development tenant first.
  • Start with the most important actions, then expand from there.

​
First workflow to try

Start with a simple matter intake workflow:
  1. Create a matter named Johnson v. Acme Corp.
  2. Upload the attached complaint into the matter vault.
  3. Create a work item that extracts parties, claims, deadlines, and requested relief.
  4. Check the work item until it completes.
  5. Return the result and link the output object.

​
Example prompts

  • Open a new matter for Johnson v. Acme Corp and give me a case kickoff checklist.
  • Search the matter vault for every document mentioning indemnification.
  • Run OCR on this scanned filing set and summarize the result.
  • Create a work item to draft a deposition outline from the uploaded exhibits.

​
Troubleshooting

Reduce the number of actions in the first version of the agent, then add more once the package is working.
Verify that your Copilot environment is using the OAuth authorization-code flow and that the final redirect stays on a Microsoft-owned callback domain.
Rebuild the package with a narrower set of actions so the first release stays focused and easy to validate.

MCP Reference

See the Case.dev MCP endpoint and the tools available in Copilot.

Matters

Learn how matters work before you add matter creation and editing actions.