Zamino
Integrations
Help center
Get started, connect sources, FAQs.
Changelog
Every update we ship.
Customers
How real teams use Zamino.
Security & trust
Encrypted · access-controlled · audited.
Contact & support
Talk to a human.
What’s new
Nov 02QuickBooks Live is now GAOct 24AI budgets now apply per-team
Pricing
Log InSign Up for Free

Connecting Microsoft 365 Copilot to Zamino

A guide for your IT admin: add Zamino as a custom federated connector so everyone with a Copilot license can ask questions about your business data in Copilot Chat.

Connect your AI6 min read

Microsoft 365 Copilot can connect to Zamino through a custom federated connector — Microsoft's mechanism for bringing external data into Copilot Chat in real time. Unlike ChatGPT or Claude, this is set up once by your Microsoft 365 admin for the whole organization; individual users then just sign in.

Federated connectors are read-only by design, which matches Zamino exactly: Copilot can query your data through safe, bounded tools — it can never change anything.

What the admin will need

  • Microsoft 365 Copilot licenses for the users who'll ask questions.
  • Global Administrator or AI Administrator role in the Microsoft 365 admin center, plus access to the Teams Developer Portal.
  • OAuth credentials from Zamino — see Step 1.
  • Each user needs a Zamino account (with data sources connected) in your Zamino organization.

Step-by-step setup (admin)

  1. Request OAuth credentials from Zamino

    Microsoft's connector registration needs a pre-registered OAuth client — email support@zamino.com with the subject "M365 Copilot OAuth credentials" and we'll send you:

    • Client ID and Client secret
    • Authorization, token, and refresh endpoint URLs
    • The scopes to enter (openid profile email offline_access)

    We register Microsoft's redirect URI (https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect) on our side before sending them.

  2. Register the OAuth client in the Teams Developer Portal

    In the Teams Developer Portal, go to Tools → OAuth Client Registration → + New OAuth connection and enter:

    • Name: Zamino
    • Client ID / Client secret: from Step 1
    • Authorization / Token / Refresh endpoints: from Step 1
    • Scopes: openid profile email offline_access
    • Enable Proof Key for Code Exchange (PKCE) — Zamino supports it

    Save, then copy the OAuth client registration ID it generates.

  3. Create the connector in the Microsoft 365 admin center

    In the admin center, go to Copilot → Connectors → Gallery tab. Under Created by your org, select Create a new connector → Add, then under Connect to MCP server click Add and enter:

    • Display name: Zamino
    • Base URL: https://api.zamino.com/mcp
    • Registration ID: the OAuth registration ID from Step 2

    Save. Changes can take up to 15 minutes to take effect.

  4. Roll it out

    From Your Connections, use Staged rollout to release Zamino to a test group first, then Deploy to all users when you're happy.

What each user does (once)

  1. In Copilot Chat, use the Zamino connector for the first time — Copilot prompts you to sign in.
  2. Sign in with the same email as your Zamino account (first time: set a password for external AI access and verify your email).
  3. Open app.zamino.com → Settings → External AI Access → Approve the pending request. This explicit approval is a Zamino security feature — no AI gets your data without it.
  4. Ask away: "What were our top 5 expense categories last quarter?"

Troubleshooting

A note on privacy

Query results flow into your organization's Microsoft 365 environment under your Microsoft agreements. Zamino sends nothing on its own — data moves only when a signed-in, approved user asks a question, and every query is logged in Zamino's audit trail. Users can revoke their own access any time in Settings → External AI Access.

Where to go next

All help articlesDidn’t answer your question?