Quick answer: In a Teams channel, add a Workflow using “Post to a channel when a webhook request is received”, copy its URL, and paste it under Integrate > Integrations > Microsoft Teams in Bugnet. New bugs, status and priority changes, comments and an optional daily digest arrive as Adaptive Cards with an “Open in Bugnet” button. Each connection is one channel with its own events and priority filter. Included on every Bugnet plan.
Studios that run on Microsoft 365 want bug alerts where the team already talks: Teams. The trick is sending the right alerts to the right channel, so a critical crash on launch day gets noticed and the hundredth duplicate of a cosmetic glitch does not. Here is how to set that up.
What gets posted
| Event | What you see |
|---|---|
| New bug | Every new report, from players through the SDK or from the dashboard. A report stacked onto an existing bug as a duplicate does not post again. |
| Bug updated | Status, priority, assignee, category and title changes, with who made them. Description edits are not posted. |
| Comment | New comments. Internal notes are never posted. |
| Daily digest | A summary from 09:00: new, resolved and open bugs, open critical and high counts, crash-free sessions and the day's most urgent new reports. |
Messages are Adaptive Cards with an Open in Bugnet button that goes straight to the full report: screenshot, description, logs and any stacked occurrences.
Setup
1. Capture bugs in the game
Create a free Bugnet project and add the SDK for your engine. Crashes and errors are captured automatically and players report the rest from an in-game widget.
2. Create a Teams workflow
- In Teams, open the channel, choose ••• next to its name, then Workflows.
- Pick Post to a channel when a webhook request is received, name it “Bugnet”, confirm the team and channel, and choose Add workflow.
- Copy the URL Teams shows (it is on
logic.azure.comorpowerplatform.com).
3. Connect it in Bugnet
Open Integrate > Integrations > Microsoft Teams, paste the URL, pick the events and the minimum priority, and choose Connect. Bugnet sends a test message straight away.
A channel layout that avoids alert fatigue
| Channel | Events | Priority filter |
|---|---|---|
| #qa | New bugs, updates, comments | All priorities |
| #live-ops | New bugs | Critical only |
| #studio | Daily digest | All priorities |
Each connection is one channel, so add as many as you need. If a message is refused, Bugnet retries after 1, 5, 25 and 125 minutes; the connection shows its last error, Deliveries lists every attempt, and Pause stops a connection without removing it.
Beyond chat
Chat is for noticing; planning happens elsewhere. Bugnet can also file bugs into GitHub, Linear, Jira, ClickUp, Asana, Trello and Notion, and page whoever is on call through PagerDuty or Opsgenie when a critical bug lands in a live game. Using Slack instead? See crash alerting in Slack.
Frequently asked questions
How do I send bug reports to Microsoft Teams?
Create a Teams workflow with the Post to a channel when a webhook request is received template, copy its URL, and paste it into Bugnet under Integrate, Integrations, Microsoft Teams. New bugs and updates then post to the channel as Adaptive Cards.
Do duplicate crash reports spam the channel?
No. A report stacked onto an existing bug as a duplicate does not post again, and each connection has a priority filter.
Can I get a daily bug summary in Teams?
Yes. The daily digest posts from 09:00 with new, resolved and open bugs, open critical and high counts, crash-free sessions and the day's most urgent new reports.
Are internal comments posted to Teams?
No. Internal notes are never posted.
Is the Teams integration free?
Yes. It is included on every Bugnet plan, including the free plan.
An alert channel only works if people still read it in month three. Filter hard, digest the rest.