Connect Microsoft Teams
Mirox can post your notifications directly into a Microsoft Teams channel — alarms, ticket activity, reports — so your whole team sees them where it already works. The connection is a standard Teams incoming webhook workflow: Teams gives you a URL, and you register that URL as a webhook in your Mirox notification settings. No plugin or app installation is required.
Where It Lives
The Mirox side of this guide happens on your Profile page, in the Notifications tab, under Channels ▸ Webhooks. Open in Mirox
Before You Start
- You need permission in Microsoft Teams to add workflows to the target channel (most channel members have this; your Teams administrator may restrict it).
- Decide which channel should receive Mirox notifications — a dedicated channel such as Mirox Alerts keeps them easy to follow.
Step 1 — Create the Webhook Workflow in Teams
- In Microsoft Teams, go to the channel that should receive notifications.
- Click the three dots (⋯) next to the channel name and choose Workflows.
- Select the template "Post to a channel when a webhook request is received".
- Sign in / confirm the connection if prompted, keep or adjust the workflow name, and click Next.
- Confirm the team and channel, then click Add workflow.
- Teams now shows the webhook URL. Copy it, then click Done.
Use Workflows, Not the Legacy Connector
Microsoft retired the older "Incoming Webhook" Office 365 connector. The Workflows template above is the current, supported way to receive webhook posts in a Teams channel. If you cannot find it via the channel menu, open the Workflows app in Teams and search for the same template.
The Workflow URL Is a Secret
Anyone who has this URL can post messages into your Teams channel. Treat it like a password — paste it into Mirox and do not share it anywhere else.
Step 2 — Add the Webhook in Mirox
- Open your Profile and select the Notifications tab.
- In the Channels card, under Webhooks, click Add webhook.
- Give it a recognizable name, for example Teams — Operations.
- Paste the workflow URL from Teams.
- Set the format to Microsoft Teams — this makes Mirox send messages Teams can render as cards.
- Save. Mirox shows the webhook's signing secret once — for a Teams connection you can simply close this, see About Signature Headers below.
Step 3 — Send a Test Message
- On the new webhook row, click Test.
- Within a few moments, a Mirox test message appears in your Teams channel.
If nothing arrives, re-check that the URL was copied completely and that the workflow is enabled in Teams, then test again.
Route Notifications to Teams
Adding the webhook makes the channel available — now make sure notifications actually use it:
- Turn on the master switch Send notifications outside the app in the Notifications tab.
- Make sure the webhook channel is enabled and selected for the notification groups you care about in the What notifies me card (by default, groups follow your global channel selection).
From then on, matching notifications are posted into your Teams channel as they happen.
About Signature Headers
Every webhook request Mirox sends is signed: it carries signature and timestamp headers computed from the webhook's signing secret, so a receiving system can verify the request really came from Mirox and is not a replay. Microsoft Teams ignores these headers — the workflow accepts any well-formed request that knows the URL — so for a Teams connection you never need the secret. It matters when you point a Generic JSON webhook at your own system and want to authenticate incoming requests; you can re-issue it any time with Rotate secret.
Troubleshooting
| Issue | Possible Cause | Solution |
|---|---|---|
| Test works, but no real notifications arrive | Master switch off, or webhook not selected for any notification group | Enable Send notifications outside the app and check the channel selection in What notifies me |
| Webhook row shows a disabled warning | Repeated delivery failures auto-disabled the webhook | Fix the cause (usually a deleted or changed workflow in Teams), update the URL, then click Test — a successful test re-enables it |
| Messages stopped after changes in Teams | Workflow deleted, disabled, or URL regenerated | Create/repair the workflow in Teams and update the URL in Mirox |
| Message shows raw JSON instead of a card | Format set to Generic JSON | Edit the webhook and set the format to Microsoft Teams |
Related Guides
- Notifications — the full notification settings guide: channels, groups, mutes, and working hours
- Tickets — the ticket activity that can be posted to Teams