TwinDocs
Connect your tools & AI

Microsoft Teams & Microsoft 365 Copilot

Use your Twin natively inside Microsoft Teams chats, channels, and Microsoft 365 Copilot with your Microsoft Entra sign-in.

For organisations running on Microsoft 365, your Twin appears directly as an agent inside Microsoft Teams and Microsoft 365 Copilot, so finance, operations, and client teams can ask governed company questions without switching out of Teams, Word, Outlook, or Copilot Chat.

FinanceGeneral
PA
Priya Anand · 09:12
Twin what is overdue over 30 days?
Twin · 09:12
£48.2k is overdue by more than 30 days, across 7 invoices. The largest is Kestrel Freight: INV-1049, £9,641.17, 41 days late.
Graph verified · Xero read today at 09:00
Open Receivables in Twin
Microsoft 365 Copilot
What is overdue over 30 days?
Your Twin agent
£48.2k is overdue by more than 30 days, across 7 invoices. The largest is Kestrel Freight: INV-1049, £9,641.17, 41 days late.
Graph verified · Xero read today at 09:00Open Receivables in Twin
Illustrations of the Twin answering in a Teams channel and as an agent in Microsoft 365 Copilot, with made-up data. Both give the same figure and a link back to the Twin.

How it works

  1. One Microsoft sign-in: Your Microsoft Entra (Azure AD) identity maps straight to your Twin organisation and role, with no separate password or pasted token.
  2. Same Twin Graph, same certified numbers: Questions asked in Teams or Microsoft 365 Copilot run against your organisation's live Twin Graph. Arithmetic runs in deterministic code, and replies include source freshness, definition versions, and authenticated links back to the web app.
  3. Clear refusals over guesses: If you ask for a figure your Twin doesn't cover, or data outside your access, it states that boundary clearly instead of letting Copilot guess from stale documents.

Where teams use it

SurfaceBest for
Microsoft Teams channels & threadsChecking client status, overdue receivables, or project blockers together with your team in the thread
Microsoft Teams 1:1 chatQuick pre-meeting lookups on a customer, supplier, or contract before joining a Teams call
Microsoft 365 CopilotPulling certified Twin Graph figures and Thing summaries into executive briefings, packs, and daily Copilot workflows

Starter prompts for Teams & Copilot

Pre-meeting client check in Teams

Give me a pre-call briefing on [Customer Name] from our Twin: invoiced revenue over the last 12 complete months, current overdue balance, active projects, and open decisions.

Teams · 365 Copilot. Pulls the unified Thing page across finance, CRM, and delivery.

Monthly variance check in Copilot

Using our Twin's agreed finance definitions, compare last complete month's revenue and overdue receivables against the prior month, separate currencies, and list the source sync timestamps.

Microsoft 365 Copilot. Uses your Twin's agreed definitions and complete-period rules.

Two ways to connect

RouteWhere it worksLicence neededBest for
Custom federated connector (MCP)Copilot Chat, Agents, Word, Excel, PowerPoint, Outlook, and ResearcherMicrosoft 365 Copilot licence per userLetting Copilot's own model call your Twin's governed knowledge graph directly across every Microsoft 365 app
Twin agent for Teams & CopilotMicrosoft Teams channels, threads, 1:1 chat, and CopilotMicrosoft Teams (works without a Copilot licence for every user)Rolling out governed company answers across the whole team in Teams alongside Copilot users

Both routes read the same Twin Graph, apply the same agreed definitions, and enforce the same user permissions.

Connect as a custom federated connector (MCP)

A Microsoft 365 Copilot custom federated connector connects your Microsoft 365 tenant directly to your Twin's governed knowledge graph at https://twins.mlx.systems/mcp/graph.

  • Ten focused read and query tools: five read your organisation's graph; two look up a customer, project, or person across systems; one lists what falls on a given day; one runs a typed deterministic query; one lists the caller's own sessions. No tool changes records.
  • Sign-in and permissions: each person signs in once with OAuth 2.1 + PKCE and sees only the records their Twin role allows.
  • Works alongside Teams: nothing extra is installed in Teams, and the existing Teams agent is unaffected.

Prerequisites

  • A Microsoft 365 administrator with Global Administrator or AI Administrator access and access to the Teams Developer Portal
  • A Microsoft 365 Copilot licence for each user who will use the federated connector
  • An active Twin organisation with your users added

Guided setup (5 steps)

  1. Request your tenant OAuth client from Mercury Labs: your Mercury Labs implementation engineer registers a dedicated confidential OAuth client for your organisation (using Microsoft's redirect URI https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect with PKCE required and read/query scopes only) and shares your Client ID and secret securely.
  2. Register OAuth in the Teams Developer Portal: open https://dev.teams.microsoft.com/tools, choose Tools › OAuth client registration › Register client, and configure:
    • Registration name: Company Twin
    • Base URL: https://twins.mlx.systems/mcp/graph
    • Restrict usage by org: My organization only
    • Restrict usage by app: Any Teams app
    • Authorization endpoint: https://mlx.systems/auth/authorize
    • Token & Refresh endpoints: https://mlx.systems/auth/token
    • Scope: openid offline_access mlx_tenant twin.query twin.read
    • Proof Key for Code Exchange (PKCE): On (required)
    • Save and copy the OAuth client registration ID.
  3. Create the custom federated connector: in the Microsoft 365 admin center, go to Copilot › Connectors › Gallery › Create a new connector › Custom connector › Connect to MCP server, enter display name Twin, base URL https://twins.mlx.systems/mcp/graph, and your OAuth client registration ID.
  4. Run a staged rollout: under Your connections, open Twin and start a staged rollout to 5–10 pilot users before deploying to all Copilot-licensed groups.
  5. Connect and verify: in Microsoft 365 Copilot Chat, each pilot user opens Settings › Sources, connects Twin, signs in once, and verifies with a cross-system question such as "What does [Customer Name] owe us right now, and which projects are still open?"

Need a walkthrough or your tenant OAuth client registered? Book a Copilot setup session.

Rollout for the Teams & Copilot agent

Your organisation administrator or implementation engineer turns on the Teams and Microsoft 365 Copilot agent package for your tenant and confirms Microsoft Entra group access. Once it's published in the Microsoft 365 admin centre, permitted users can pin the Twin agent in Teams and Copilot straight away.

On this page