Connect Microsoft Teams

Deliver InfraNest alerts into a Microsoft Teams channel, so incidents and expiries reach the whole team.

#Before you start

Get a workflow URL for the Teams channel you want alerts in:

1. In Teams, open the channel and select ⋯ → Workflows.
2. Choose the Post to a channel when a webhook request is received template and create it.
3. Copy the URL the workflow shows when you save it. It is on logic.azure.com or api.powerplatform.com.

Not the old Incoming Webhook connector. Microsoft switched those off on 22 May 2026, so a URL containing webhook.office.com can no longer deliver anything — InfraNest will not accept one. Many search results still describe that route; the Workflows steps above are the current one.

#Connect it in InfraNest

1. Go to Integrations → Microsoft Teams and select Connect (or Add account if you already have a Teams destination). From Alerts → Destinations, Add destination takes you to the same place.
2. Under Post into a Microsoft Teams channel, give it a Name — the team or channel it reaches — and paste the Workflow URL.
3. Select Connect.
4. InfraNest offers to Send a test straight away. Do it, and check the message appears in the channel.

#What arrives in Teams

Each alert is a card in the channel: what happened, then the details. Teams can't change a card once it is posted, so when the problem is over InfraNest posts a new one that names the alert it closes and how long it lasted.

#Turn an alert into an issue

When your workspace has Jira, Linear or GitHub connected in Integrations, an alert about an open incident carries a Create issue button. It opens the incident in InfraNest with the Create issue window ready: check the tracker and the project or team, then select Create issue. If the incident already has an issue, the button names it (for example Linear ENG-143) and opens it instead. The button opens InfraNest rather than filing the issue inside Teams, because alerts reach Teams through a workflow that can't send anything back to InfraNest.

#The destination's page

Under Integrations → Microsoft Teams → Connections & settings, select the destination to open its page.

• Connection details: the workflow URL it sends to. Paste a new one to replace it, then select Save.
• What should this destination hear?: All events or Urgent only.
• Hours (optional): set From and Until, and optionally the days. Outside those hours the destination hears critical events only, so an outage still gets through.
• "Needs you" digest: Off, Daily or Weekly, on Monday. Posts the same list as the "needs you" email in the channel, in the morning in your workspace's time zone, and only when something new appears. Anything urgent is still sent the moment it happens.
• The ⋯ menu at the top has Test connection, Rename account, Disable integration (and Enable integration to switch it back on) and Disconnect.

In the destination list, the ⋯ menu next to each destination has Send test, Edit (its page) and Delete. A deleted destination can be restored from Recently deleted for 14 days.

#Check it keeps working

Under Alerts → Destinations, each destination shows its last test: Last test delivered, Last test sent … not confirmed yet or Last test failed. Switch on Monthly test to have a test alert sent there once a month, so a broken path shows up before an outage does. Each test message has an I got it link: click it to confirm someone saw it.

If Microsoft Teams starts turning alerts away, the destination says Not delivering and Alerts are not reaching this destination, and whoever manages it is told by email and in the bell. It is never switched off: InfraNest keeps sending, emails each alert it turned away to whoever manages it instead, and keeps them for 7 days so you can Send them here now once it works again. See A destination says it is not delivering.

#Send alerts to Teams

Once the destination is saved, choose it when you decide which alerts go where. See Alerts and destinations.

#Good to know

• The workflow URL is stored securely and never shown again after saving.
• One workflow posts to one channel. Add another destination for a different channel.
• Alerts appear posted by Workflows, not under an InfraNest name. That is how Microsoft's replacement for connectors works and is not something either side can change.
• If your organisation restricts Power Platform, an admin may need to allow the Workflows app before the template above can be created.

#Related articles

• Alerts and destinations
• A destination says it is not delivering
• Connect Power Automate — to start a flow from an InfraNest event instead