Alert failures

Overview

Cost Analyzer sends alerts for budgets, anomaly detections, and custom monitors through email and Teams notification channels. When alerts are not delivered, the cost monitoring chain breaks — overspend goes undetected and escalation policies do not trigger. This article covers the most common alert delivery failures and how to resolve them.

Business value

• Ensure critical cost alerts reach their intended recipients without delay
• Identify and fix broken notification channels before a real cost event occurs
• Distinguish between a delivery failure and a configuration issue to resolve the correct root cause

How it works

Alert delivery in Cost Analyzer depends on three components working correctly: the monitor must evaluate and trigger correctly, the notification channel (email or Teams webhook) must be reachable, and the recipient configuration must be valid. A failure in any one of these components results in a missed alert.

Troubleshooting

1. Alert triggered in Cost Analyzer but no email received
   Cause: The recipient email address is invalid, the email was delivered to a spam or quarantine folder, or the organization's mail filter is blocking notifications from the Turbo360 sending domain.
   Fix: Verify the recipient email address in the alert configuration. Check the recipient's spam and quarantine folders. If emails are being filtered, ask your IT team to allowlist the Turbo360 notification sending domain. Send a test alert from Cost Analyzer to confirm delivery after allowlisting.

2. Teams alert not delivering to the configured channel
   Cause: The Teams incoming webhook URL has expired, been deleted, or the Teams channel has been archived or renamed since the webhook was created.
   Fix: Open Microsoft Teams and verify the target channel is active. Regenerate the incoming webhook connector for the channel and update the webhook URL in the Cost Analyzer notification channel configuration. Retest the alert.

3. Alert was delivered but the wrong person received it
   Cause: The alert recipient list on the budget or monitor is outdated — a team member has changed roles, left the organization, or the cost group ownership has been reassigned without updating the alert configuration.
   Fix: Review the recipient list on the affected budget or monitor. Update it to reflect the current cost group owner. Review all related escalation policies to ensure the escalation chain is also current.

4. Escalation alert not triggering after the initial alert was sent
   Cause: The escalation policy delay period has not elapsed, the escalation policy is not linked to the correct alert, or the initial alert was acknowledged in the system before the escalation window expired.
   Fix: Confirm the escalation policy is correctly linked to the budget or monitor. Verify the escalation delay setting matches the intended window. Check whether the initial alert was marked as acknowledged — escalation does not trigger for acknowledged alerts in some configurations.

5. Alert history shows alerts as sent but recipients report never receiving them
   Cause: Alert history records dispatch from Cost Analyzer, not confirmed delivery at the recipient's mail server or Teams channel. Delivery failures at the destination are not always reflected in the alert history.
   Fix: Treat alert history as a dispatch log, not a delivery confirmation. Test the notification channel independently by sending a test notification from Cost Analyzer. If the test also fails, resolve the channel configuration issue before relying on alert history for confirmation.

Related articles

• Budget issues
• Escalation policies
• Automatic anomaly detection
• Monitoring strategies
• Common errors