Set up Microsoft Teams webhook notifications

Use Teams Workflows → Send webhook alerts to a channel, allowing external callers under your organization’s policy, then copy the full signed URL. In CostRadar, open Settings → Alert Channels, paste it into Microsoft Teams Webhook URL, click Test, check the destination channel, then Save Channels. Never paste a webhook URL into the chatbot. Testing does not save it; Connected means stored, not verified delivery. Growth or Business is required.

Create a Teams Workflow

1. In Microsoft Teams, open Workflows and search for Send webhook alerts to a channel. Microsoft may also show wording such as Post to a channel when a webhook request is received. Use a webhook-to-channel template, not a channel link or a legacy connector setup guide.
2. Sign in to the Teams connection when prompted, choose the Team and Channel, and create/save the workflow.
3. CostRadar sends a webhook POST without a Microsoft user bearer token. Use the template allowing external callers; if the trigger offers Who can trigger the flow?, it must allow Anyone, not only people in your organization or specific users. Only do this if your organization's policy permits it. The secret URL authorizes posting: do not publish it. If this option is prohibited, ask your Microsoft administrator; do not bypass policy or broaden Graph permissions.
4. On the workflow details page, choose Copy webhook link. Keep the complete generated HTTPS URL, including its query string and signature. Do not shorten it or substitute your Teams channel URL. Keep the workflow enabled.

Connect and test in CostRadar

Webhook alerts require Growth or Business and an account owner who can manage settings. Open Dashboard → Settings → Alert Channels. Paste the URL into Microsoft Teams Webhook URL. Never paste a webhook URL into the chatbot, support email, or screenshots.

Click Test while the entered URL is present: this sends a real test message. Check the intended Teams channel for the card. Then click Save Channels to retain the URL for future alerts; testing alone does not save it. A successful test response means the receiving endpoint accepted the request, not proof the workflow posted a card. Verify the channel and, if necessary, the workflow run history.

After reloading, Connected and a masked value mean a URL is stored, not that delivery was recently verified. The saved URL is not revealed. To replace or retest it, focus the field and paste the full URL from Teams, test, then save. Do not paste the displayed mask. Disconnect removes the CostRadar destination; it does not delete the Teams workflow.

Troubleshooting Teams webhook notifications

If Workflows or a template is unavailable, or you cannot select the destination channel, ask your Teams administrator about app policy, channel permissions, and workflow availability. Keep an appropriate workflow owner/co-owner so the flow can be maintained if its creator leaves.

For 401/403 or authentication failures, check the trigger's caller restriction and connection authorization; do not add a Microsoft password or Graph token to CostRadar. For an accepted test with no card, check the chosen channel, workflow run history, failed actions, and Teams connection. CostRadar sends an Adaptive Card payload; use a compatible webhook-to-channel flow rather than a custom trigger expecting unrelated JSON.

For an invalid URL, copy the full link again. If it was leaked, revoke or regenerate it in Microsoft and replace the saved URL. If Webhook host resolves to a non-public address persists, report the exact error text without the URL to support@costradar.io; do not substitute an IP address or disable security checks.

The chatbot can guide setup but cannot access your Teams workspace, configure the flow, contact support, or confirm message receipt. Future anomaly notifications depend on detection and eligibility; a test does not generate a billing anomaly or prove future alert delivery. Azure cost data and alerts are not real time.

Microsoft instructions

On Microsoft Support, search for “Send messages in Teams using incoming webhooks.”