Microsoft 365 Copilot · Custom federated connector
Connect Copilot to
your company data.
Without the guesses.
Microsoft 365 Copilot reads email, Teams and SharePoint well, but it cannot see reconciled figures across your finance, CRM and project systems. The Company Twin sits underneath Copilot and Claude as a governed knowledge graph, answering cross-system questions in under a second with source links and role-based permissions.
One question across finance, CRM and delivery.
Ask inside Copilot Chat, Word, Excel, PowerPoint or Outlook. Copilot calls your Company Twin over MCP, and the Twin's model-free graph engine returns pre-computed figures with provenance.
Asked
“What does Northgate Retail owe us right now, and which projects are still open?”
Calculated from reconciled ledger, CRM and project records. The same figures return identically in Copilot, Teams and Claude.
- Current overdue balance
- £48,620.00
4 invoices · Ledger synced 12 mins ago
- Open delivery projects
- 3 active (1 at risk)
CRM + delivery tracker · Joined by client entity
- Unbilled work in progress
- £19,400.00
Time & milestones · Agreed WIP definition v2
Why raw Copilot connectors are not enough.
Plugging Copilot straight into raw APIs still leaves a language model guessing joins, calculating totals on the fly and missing legacy systems. A governed knowledge graph does that work ahead of time.
Asked the same question, Copilot says £51,300? and Claude says £46,975? A language model matches the names and adds up the rows, each time it is asked. Reached: Xero, HubSpot, Asana. Not reached: SunSystems, Google Sheets.
Two tools, two answers, and nobody can say which is right.
Asked the same question, Copilot and Claude both say £48,620.00. The Company Twin holds reconciled entity links, figures pre-computed by the Rust graph engine and one role model for every tool, over Xero, HubSpot, Asana, SunSystems, Google Sheets.
One figure in both, with its sources and the time it was read.
01Cross-system joins
Raw Copilot connectors: Copilot searches each connector separately and guesses how client names match across CRM, ERP and projects.
Company Twin governed knowledge graph: Records are linked across systems ahead of time into one entity graph, with source links back to every record.
02Numbers & arithmetic
Raw Copilot connectors: The language model pulls raw rows and estimates totals, often giving different answers to the same question.
Company Twin governed knowledge graph: Pre-computed in a deterministic, model-free Rust graph engine using your agreed business definitions.
03Legacy IT & spreadsheets
Raw Copilot connectors: Depends on clean cloud SaaS APIs; older ERPs (such as SunSystems or Dynamics GP) and spreadsheets stay invisible.
Company Twin governed knowledge graph: Connects legacy ERPs, SOAP/SQL databases and operational spreadsheets into one clean read-only surface.
04Copilot + Claude governance
Raw Copilot connectors: Each AI tool gets separate credentials and uneven access rules across the organisation.
Company Twin governed knowledge graph: One granular role-based permission model persists across Microsoft 365 Copilot, Teams, Slack and Claude.
05Uncovered questions
Raw Copilot connectors: Falls back to searching stale documents and extrapolating an answer.
Company Twin governed knowledge graph: Refuses clearly when a figure is outside coverage or caller permissions, and names the nearest covered metric.
One governed knowledge graph underneath every AI tool.
Your Company Twin runs a model-free Rust graph engine over your connected systems, so every figure is calculated once, checked against source reports, and governed by each person's role.
| Records | Account manager | Finance director |
|---|---|---|
| Reads | Reads | |
| Reads | Reads | |
| Reads | Reads | |
| Blocked | Reads | |
| Blocked | Reads |
- Same question, same number
- The engine follows your definitions and uses no AI model, so the figure stays identical across Microsoft 365 Copilot, Teams, Slack, Claude, ChatGPT, the web app and Twin for Mac until the underlying records change.
- Answers in milliseconds
- It holds your connected records and agreed definitions in memory, so a question across several systems doesn’t have to wait on each of them.
- Every figure traces back
- Each result comes with what was counted and how, right down to the invoices, bookings or tasks behind it.
- Each person’s own view
- It reads only the records the person asking is allowed to see, so a total never includes a row they couldn’t open.
01
Built for real mid-market IT estates
Whether your finance runs on SunSystems, Dynamics GP, Xero, NetSuite or operational spreadsheets, we wire the connections read-only and build your governed knowledge graph in days.
02
Same truth in Copilot and Claude
Many UK organisations roll out Copilot broadly across operating teams while leadership or investors work in Claude. Both connect to the same Company Twin and return identical figures.
03
Granular permissions that persist everywhere
Expose sales invoices to account managers while keeping payroll restricted to finance. Role groups stay enforced whether a person asks in Copilot, Teams, Slack or Claude.
Live in a staged rollout in two focused weeks.
Connect the Twin as a Microsoft 365 Copilot custom federated connector over OAuth 2.1 with PKCE, or run the Teams agent alongside it for colleagues without Copilot licences.
01 · Mercury Labs + finance lead
Connect systems & agree definitions
We connect 2 to 3 core systems read-only, reconcile entities into your knowledge graph, and verify figures against your source reports.
02 · Your Microsoft 365 admin
Register the federated MCP connector
Register our dedicated tenant OAuth client in the Teams Developer Portal (PKCE required) and add https://twins.mlx.systems/mcp/graph in the M365 admin center.
03 · IT + pilot group
Staged rollout to 5 pilot users
Enable the connector for an initial Copilot-licensed group via M365 staged rollout, verify live cross-system answers, then expand across the business.
Same governed knowledge graph on every surface.
Start where your team already works today. Add other AI tools later without rebuilding definitions or permissions.
Questions IT and finance teams ask first.
Straight answers on connectors, licences, permissions and setup.
Through Microsoft's custom federated connector (Connect to MCP server) pointing to your Twin's focused /mcp/graph endpoint using OAuth 2.1 with PKCE. Ten read and query tools work across Copilot Chat, Word, Excel, PowerPoint, Outlook and Researcher.
Give Copilot the company data it cannot see.
Show us one cross-system question your team chases every week. We will run a live 20-minute walkthrough in Copilot and Claude, then scope a two-week staged rollout.
