Microsoft Teams

The Microsoft Teams integration posts every share you create as an Adaptive Card into a Teams channel: title, page, environment, diagnostics counts, a link to the annotated screenshot, and a View full report button.

Do not use “Connectors → Incoming Webhook”

The legacy Teams Incoming Webhook (an Office 365 / Microsoft 365 Connector) was retired by Microsoft: connectors stopped working on 22 May 2026 and new ones can no longer be created. Tutorials that tell you to open Channel → Connectors → Incoming Webhook are out of date.

The supported path is the Workflows app (Power Automate) described below.

Step 1: Create a Workflows webhook in Teams

1. In Teams, open the team and channel that should receive reports
2. Click ⋯ next to the channel → Workflows
3. Search for and pick the template “Post to a channel when a webhook request is received”
4. Confirm the team and channel, then click Save
5. Copy the generated webhook URL — it is a Power Automate URL, e.g. https://prod-12.<region>.logic.azure.com/workflows/…/triggers/manual/paths/invoke?…

Step 2: Add the integration in BugCapturer

1. Sign in and open the integrations page
2. Pick Microsoft Teams in the left platform list → Add integration
3. Fill in a name and the Workflow webhook URL from step 1
4. Click Verify & save — the backend checks the URL is a Power Automate host and posts a test card to your channel
5. When the card appears in Teams, the integration is active

What the card contains

Element	Content
Title	🐞 [type] first line of the description
Page	Title of the page where the report was captured, linked to the sanitized URL
Env	Browser · OS · screen resolution
Diagnostics	Counts only — Console 2 · Network 0
Screenshot	Link to the annotated screenshot — shown inline when Teams can fetch the image
Button	View full report → the share page (with the full error details)

What to expect from Teams

Behaviour	Detail
Sender identity	Cards are posted by the Workflows bot (Flow bot). The icon and display name cannot be customised.
Workflow ownership	A workflow belongs to the user who created it. If that person leaves and the flow has no co-owner, it becomes an orphan flow and stops posting. Create it with a team account or add a co-owner.
Message size	28 KB per message. BugCapturer truncates the description well below that.
Rate limit	Roughly 4 requests/second. Exceeding it returns 429; BugCapturer retries with backoff.
Private channels	Workflows support for private channels arrived late (April 2026). If posting fails, use a standard or shared channel.
Adaptive Cards	BugCapturer sends an Adaptive Card wrapped in a message envelope. Buttons are OpenUrl actions only — no interactive callbacks.

Delivery, retries and failures

• Any 2xx response counts as success — Workflows normally returns 202 Accepted
• Failures are retried twice (5s / 15s backoff) and recorded in the delivery log
• 20 consecutive failures auto-disable the integration and email you
• Typical causes: the workflow was turned off or deleted, the channel was removed, or the tenant blocks Power Automate flows

Security

• The webhook URL is the credential — anyone holding it can post into that channel
• BugCapturer never shows it back in full: cards and lists display only the last 6 characters
• To replace it, paste the full URL again while editing the integration
• To revoke it, turn off or delete the workflow in Teams
• Only Power Automate hosts (*.logic.azure.com, *.powerplatform.com, *.powerautomate.com) are accepted

FAQ

“Official webhook domains only” on save? The URL must be a Power Automate / Workflows webhook. Connector URLs (*.webhook.office.com) no longer work and are rejected.

Where is the screenshot? The card always carries a link to the annotated screenshot. Teams fetches and renders the image itself; if our screenshot proxy is unreachable the card still posts and the link still works.

I need reports in a private channel? Use a standard or shared channel for now; Workflows support for private channels is still uneven across tenants.

See also: delivery logs and auto-disable.