Skip to main content
Ask AI

Microsoft Teams

The TestRelic Microsoft Teams App brings Ask AI into the Teams channels where your team already works. It is a full-parity counterpart to the Slack App: run an Ask AI prompt from a channel, pin a weekly QA digest, push any artifact from the web app to Teams, and get alerted when a quality gate fails — all without leaving Teams.

Growth plan required

The Teams App talks to Ask AI, which is part of the Growth plan. See Plans & Billing. Prompts from an org on the Starter plan will respond with a plan-upgrade prompt.

What the integration enables​

The Teams App offers the same capabilities as the Slack App, mapped onto Teams terminology:

  • Run Ask AI from a channel — Address the TestRelic bot with a prompt and it runs through Ask AI, then threads the response under your message with charts, deep links, and follow-up actions.
  • Scheduled QA digests — Post recurring summaries (weekly flaky digest, Monday sprint review, nightly regression report) to any channel; cards render with metric tiles, top offenders, and a "View full dashboard" deep link.
  • Share-back from the web app — One action on any Ask AI artifact — dashboard, report, test plan, presentation, data table, or chart — sends a rich card to the Teams channel of your choice.
  • Failure alerts — Optional alerts when monitoring quality gates fail, with the failing test case, a summary of the cause, and an "Open in TestRelic" button.
  • Threaded Ask AI follow-ups — Replies in the same thread continue a single Ask AI conversation, so follow-ups inherit @repo, @test_run, and other context from the original prompt.

The app uses the same Ask AI runtime, artifacts, memory, and privacy posture as the web app and the Slack App.

Installing the Microsoft Teams App​

Installation is a two-step flow. Unlike Slack, connecting in TestRelic alone is not enough to make the bot appear in Teams — you also have to add the Teams app package.

Step 1 — Connect in TestRelic (OAuth)​

  1. Open Settings → Integrations → Microsoft Teams in the TestRelic web app and click Connect.
  2. You are redirected to Microsoft Entra ID (Azure AD) to sign in and grant consent.
  3. After approval you are returned to TestRelic with the integration showing Connected.

This OAuth step binds your Teams tenant to your TestRelic org. It establishes the trust relationship — but it does not, on its own, place the bot in any Teams channel.

Connect alone does not add the bot

Microsoft Teams requires a separate app package to be installed before the bot is usable. OAuth Connect only links your tenant to your TestRelic org. The TestRelic bot appears in Teams only after Step 2 below. If you finish Step 1 and the bot is nowhere to be found, that is expected — continue to Step 2.

Step 2 — Add the Teams app package​

The bot becomes available in Teams once the TestRelic Teams app package is added to your tenant and the Azure Bot Teams channel is enabled:

  • Sideload it yourself — If your tenant allows custom app uploads, add the app package directly from Apps → Manage your apps → Upload an app in the Teams client.
  • Have a Teams admin upload it — If custom uploads are restricted, a Teams administrator can publish the package to your organization's app catalog from the Teams admin center, after which everyone in the tenant can add it.

Once the package is installed, add the TestRelic app to the channels where you want to use it, then return to a channel and address the bot with a prompt.

note

The two steps are independent in order of completion, but both are required: Connect (Step 1) establishes the tenant ↔ org link, and the app package (Step 2) places the bot in Teams. Only when both are done will prompts reach Ask AI.

Running Ask AI in a channel​

Address the TestRelic bot in any channel it has been added to, and write your prompt in natural language — the same as the Ask AI composer in the web app.

Basic prompts​

Channel: QA Leads
which tests broke after yesterday's deploy?

The bot replies in-thread with a regression summary card: failing test cases, the most likely root cause, affected modules, and a button to open the run in the web app.

Channel: Checkout Team
show me the flakiest tests in the checkout suite over the last 7 days

Returns a card with a trend per offender, retry counts, and a "Pin as weekly digest" action.

Scoping prompts with TestRelic context​

You can use the same @ shortcuts that work in the web composer:

summarize failures in @run-20260518-prod and tell me which are infra vs product
generate a sprint review deck for @repo:web-app covering the last 14 days

When the response includes a presentation, report, or dashboard artifact, the app attaches it and posts a preview card.

Threaded follow-ups​

Replying in the thread continues the same Ask AI conversation:

which tests broke after yesterday's deploy?
   ↳ "and which of those have been failing for more than a sprint?"
   ↳ "open a Jira ticket for the top 3"

The third message uses your connected Jira integration to file tickets without leaving Teams.

Scheduled QA digests​

Digests are recurring, AI-generated summaries that post on a schedule to a channel of your choice.

Creating a digest​

From the web app:

  1. Open Ask AI, run the prompt you want to schedule (e.g. "weekly flaky digest for last 7 days").
  2. In the artifact toolbar choose Share → Schedule to Microsoft Teams.
  3. Pick the destination channel, choose a cadence (daily / weekly / monthly), set the time and timezone, and confirm.

