Connect / Microsoft 365 Copilot

Connect Microsoft 365 Copilot to Telara

Telara is being prepared as a Microsoft 365 Copilot agent. Once the Microsoft marketplace package is published, employees will install it from Microsoft 365 and connect with their existing Telara account, with no API key or MCP URL to paste.

client_type: m365_copilot

The endpoint

Streamable HTTPhttps://api.telara.dev/v1/mcp

AuthOAuth 2.1 + PKCE with dynamic client registration

Rolling it out centrally

The Microsoft 365 app package is complete and ready for Marketplace submission. After Microsoft review, a customer administrator enables it for the intended users and each employee completes Telara OAuth once.

Microsoft Marketplace review validates the public Microsoft 365 Copilot offer and agent package.

A customer Microsoft 365 administrator enables the approved offer for the intended users or groups.

Employees install or select Telara in Microsoft 365 Copilot and complete their own OAuth consent, with no API key, MCP URL, or tenant identifier to paste.

Before you commit to this

Streamable HTTP is required, and Telara serves it

Copilot Studio will not accept an SSE-only server. Use https://api.telara.dev/v1/mcp, not the /sse endpoint. This trips people who followed a generic MCP setup guide that leads with SSE.

Public availability requires a Microsoft 365 app package

Microsoft’s public Copilot connector route is a Microsoft 365 app package with an agent connector, not a standalone connector-gallery entry. Telara’s offer is staged for Marketplace submission but is not yet under review or publicly available.

Delegated user consent is not enough

Tenant-wide behaviour needs admin consent on the Entra app registration. A user consenting for themselves produces a setup that appears to succeed and then returns nothing for everyone else — the same failure mode the Microsoft 365 Copilot usage connector has on the inbound side.

Confirm it actually worked

The client's “connected” badge reports a successful handshake, not a tool call. Ask Microsoft 365 Copilot something answerable only from your indexed Telara data, then read GET /v1/mcp/audit/log and look for a row with client_type=m365_copilot.

An answer with no matching audit row means the assistant replied from its own knowledge and never called Telara — a routing problem in the tool descriptions, not a broken connection. Every transport check will still look green.

Support, privacy, and reviewer testing

The complete OAuth and platform-review guide defines the governed 21-tool contract, the reviewer test flow, and the safe test action for platforms that permit writes.

For setup or reviewer access, contact support@telara.dev. For privacy requests, contact privacy@telara.dev. Telara's Privacy Policy and Terms of Service apply to every connection.

Comparing platforms? See connection paths for what each one needs. Looking instead to let Telara readthis platform's usage and spend? That is the opposite direction — see the connector catalog.