Skip to main content

Connecting Microsoft 365 Copilot to the OneIQ MCP

How to add the OneIQ MCP server to a Copilot Studio agent and publish it to Microsoft 365 Copilot.

Written by Omega Team

Microsoft 365 Copilot doesn't accept a custom MCP server directly. Instead, you add OneIQ as a tool in a Copilot Studio agent, then publish that agent to Microsoft 365 Copilot.

Before you start

  • A Copilot Studio licence (or an active trial) and maker permissions in your Power Platform environment

  • A Microsoft 365 Copilot licence, if you want the agent to appear in Copilot chat

Create an agent and add the OneIQ MCP server as a tool

  1. Log into copilotstudio.com and switch to the classic experience.
    ​

    AI generated image
  2. On the Home screen, under Start building from scratch, click Agent.

  3. Enter a name for the agent (e.g. OneIQ) and click Create. Before continuing, wait for the message Your agent has been provisioned to appear.

  4. Once your agent has been provisioned, click Edit and enter a Description for your agent, such as the following below, then click Save:
    ​
    ​Ask Copilot about your VMs, hosts, storage, cloud costs and sizing, answered live from your OneIQ data
    ​

  5. Click the Tools tab, then + Add a tool, then select Model Context Protocol
    ​

  6. Enter a Server name (e.g. "OneIQ") and a short Server description.

  7. Enter https://mcp.oneiq.com as the Server URL.

  8. Set Authentication to OAuth 2.0, then choose Dynamic discovery.

  9. Click Create (this can take a few minutes).
    ​

  10. On the Add tool dialog, open the drop-down next to Connection and select Create a new connection.
    ​

  11. Enter a Display name for the connection, then click Create.
    Creating the connection redirects you to OneIQ to log in and authorize access, the same flow as Claude and ChatGPT (see What happens next (all plans)). Click Allow to finish connecting, and keep Maintain access to your account so it can continue working even when you're not using it checked if desired.​
    Then click Add and configure. You should now be back under the Tools tab.
    ​

  12. Under Details, expand Additional details and make sure Credentials to use is set to End user credentials.
    ​

  13. Go back to the Overview tab, click Edit in the Instructions section, enter the following, and then click Save:
    ​

    Role and goal:
    ​You are an internal OneIQ assistant that helps users query and act on OneIQ data and systems exclusively through the OneIQ tool connected to this agent. Your only source of information and actions is that MCP connection. You have no other knowledge source, browsing ability, or tool.
    ​

    Scope:
    ​In scope: any request that can be answered or fulfilled by calling the OneIQ tool (e.g., looking up OneIQ data, running supported OneIQ actions or queries exposed via that server).


    ​Out of scope: general knowledge questions, requests unrelated to OneIQ, and anything that would require a tool, connector, or data source other than OneIQ. If a request falls outside this scope, say so plainly and do not attempt to answer from general knowledge.
    ​

    Tone and response style:
    ​Be concise, professional, and clear. Avoid speculation. If OneIQ doesn't return the information needed, say that rather than guessing.
    ​

    When to ask questions, use knowledge, or take actions:

    Ask a clarifying follow-up if the user's request is missing details the OneIQ tool needs to run (e.g., a required ID, name, or date range).
    ​

    Always route data lookups and actions through OneIQ. Never fabricate results.


    ​If OneIQ returns an error or no data, tell the user what happened and suggest they verify inputs or contact support if the issue persists.


    ​If a request requires elevated permissions or an action outside what OneIQ exposes, direct the user to the appropriate OneIQ contact rather than attempting a workaround.
    ​

Publish to Microsoft 365 Copilot

  1. Click on Publish in the top right corner. In the Publish this agent window, make sure Force newest version is checked and click Publish. (This could take a few minutes to complete)

  2. Click the Channels tab, then under Microsoft channels, click Microsoft 365 and Teams.

  3. Under Turn on Microsoft 365, make sure Make agent available in Microsoft 365 Copilot is checked.

  4. Click Add channel.

  5. Next under Agent preview, you should now be able to click on See agent in Microsoft 365. This launches Microsoft 365 Copilot in the browser.
    ​

  6. The agent window in Microsoft 365 Copilot should now appear. Click Add to add your new agent to Microsoft 365 Copilot.

  7. Go back to the copilotstudio.com browser window with your agent and click Publish in the top right corner. In the Publish this agent window, make sure Force newest version is checked and click Publish. (This could take a few minutes to complete)

  8. Switch back to the Microsoft 365 Copilot browser window and ask:
    Can you query the OneIQ MCP?

    At this point you may see the message "Let's get you connected first, and then I can find that info for you. Open connection manager to verify your credentials. Once the connection is ready, retry your request."
    ​

    Note: Do not click Retry yet.
    ​

    Click Open connection manager to go to the Manage your connections window. Click Connect, then click Submit.
    ​


    ​

  9. Switch back to the Microsoft 365 Copilot browser window and click Retry (a browser refresh may be required). Microsoft 365 Copilot should now be able to query the OneIQ MCP.


Troubleshooting

The OneIQ tool was added, but Copilot never uses it

Copilot Studio agents only call a tool when the request clearly matches it. Try naming OneIQ explicitly in your prompt, and check that the Server description you entered explains what OneIQ does.
​

The connection fails or the tool returns an error

MCP servers in Copilot Studio run through Power Platform custom connectors, so your organization's data loss prevention policies apply. Ask your Power Platform administrator to confirm the OneIQ connector isn't in a blocked group in the Power Platform admin center.

Did this answer your question?