You can also ask the bot to schedule a digest directly from a channel.

Managing digests​

  • View all scheduled digests at Settings → Integrations → Microsoft Teams → Schedules.
  • Pause, edit cadence, or change the destination channel inline.
  • Audit log entries record who created, paused, or deleted each schedule.

What digests look like​

Every digest is a Teams card with three sections:

  1. Headline metrics — stat tiles (e.g. Pass Rate, Flaky %, MTTR) computed from the digest's time window.
  2. Top offenders — the top entities relevant to the prompt (flakiest tests, slowest suites, most-recent regressions), each with retry counts or trend deltas.
  3. Deep link — a "View full dashboard" button that opens the equivalent Ask AI artifact in the web app, with the same time window and filters.

Share-back from the web app​

Every Ask AI artifact in the web app has a Share → Microsoft Teams action.

  1. Generate the artifact in the Ask AI chat (dashboard, report, test plan, presentation, data table, or chart).
  2. Click Share → Microsoft Teams in the artifact toolbar.
  3. Pick the channel and add an optional message.
  4. The card is posted with metric snapshots, a preview (for presentations and reports), and an "Open in TestRelic" deep link.

For more on what each artifact type contains, see AI Insights & Artifacts.

Failure alerts​

Connect monitoring quality gates to Teams to get a notification the moment a gate fails:

  1. Go to Monitoring → Quality Gates and pick a gate.
  2. Under Notifications, add a Microsoft Teams channel as a destination.
  3. Failure alerts include the failing test case, the gate threshold that was crossed, and an Open in TestRelic button. You can reply in the thread with an Ask AI prompt to ask for a root-cause analysis.

Sample use cases​

Daily standup helper​

Run during standup to anchor the conversation in real numbers:

what's the test pass rate trend for the last 5 days, and any new flaky tests this morning?

The card surfaces stat tiles plus a list of overnight regressions, so engineers can divide work before the meeting ends.

Triage a noisy alert​

When a quality gate alert fires:

  1. Click the Open in TestRelic button to confirm the failure is real.
  2. Reply in the alert thread asking whether it was a flake or a real regression.
  3. The AI inspects retry patterns, comparable past failures, and CI metadata, and returns a verdict with confidence.

Sprint review one-liner​

The day before sprint review, a scheduled digest posts to an engineering-leads channel:

generate a 4-slide sprint review covering test coverage, flakiest tests,
new regressions, and MTTR for the last 14 days

The card attaches the deck. Stakeholders read it in Teams; engineers open the artifact in TestRelic for drill-down.

Cross-team coverage check​

A PM asks a coverage question without leaving Teams:

map critical test paths from the checkout journey to confirmation
and flag any P0 gaps for @repo:web-app

The reply renders a navigation-path map and a coverage-gap table, so PM and QA can align in-channel.

Conversation memory and privacy​

  • Teams-originated conversations show up in the Ask AI Chat Sidebar in the web app, tagged with a Teams badge, and are unified with your web and Slack Ask AI conversations.
  • Memory is scoped per TestRelic user — if you trigger a prompt from Teams and continue from the web app under the same TestRelic account, memory is continuous.
  • The app acts only on prompts addressed to it; it does not ingest general channel traffic.
  • Prompts and responses are stored in the same governed Ask AI conversation history as the web app — they are not used to train shared models.

Troubleshooting​

The bot doesn't appear after Connect​

This is the most common issue, and it is expected behavior. OAuth Connect only links your Teams tenant to your TestRelic org — it does not place the bot in Teams. Complete Step 2 above: add the TestRelic Teams app package (sideload it yourself or have a Teams admin upload it to your org's app catalog) and make sure the Azure Bot Teams channel is enabled. Then add the app to the channels where you want to use it.

Prompts aren't reaching Ask AI​

Confirm both halves of the install are in place: the integration shows Connected in Settings → Integrations → Microsoft Teams (Step 1), and the app package is installed and added to the channel (Step 2). If either is missing, prompts will not reach the Ask AI runtime.

Plan-upgrade prompt instead of an answer​

Ask AI is part of the Growth plan. If your org is on Starter, the bot responds with an upgrade prompt and scheduled digests pause automatically. See Plans & Billing.

Digest didn't post at the scheduled time​

Check Settings → Integrations → Microsoft Teams → Schedules. Common causes:

  • The destination channel was removed, or the app was removed from it — re-add the app to the channel.
  • The org is on the Starter plan — only Growth orgs can run AI digests; the schedule pauses automatically with a notice.
  • The digest prompt failed to resolve (e.g. it references a deleted repo) — edit the prompt or recreate the schedule.

Disconnecting​

  1. Navigate to Settings → Integrations → Microsoft Teams.
  2. Click Disconnect.
  3. Confirm. Scheduled digests are paused and channel mappings are retained in case you reconnect.

Removing the TestRelic app package from Teams (or having a Teams admin remove it from the app catalog) stops the bot from appearing in channels independently of the OAuth connection state.