TestingOps.ai

Connection guides · Connection guide

Microsoft Teams, Copilot and TestingOps: a Copilot Studio agent for your tests

Teams has no setting of its own for adding an MCP server. You build an agent in Copilot Studio, add the TestingOps MCP server as its tool and publish the agent to Teams and Microsoft 365 Copilot.

  • Connection guide
  • Setup guide
Request a demo Microsoft: connect an agent to an existing MCP server
Connection
Connection guide
Writes back
Depends on the access you grant
Last checked
7 Nov 2026

In short

Microsoft Teams & Copilot and TestingOps in short

TestingOps does not ship a Teams app or bot; instead, an agent built in Microsoft Copilot Studio uses the TestingOps MCP endpoint, which ends in /api/mcp/v1, as a Model Context Protocol tool and is published to Teams and Microsoft 365 Copilot.

The Copilot Studio agent signs in to TestingOps through the consent page or sends an access key in the Authorization header, then reads runs, cases and defects or, with write access, starts runs and files defects.

TestingOps never reads Teams chats, meetings, mail or files, and building, publishing and licensing the agent happen in your Microsoft tenant.

What it does

What it does for your testing

  1. 1

    Run results asked for in Teams

    Input
    A question to the agent in Teams: did last night's regression pass?
    TestingOps
    Returns the run's outcome and its failing cases through the agent's TestingOps tool
    Output
    The answer in the Teams conversation, without opening TestingOps
  2. 2

    A defect filed from a conversation

    Input
    A tester describing a failing case to the agent
    TestingOps
    Files a defect in TestingOps with steps, expected and actual results, linked to the failing result
    Output
    A defect that is counted, retested and tied to its case instead of a chat message
  3. 3

    Release status in Microsoft 365 Copilot

    Input
    A release manager's question about readiness
    TestingOps
    Returns the readiness recommendation with open blockers and cases that never ran
    Output
    The status, including its gaps, in the Microsoft tool the manager already uses

Step by step

How it works

  1. Create an agent in Copilot StudioCopilot Studio is where the agent lives; Teams itself has no option to add an MCP server.
  2. Add TestingOps as an MCP toolOn the agent's Tools page, add a new tool of type Model Context Protocol and enter the endpoint from Integrations → API & MCP as the server URL.
  3. Choose how the agent signs inOAuth sign-in through the TestingOps consent page, or an API key sent in the Authorization header with the value Bearer <key>.
  4. Publish to Teams and Microsoft 365 CopilotPublish the agent from Channels to Teams and Microsoft 365 Copilot. Your Microsoft 365 admin may have to approve it.
  5. People ask the agentThe agent calls TestingOps tools when a question needs them, with the permissions of the TestingOps identity behind it.

Copilot Studio's menus and licensing belong to Microsoft and can change. TestingOps provides the endpoint, the consent page and access keys.

Connect

Setup

  1. In TestingOps, open Integrations → API & MCP and copy the Endpoint (streamable HTTP); for key sign-in, create a key under Access keys.
  2. In Copilot Studio, open the agent's Tools page, add a new tool and choose Model Context Protocol; enter a server name, a description and the endpoint as the server URL.
  3. For authentication choose OAuth 2.0 with dynamic discovery to use the TestingOps consent page, or API key as a header named Authorization with the value Bearer <key>.
  4. Add the tool to the agent, then publish the agent to Teams and Microsoft 365 Copilot from Channels; your Microsoft 365 admin may have to approve it.

Documentation: Microsoft: connect an agent to an existing MCP server

Where you connect it in TestingOps: Integrations → API & MCP → Connection guides → Microsoft Teams & Copilot

Use cases

Use cases

A quick status check in Teams

Trigger
A developer asks the agent whether the overnight run passed
Uses
Runs and their results
Agent activity
The Copilot Studio agent calls TestingOps and summarises the failing cases
Result
The answer in Teams without switching tools
Condition
The agent must be published to Teams and approved where your tenant requires it

Report a defect where the discussion happens

Trigger
A tester describes a failure in a chat with the agent
Uses
Defect reporting linked to the run result
Agent activity
The agent files the defect in TestingOps with steps, expected and actual result
Result
A tracked defect instead of a message that gets lost
Condition
Needs read and write access

Release readiness for a manager

Trigger
A release manager asks Microsoft 365 Copilot about the coming release
Uses
Release readiness assessment
Agent activity
The agent returns the recommendation together with blockers and never-run cases
Result
A status that says what is not covered
Condition
Read only access is enough

Capabilities

Capabilities and limits

What is read

  • Through your agent: runs, results and evidence, cases, defects, release readiness and the knowledge base of the projects its TestingOps identity can open
  • Not read: Teams chats, meetings, mail, calendars or files

What is produced

Answers in Teams or Microsoft 365 Copilot that your agent builds from TestingOps tool results

Where it can write

With read and write access: cases, runs, defects and items in trackers connected to TestingOps. TestingOps writes nothing to Teams or Microsoft 365.

How it connects

A Model Context Protocol tool in a Copilot Studio agent, pointing at the TestingOps MCP endpoint over streamable HTTP

Account and permissions

  • OAuth sign-in on the TestingOps consent page, or an access key sent as Authorization: Bearer <key>
  • An access key acts as the person who created it: if the agent sends one key for everyone, every user of the agent works with that person's TestingOps permissions
  • Building, publishing and licensing the agent happen in your Microsoft tenant; an admin may need to approve it

Limits

  • No TestingOps Teams app, bot or manifest: the agent is yours to build and maintain
  • TestingOps agents cannot use Teams, Outlook, SharePoint or OneDrive as tools; that direction needs an app registration in your own Microsoft Entra tenant and is not offered
  • The TestingOps endpoint must be reachable from Microsoft's cloud over https
  • Tools only: no MCP resources or prompts

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A QA team publishes a Copilot Studio agent called Test status to Teams. A developer asks it whether the payment cases passed on staging after the morning deployment; the agent reads the latest run through TestingOps and replies with two failing cases and their error messages.

The tester in the same chat asks the agent to file a defect for one of them. Because the agent signs in with read and write access, the defect lands in TestingOps linked to the failing result, where the team's triage picks it up.

Frequently asked questions

Is there a TestingOps app for Microsoft Teams?

No. You build the agent in Copilot Studio and publish it in your own tenant; TestingOps provides the MCP endpoint, the consent page and the access keys the agent uses.

Does TestingOps read our Teams chats or meetings?

No. Your agent calls TestingOps; TestingOps does not connect to Teams, Outlook, SharePoint or OneDrive. Letting TestingOps agents use those as tools would need an app registration in your own Microsoft Entra tenant and is not offered.

Sign-in or access key?

With sign-in, each person approves access with their own TestingOps account. An access key acts as the person who created it, so if the agent sends one key for everyone, every user of the agent works with that person's permissions.

Can the agent start test runs?

Yes, with read and write access. A run against a production environment also needs the production run permission and a person's approval in TestingOps.

What do we need on the Microsoft side?

Copilot Studio to build the agent and a tenant that allows publishing it to Teams and Microsoft 365 Copilot; your Microsoft 365 admin may need to approve the agent. Licensing is Microsoft's, so check it with your admin.

Next step

Request a demo to see what a Copilot Studio agent can answer from your TestingOps projects.

Request a demoMore connection guides integrations