Skip to content
English - United Kingdom
  • There are no suggestions because the search field is empty.

Using the Konquest MCP Server with Microsoft 365 Copilot

The Konquest MCP server connects your Konquest account directly to Microsoft 365 Copilot, letting you query placements, manage users, and interact with your data through natural language. This article walks through how to set up the connection using Microsoft Copilot Studio.

Overview

The Konquest MCP server allows you to interact with your Konquest account directly through Microsoft 365 Copilot, using natural language. Rather than calling the API manually, you can describe what you want to do and Copilot will handle the rest.

This is done by creating an agent in Microsoft Copilot Studio and connecting it to the Konquest MCP server. Once published, the agent is available directly inside M365 Copilot.

This guide has been tested with Microsoft 365 Copilot via Copilot Studio.


Setting Up the Connection

Step 1: Create an Agent in Copilot Studio

Sign in to Copilot Studio and select Create > New agent. Give the agent a name, for example Konquest Assistant.

Inside the agent, select Add a tool and choose MCP connector.

Enter the following details:

  • URL: https://mcp.konquest.io/mcp

When prompted to configure authentication, select OAuth 2.0 then select Manual and enter the following:

Field Value
Identity Provider Generic OAuth 2
Client ID SHbYiiQcjZYXYAaerp08sXIAK7sV6QmI
Client Secret (contact Konquest support)
Authorization URL https://auth.konquest.io/authorize
Token URL https://auth.konquest.io/oauth/token
Refresh URL https://auth.konquest.io/oauth/token
Scope openid profile offline_access

OAuth 2.0 configuration for Konquest MCP.


Step 2: Send Your Redirect URL to Konquest

After saving the tool configuration, Copilot Studio will display a Redirect URL. It will look similar to:

https://global.consent.azure-apim.net/redirect/...

Copy this URL and send it to support@konquest.io. Konquest needs to register it before the OAuth connection can complete. They will confirm once it has been added.


Step 3: Create a Connection

Once Konquest has registered your redirect URL, return to Copilot Studio and complete the connection:

  1. Go back to the MCP tool in your agent
  2. Select Create new connection
  3. A sign-in window will appear — authenticate with your Konquest credentials
  4. Once authenticated, Copilot Studio will perform the MCP handshake and automatically discover all available Konquest tools

Step 4: Publish the Agent to M365 Copilot

Once the connection is confirmed:

  1. Click Publish in Copilot Studio
  2. Go to the agent's Channels settings and enable the Microsoft 365 Copilot channel
  3. To roll out to your organisation, deploy via the Microsoft 365 Admin Center or Teams Admin Center, selecting the users or groups who should have access

Users will find the agent available within M365 Copilot and can start interacting with Konquest data straight away.


Available Tools

The available tools are the same as those exposed through the Konquest MCP server. See the Using the Konquest MCP Server with Claude article for the full tool list and descriptions.


Tips

  • Your permissions apply. Because Copilot acts as your authenticated Konquest user, it can only perform actions you could carry out yourself through the Konquest UI.
  • Each user authenticates individually. The OAuth connection is per-user — each person will be prompted to sign in to Konquest the first time they use the agent.
  • One redirect URL per Copilot Studio instance. If multiple users in your organisation are setting up the connector, each will need their redirect URL registered with Konquest separately.

Further Support

For questions about the MCP server or to report issues, contact: support@konquest.io