Connect Microsoft Copilot

Make Zahlenwerk available in Microsoft 365 Copilot and Teams through Copilot Studio.

Preview

The Microsoft Copilot connection is new. If something doesn't work as described, send us a short note of what Copilot shows. That helps us more than a screenshot of the settings.

Unlike Claude, people don't set up the connector themselves. Your Microsoft 365 admin creates an agent with Zahlenwerk once in Copilot Studio and makes it available in Microsoft 365 Copilot and Teams. After that, each colleague signs in once with their own Zahlenwerk account the first time they use it. Copilot therefore only sees what that person may see in Zahlenwerk.

Requirements

Access to Copilot Studio with permission to publish agents (usually included with Microsoft 365 Copilot licences).
Power Platform data policies must not block custom connectors, because MCP servers run as connectors in Copilot Studio.
Everyone who uses Zahlenwerk in Copilot needs a Zahlenwerk account in the team.

Setup by the admin

Create an agent

Open Copilot Studio and create an agent, e.g. "Zahlenwerk". A short description is enough, for example: "Answers questions about our portfolio, reports and deadlines from Zahlenwerk."

Add the MCP server

In the agent, go to ToolsAdd a toolNew toolModel Context Protocol.

Server name: Zahlenwerk
Server description: "Portfolio, fund and LP reports, capital calls, tasks and directory of the family office platform Zahlenwerk." Copilot uses this text to decide when to ask Zahlenwerk.
Server URL:

https://app.zahlenwerk.studio/api/mcp

Choose OAuth 2.0 with the type Dynamic discovery, then Create. Copilot Studio finds the sign-in itself and registers with Zahlenwerk. You don't enter a client ID or secret.

Create the connection

Under Add tool, choose Create a new connection. Copilot Studio opens the Zahlenwerk sign-in. Sign in, approve the access, then Add to agent.

In the tool's settings, the connection should use each user's own credentials (end user credentials), not yours.

Choose tools (optional)

Copilot Studio lists every Zahlenwerk tool separately. Switch off what Copilot shouldn't do, for example every tool that changes data if Copilot should only read.

Test and publish

In the test pane, ask: "List my report collections in Zahlenwerk." If that works, publish the agent under ChannelsTeams and Microsoft 365 Copilot and make it available to the right people in the Microsoft 365 admin center.

First use

The first time someone uses it, Copilot shows a sign-in card. They sign in to Zahlenwerk, confirm with their second factor if their team requires one, and approve the access. The connection then stays in place; Copilot renews it on its own.

If Dynamic discovery fails (the sign-in window closes straight away or shows an error), create the server again and choose the type Dynamic with these addresses:

Authorization URL: https://app.zahlenwerk.studio/oauth/authorize
Token URL template: https://app.zahlenwerk.studio/oauth/token

For developers: declarative agent

If you build a declarative agent with the Microsoft 365 Agents Toolkit instead of Copilot Studio, choose Add an ActionStart with an MCP Server, enter the same URL and pick OAuth (with dynamic registration) as the sign-in.

What doesn't work in Copilot (yet)

Uploading documents: Copilot can't hand files to Zahlenwerk. Upload reports in the app; Copilot reads them afterwards.
Generated files: letters, dossiers and reports appear as a link, not as a preview.

Disconnecting

In Zahlenwerk, under SettingsMCPConnected apps, click Revoke next to Microsoft Copilot. That ends this person's access. For the whole organisation, the admin removes the agent in Copilot Studio or blocks it in the Microsoft 365 admin center.

On this page