Microsoft Teams

https://docs.evohub.io/mcp

claude mcp add --transport http evohub-docs https://docs.evohub.io/mcp

{
  "mcpServers": {
    "evohub-docs": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://docs.evohub.io/mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "evohub-docs": {
      "url": "https://docs.evohub.io/mcp"
    }
  }
}

{
  "servers": {
    "evohub-docs": {
      "type": "http",
      "url": "https://docs.evohub.io/mcp"
    }
  }
}

EvoHub can post On-Call alerts to a Microsoft Teams channel. Each alert arrives as a card with its title, severity, source and start time, and buttons to acknowledge it, resolve it or open it in EvoHub. Teams runs alongside paging: it never replaces the phone calls, push notifications and emails your escalation policies send.

Teams messages are free: they are not counted towards your usage.

Microsoft retired Office 365 connectors in Teams in May 2026. Old "Incoming Webhook" URLs (outlook.office.com/webhook/…) no longer work and EvoHub does not accept them. Use a Workflows webhook as described below.

#Add a Teams channel

The URL is a credential: anyone who has it can post to your channel. EvoHub stores it encrypted and never shows it again. To change it, remove the channel and add it again with the new URL.

Only URLs on powerplatform.com or logic.azure.com over https are accepted.

Adding, testing and removing chat channels needs the On-Call settings permission and the Organization settings permission. A Teams channel added here can also be picked as an Uptime notification channel and a changelog notification destination.

#Where alerts are posted

• Every new alert — channels marked Every new On-Call alert in Chat apps get every new alert.
• From an escalation step — open the escalation policy, click Edit, and in the step's Chat area pick the channel under Chat channel. The step still pages its target; the post is in addition. See Escalation policies.

An alert is posted to a channel once, even if both apply.

#Acknowledge and resolve from Teams

The Acknowledge and Resolve buttons open EvoHub in your browser. You confirm the action there, signed in as yourself:

• You need permission to respond to alerts. If the alert belongs to a team, you must be in that team, be an admin, or be the person the alert is assigned to.
• If you are signed in to a different organization, EvoHub tells you to switch to the alert's organization first.
• Each button link works once and expires after 24 hours. After that, open the alert from Open in EvoHub instead.

The action is recorded on the alert's timeline under your name, for example "Acknowledged from Microsoft Teams."

#When the alert changes

A Workflows webhook cannot edit a card it has posted. So when the alert is acknowledged, taken over or resolved — anywhere: in EvoHub, the mobile app, by phone or in Slack — EvoHub posts a short follow-up card under the original, for example "Resolved by Ada Lovelace: Disk full on db-1". The original card keeps its buttons; using one on an alert that is already done just tells you so.

Cards are posted by Teams' "Flow bot". Teams limits a channel to a few messages per second; EvoHub waits and retries once when Teams asks it to slow down.

#Remove a channel

In Organization → Chat apps, click the remove (trash) button next to the channel and confirm with Remove. Escalation steps that named it post nowhere until you choose another channel. Delete the workflow in Teams as well if you no longer need it.

#Related

• Slack
• Escalation policies