Manage365 Docs

Teams & Slack notifications

Manage365 alerts can fan out to Microsoft Teams or Slack channels via incoming webhooks. Delivery is best-effort and never blocks the state change that produced the alert.

Microsoft Teams

  1. In Teams, open the channel where alerts should land.
  2. Channel menu → Connectors →Incoming Webhook. Name it “Manage365 alerts”, optionally upload your MSP logo.
  3. Copy the generated webhook URL.
  4. In Manage365: Settings → Notifications → Add channel. Pick type Microsoft Teams, paste the webhook URL, set severity filter + severity-floor.
  5. Send a test — look in the Teams channel, the card should appear with severity colour, tenant context, and an ack / resolve link back into Manage365.

Slack

  1. In Slack: Apps → Incoming Webhooks → Add to Slack. Pick the channel, copy the webhook URL.
  2. In Manage365: Settings → Notifications → Add channel. Pick type Slack, paste the URL, configure filters.
  3. Send a test. The message is a Block Kit card with severity, title, tenant, an ack action button, and a deep link.

Severity routing

Per-channel severity floor means you can pipe onlyhigh + critical to the NOC Teams channel while the L2 / L3 channel gets everything medium+. Mix freely.

What the cards contain

  • Severity badge (colour-coded)
  • Alert title + short description
  • Customer tenant (with link)
  • Resource type + resource ID
  • Created timestamp in local time
  • Inline actions: Ack, Resolve, Open in portal

Delivery accounting

Each channel tracks successful and failed delivery counts and the last error. If a webhook gets 410'd by Microsoft / Slack (e.g. the channel was deleted), the channel enters a disabled state after three consecutive failures — fix the URL and re-enable.