Connect a Microsoft Teams webhook

Create, save, test, and secure a supported Microsoft Teams workflow webhook.

Last checked 21 August 2026

TechDash posts Microsoft Teams alerts to an external webhook workflow. Use the standard workflow intended to receive webhook alerts from outside Teams. A workflow restricted to people in your organisation requires Microsoft authentication and does not work as a normal TechDash webhook.

Create the workflow in Teams

  1. Open Microsoft Teams and find the channel that should receive TechDash alerts.
  2. Open the ••• menu beside the channel name and choose Workflows.
  3. Search for Send webhook alerts to a channel and select it.
  4. Sign in if Teams asks you to authenticate.
  5. Confirm the correct Team and Channel.
  6. Select Add workflow.
  7. Copy the Webhook URL that Teams displays.

If Workflows is unavailable, your Microsoft 365 administrator may need to enable the Workflows app. Do not choose a similarly named flow that requires the caller to authenticate as a person.

Add it to TechDash

  1. Open Notifications.
  2. Find Microsoft Teams webhook.
  3. Paste the complete HTTPS workflow URL.
  4. Select Send test.
  5. Confirm “TechDash test notification.” appears in the intended Teams channel.

There is no Save button. TechDash stores the field as it changes. Clearing Microsoft Teams webhook removes the global destination for future notifications.

Select How to configure beside the field whenever you need the in-app setup steps.

Supported URL hosts

TechDash requires HTTPS and accepts Microsoft Teams webhook URLs on these host patterns:

  • webhook.office.com and its subdomains
  • Subdomains of logic.azure.com
  • Subdomains of api.powerplatform.com

TechDash checks the hostname, not text elsewhere in the URL. A normal Teams channel link, SharePoint link, or Microsoft sign-in page is not a webhook and will be rejected.

Microsoft may vary the regional prefix in a workflow URL. Copy the entire generated value without shortening or editing it.

How the secret is stored

TechDash encrypts a non-empty webhook URL before saving it in local settings. The encryption key stays in TechDash application data on this computer. TechDash does not store this secret in the macOS login Keychain.

The URL can trigger the workflow, so treat it like a password. If it is exposed, remove or regenerate the workflow URL in Teams, then replace it in TechDash.

Which alerts use Teams

Microsoft Teams delivery requires:

  • A global Microsoft Teams webhook value.
  • Microsoft Teams On under Notify for the relevant monitored page.
  • A new notification-eligible failure, escalation, or enabled recovery.
  • No matching ignored-check rule.
  • TechDash running with network access.

Built-in Warning and Critical incidents can post. Built-in Advisory incidents remain in TechDash. A Custom Check follows its separate Notify choice, including a custom Advisory rule configured to notify.

Sitewide findings use the / monitored page's Microsoft Teams toggle when present, otherwise the first monitored page's toggle.

Understand the test

TechDash sends Teams a short card with the text “TechDash test notification.” The test uses one request with a fixed timeout. It bypasses severity, page toggles, ignore rules, and recovery settings.

TechDash does not check whether Teams accepted the message after the request completes. Confirm that the card appears in Teams. A “sent” result without a card can mean the workflow was removed, disabled, changed, or rejected the message. Recreate the standard Send webhook alerts to a channel workflow and test the new URL.

Related articles