Skip to content

Microsoft Copilot

Microsoft Copilot (formerly Microsoft 365 Copilot) reaches Elaichi through a Copilot Studio agent. A maker adds Elaichi to the agent once as a tool and publishes the agent. After that, each person who uses the agent signs in to Elaichi as themselves, and every app your organization connected in Elaichi, and every tool they are allowed to use, is available from Microsoft Copilot. Microsoft Copilot is one example of an AI client. Other clients use the same Elaichi endpoint.

Where to find the endpoint: in the Elaichi web app, choose Connect in the sidebar, then copy the endpoint shown in Connect your AI client.

How Elaichi connects to AI clients explains the parts that are the same for every client: one connection, one consent screen and your own access. This page covers only the Microsoft Copilot steps.

Before you start

Requirement Detail
Copilot Studio Permission to create and edit agents in a Copilot Studio environment.
Microsoft Copilot The people who will use the agent can use Microsoft Copilot.
Where it applies Per agent. Everyone the agent is shared with can use it, and each person signs in to Elaichi separately.
Elaichi account The same sign-in you use for the Elaichi web app, for the maker and for each user.
Your organization's policy Power Platform data policies also govern MCP tools in Copilot Studio, and your Teams admin decides whether Power Platform apps can be added to Teams.

Add Elaichi to a Copilot Studio agent

These steps match Microsoft Learn as of October 2026. Menu names can change.

  1. In Copilot Studio, open your agent and go to its Tools page.
  2. Select Add a tool, then New tool, then Model Context Protocol. The MCP onboarding wizard opens.
  3. Set Server name to Elaichi, write a short Server description (for example, "Tools for our company's connected apps"), and paste the endpoint as the Server URL.
  4. Under authentication, choose OAuth 2.0, then Dynamic discovery. Select Create, then Next.
  5. In Add tool, select Create a new connection. Elaichi's sign-in and consent screen opens. Pick your organization, choose what the agent may do, choose the tools, then select Allow access.
  6. Select Add to agent.
  7. Keep the tool's authentication on end-user credentials, not maker-provided credentials. Then each person signs in to Elaichi as themselves, and Elaichi applies their own access.

The endpoint is the only value you enter:

https://api.elaichi.ai/mcp
Info

Do not use API key, Dynamic or Manual OAuth, and do not enter a client ID or secret. Elaichi supports dynamic client registration with discovery, so Dynamic discovery finds and registers everything itself.

The consent screen shows the name that Copilot Studio registered for itself. Elaichi does not show a verified mark for it, so check that you started this sign-in from Copilot Studio yourself before you allow access.

On the consent screen, for most use, keep Read your organization's data and Run your connected tools ticked. Approve what the client can do explains each scope.

Publish the agent to Microsoft Copilot

  1. Publish the agent at least once.
  2. On the top menu bar, select Channels, then the Teams and Microsoft Copilot tile.
  3. Under Turn on Microsoft 365, keep Make agent available in Microsoft Copilot selected. Without it, the agent is only in Teams.
  4. Select Add channel.
  5. To use it yourself, select See agent in Teams, then Add. To give it to others, share the agent with them, or submit it for admin approval from Availability options.

In Microsoft Copilot, type @, pick your agent, and ask your question. The first time someone uses an Elaichi tool, they are asked to sign in to Elaichi and approve access.

Connect your first app

Ask the agent in Microsoft Copilot. It is the same prompt the Connect your AI client dialog gives you. It confirms the connection and helps you connect an app.

Elaichi is connected. List the Elaichi tools you have, then help me connect my first app. If a sign-in comes up, stop and tell me. I approve the access myself.

The last two sentences matter. A model cannot grant itself access to Elaichi, so you must approve each sign-in yourself. Without those sentences, a client can report success while a sign-in waits unanswered.

You connect the app itself in Elaichi, not in Copilot Studio. See Connect an account. Once an app is connected, it appears in the agent with no change to the tool.

What to know

  • One agent, many people. The maker sets up the tool once. Each user signs in to Elaichi on first use and sees only what their own Elaichi access allows.
  • Name Elaichi in your question. The agent may answer without calling Elaichi. Say "use Elaichi to list my open GitHub issues" so it makes the call.
  • The server description matters. The agent uses it to decide when to call Elaichi. Name the kinds of apps and tasks your team uses Elaichi for.
  • To disconnect, remove the tool from the agent, or revoke the grant in Settings → Connected apps in Elaichi. Revoking stops the token working immediately.
  • If you disconnect an app in Elaichi, it also disappears from the agent.

Troubleshooting

Symptom Likely cause
The tool cannot be added, or is blocked A Power Platform data policy blocks the connector. Ask your Power Platform admin.
The agent does not appear in Microsoft Copilot Make agent available in Microsoft Copilot was not selected, or the agent was not published after you added the channel. Teams can also cache apps for a while.
Everyone acts as the maker The tool uses maker-provided credentials. Switch it to end-user credentials.
No tools appear after you sign in No app is connected in Elaichi yet, or no toolbox you can reach has tools. Connect an app first.
A tool you expect is missing A restriction blocks it, or it is not in a toolbox you can reach. Connected tools are never listed, so ask the agent to search for the tool by name.
A call is refused after consent You did not grant the scope the call needs. Connect again and tick that scope.