Connect Microsoft Copilot to your company knowledge base

Before you start

• Applies to. Dienox works in Microsoft Copilot through Copilot Studio. Microsoft 365 Copilot additionally needs an agent that your IT team publishes.
• Role. Someone with rights in your Copilot Studio environment does this once.
• Plans. See Microsoft's page.
• How it connects. Microsoft's documentation describes an onboarding wizard for connecting an agent to an existing MCP server, with three ways to sign in: none, an API key or OAuth 2.0. Dienox uses OAuth 2.0.
• In Dienox. You need an account in your organisation, and an administrator invites you. Dienox is in beta, so your organisation joins the beta first.

Last checked: 1 October 2026

Plans and menus change. Microsoft's own page on connecting an agent to an existing MCP server is leading.

The steps

1. In Copilot Studio, open the agent that should know your organisation.
2. Add a tool of the type Model Context Protocol to that agent.
3. Paste this address: https://dienox.com/mcp
4. Choose OAuth 2.0 with dynamic discovery. Copilot Studio then registers itself with Dienox.
5. Sign in to Dienox, pick your organisation and click Allow.

The agent can now read your knowledge base when a question needs it.

What you can ask now

Ask the agent what you would ask a colleague who has been there for years. It reads the knowledge base when the question needs it, and names the source.

• "Who owns the contract with this supplier?" The person and the role, from what your organisation wrote down about who owns what.
• "What did the board decide about the reorganisation?" The decision, when it was made and by whom, with the reasons behind it.
• "How do we handle a complaint from a key account?" The process as your organisation runs it, with the source under the answer.

For a whole team

Someone with rights in Copilot Studio adds Dienox to an agent once, with the steps above. Your people then ask that agent.

How the agent reaches your colleagues, and whether each of them signs in to Dienox, is set in Copilot Studio: see Microsoft's page. On our side the rule is the same whoever signs in. A connection works within the role of that person, in the one organisation they picked. A reader's connection only reads.

Microsoft 365 Copilot needs one thing more: an agent that your IT team publishes. That happens on Microsoft's side, and we do not describe those steps here. See Microsoft's documentation.

If it does not work

• You cannot add a tool to the agent. You need rights in your Copilot Studio environment. Ask whoever manages it.
• Dienox does not show up in Microsoft 365 Copilot. The steps here cover Copilot Studio. Microsoft 365 Copilot additionally needs an agent that your IT team publishes.
• Your organisation is not offered when you sign in. You need your own account in that organisation on Dienox. Ask an administrator there to invite you.
• Every connection is refused. An administrator of your organisation has switched AI access off in Dienox, and can switch it on again.

The same knowledge in your other tools

Whatever you connect next reads the same knowledge base. What was settled in a chat here is there in the next tool, for you and for your colleagues.

• Connect Claude. As a custom connector, on the web and in the desktop app.
• Connect ChatGPT. As a custom app, published once for a whole workspace.
• Connect Cursor. As an MCP server, with a personal token.

Every tool side by side: connect your AI tools to your company knowledge. What the address you add does, and what it cannot do: the Dienox MCP server.

Questions people ask