Connect Microsoft Copilot to Beeye
Add Beeye as a tool to a Microsoft Copilot Studio agent, then ask about your schedule, budgets and people. The agent reads your Beeye data with your access rights and writes the answer. It cannot change anything in Beeye.
Before you start
- Copilot Studio
Access to Microsoft Copilot Studio and a Beeye user.
- Your Beeye API key
In Beeye, click your profile photo, open Informations and click Copy. No key? Ask your Beeye administrator or your Customer Success Manager.
- Your server address
- Europe
https://mcp.eu.mybeeye.com/mcp - Canada
https://mcp.ca.mybeeye.com/mcp - United States
https://mcp.us.mybeeye.com/mcpFrom January 1, 2027
- Europe
- Your Power Platform data policy
Copilot Studio connects to MCP servers through Power Platform connectors. If a data policy blocks custom connectors, ask your Power Platform administrator to allow the Beeye connector.
- Approval
Your IT or security team approves Copilot Studio for Beeye data.
Set it up
- Open Copilot Studio. In the left menu, click Agents.
- Open your agent, or create a new one.
- On the Build tab, find the panel on the right. In Model, select a tested model (see below).
- Next to Tools, click +. In the Add a tool window, click Model Context Protocol (MCP), then + Add.
- Type the name
Beeyeand the description: “Beeye resource planning data: projects, budgets, resources, capacity and conflicts.” - In Server URL, paste your region’s server address.
- In Authentication, select API key. In Parameter type, select Header. In Header name, type
X-BEEYE-API-KEY. - In Key value, paste your API key, then click Add.
- Recommended: in the agent’s Instructions, paste “You answer questions about Beeye resource planning data. Use the Beeye tools for every answer. Do not guess numbers. If the Beeye tools return no data, say so.” In Knowledge, remove Search all websites, so answers come only from Beeye.
Check the connection
Click the Preview tab and ask: “Am I connected to Beeye?” The agent replies with your name and your firm.
Five questions to start
- “Who is overloaded next week, and on which jobs?”
- “Which jobs will go over budget before the end of the fiscal year?”
- “Give me the close-out summary for Aster & Co.: hours, fees and variance to budget.”
- “Who is free in January and has already worked on this client’s audit?”
- “Show utilization by team over the last 3 months, with the 5 jobs most over budget.”
Models and good answers
Beeye tested the connector with Claude Opus 5 and Claude Opus 5.5 in Copilot Studio. Other models can give wrong or incomplete answers. Want to use another model? Tell your Customer Success Manager: Beeye can test it with you.
- Give dates: “next week”, “December 2026”.
- Use the exact names of jobs, clients and teams. Say “my jobs” for the jobs you manage.
- If an answer is slow or incomplete, ask for a shorter period or one team.
- Start a new conversation for a new topic: in long ones, the model can mix up details.
- Check important numbers in Beeye before you make a decision.
Troubleshooting
| Problem | What to do |
|---|---|
| The agent cannot connect | Check the server address for your region, that the header name is X-BEEYE-API-KEY and that the key has no spaces. |
| The agent says the API key is not valid | Copy the key again from your Beeye profile. If it still fails, contact your Customer Success Manager. |
| The agent shows data you did not expect | The agent uses the access rights of the key’s owner. Check that it uses your own key. |
| The MCP option is missing in Copilot Studio | A Power Platform data policy blocks it. Contact your Power Platform administrator. |
| Answers are slow or stop | The request is too large. Ask for a shorter period or a smaller group. |
| A “too many requests” error | Each key can send 60 requests per minute. Wait one minute, then try again. |
Security and your responsibility
- Read-only
The agent cannot create, change or delete anything in Beeye. If it says it changed something, that statement is wrong.
- Your access rights
The agent sees only what your Beeye user can already see.
- A personal key
Your API key is personal: never share it, and never send it by email or in a ticket. If you think someone has it, contact your Customer Success Manager. Beeye revokes it; it can keep working for up to 5 minutes.
- Answers can be wrong
Beeye returns accurate data, but the model writes the answer. It can invent numbers, names or dates, or misread a vague question. Check key numbers in Beeye.
- Usage and cost
One question can make several calls to Beeye and send a lot of data to the model. Copilot Studio bills by usage, so large questions cost more. Ask your Microsoft administrator about your usage limits.
- Your firm’s responsibility
Beeye controls the MCP server, not your Copilot Studio agent. Your firm decides how your Copilot Studio agent is used with Beeye data: the provider’s data, privacy and retention settings, who can see conversations, your policies and the laws that apply, such as GDPR.
Who to contact
| Topic | Contact |
|---|---|
| API key, server, wrong data in Beeye | Your Customer Success Manager |
| Approval to use the assistant with Beeye data | Your IT or security team |
| Copilot Studio licenses, data policies, publishing to Teams | Your Microsoft 365 or Power Platform administrator |
| A wrong answer while the data in Beeye is right | No ticket needed: ask again with more detail, or use a tested model |
When you contact Beeye, give the assistant, the model, the question, and the date and time. Never send your API key.
Other guides
- ClaudeClaude Desktop, Mac and Windows · about 15 minutes
- Other assistantsany assistant that supports MCP · a few minutes
Back to AI connectors: what the assistant can do, governance and FAQ.