Get incidents and alerts into the channel your team already watches
Post InfraNest alerts straight into a Teams channel, with a one-click path to filing an issue
Connect a Teams channel and InfraNest starts posting your alerts there instead of leaving you to check a dashboard by hand.
- Team alerts in the channel: the same list of what needs attention that goes out by email can post to a Microsoft Teams channel, in the same order and words.
- Personal alerts in chat: each person can also get their own alerts sent to them directly in Microsoft Teams.
- One click toward an open issue: an alert about an open incident with no issue yet carries a Create issue button; once an issue tracker is connected, pressing it opens InfraNest with the issue form ready to go. Once the incident has an issue, the same button becomes a link straight to it.
What it looks like in InfraNest
Or let an automation act on it
What you can do
Once Microsoft Teams is connected, this is what InfraNest can do with it.
- Team alert digest posted to a channel
- Personal alerts sent to each person
- Create issue button on open incidents
- Button links to the issue once filed
Not supported
This integration only delivers alerts to Teams and offers a button toward filing an issue — it does not read messages back from Teams or page anyone on call.
How to connect it
- 1
Create a workflow in Teams
Get the URL InfraNest needs to post into your channel: in Teams, open the channel, go to ⋯ → Workflows, and create the "Post to a channel when a webhook request is received" workflow.
- 2
Add the destination in InfraNest
Connect the channel so alerts have somewhere to go: open Alerts → Destinations, select Add, choose Microsoft Teams, and paste the workflow URL.
- 3
Test and save
Confirm messages actually reach the channel before relying on it: select Send test alert, check it appears in Teams, then Save.
That’s it — Microsoft Teams is connected.
Full setup guideSet up with AI
I use Microsoft Teams, and I want to connect it to InfraNest (infranest.io) — it manages domains, DNS, servers and certificates across providers. InfraNest asks for: Webhook URL. Walk me through creating that in Microsoft Teams: where each setting is in the current interface, whether a read-only option exists, and how to check it works before I paste it in.
Questions
#Can I use the old Incoming Webhook connector URL?
No. Microsoft retired those on 22 May 2026, and a webhook.office.com URL can no longer deliver anything. You need the newer workflow URL from Teams' Workflows feature, as described in the setup guide.
#Will alerts show up as coming from InfraNest?
No — messages arrive posted by Workflows rather than under an InfraNest name. That's how Microsoft's replacement for connectors works on their side, not something either InfraNest or you can change.
#What happens if the workflow URL stops working?
If the channel's workflow is removed or the URL is revoked, InfraNest can no longer post to that channel and you'll need to create a new workflow and update the destination with the new URL.
#Can I send alerts to more than one channel?
Yes, but each workflow posts to a single channel, so you'll add a separate destination with its own workflow URL for each additional channel.
#What do I need before connecting Microsoft Teams?
You need a workflow URL created in the Teams channel (Workflows, not the old Incoming Webhook connector) — see the setup guide.
Often connected together
One dashboard for every provider
Add this integration, then the rest of your stack — domains, DNS, servers, certificates and monitoring in one place.
Free plan · No credit card required · Set up in minutes