How to set Teams, Slack and email alerts

Set the organization’s default alert destinations in Settings ▸ Alerts. Teams, Slack and email are separate channels, so one alert can reach all of them, and each is paused or replaced for a cost group on its own.

Admins only

You need the Admin role to do this. Admins are set in Settings ▸ Users & Access. If you don’t see the screens below, ask an admin in your organization.

Set the default channels

Open Settings ▸ Alerts. Under Organization Teams channel webhook, turn Alerting on and enter the Teams channel webhook URL. CloudMonitor accepts HTTPS Power Automate workflow URLs, including current api.powerplatform.com URLs, and Microsoft Teams incoming webhook URLs.

To add Slack delivery, use Organization Slack channel webhook in the same form. Turn Alerting on and enter an HTTPS Slack Incoming Webhook URL beginning https://hooks.slack.com/services/ (or the equivalent hooks.slack-gov.com URL for GovSlack). Do not paste a Slack URL into the Teams field: Slack expects Block Kit JSON, while Teams expects an Adaptive Card.

To add email delivery, turn Alerting on under Organization email recipients and list the Email addresses that should receive alerts. Separate addresses with commas or new lines. Every address receives every alert sent to the organization recipients, and a repeated address is kept once.

Select Save once after staging changes to any of the destinations. Select Cancel to discard all staged destination changes. An invalid URL, or an email address CloudMonitor cannot accept, is named beside its field, and Save stays unavailable until it is fixed.

The saved destinations receive alerts unless the affected cost group has its own destination on that channel.

Pause default delivery

Use a destination’s Alerting control to pause delivery, then select Save, when you need to keep its URL or addresses without sending alerts to it. Each channel pauses on its own: pausing Teams does not pause Slack or email.

While the organization Teams webhook is off, the page shows this warning, followed by how many cost groups have no Teams destination of their own:

No active organization Teams channel webhook.

Those cost groups get no Teams alerts until the organization Teams webhook is active again. Their Slack and email delivery is unaffected. Slack and email show a similar warning while you have turned them on but not yet saved:

No active organization Slack channel webhook.

No active organization email recipients.

Cost Group overrides lists each cost group with its own destination on any channel. Check it before turning a default off.

Give one cost group its own destination

Open the group from the Cost Groups list in Cost Allocation, choose edit, then open the Alerts step. Cost group owners can manage their own group’s delivery; admins can manage every group’s delivery. The step shows a channel only while its organization destination is turned on in Settings ▸ Alerts.

Clear Use organization Teams alert channel, Use organization Slack alert channel or Use organization email recipients, enter the group’s own webhook URL or email addresses, then select Save changes.

A cost group’s destination replaces the organization destination on that channel only. If the organization has Teams and email turned on and a cost group sets only its own Teams webhook, that group’s alerts go to its own Teams channel and to the organization email recipients. This applies to both anomaly and budget alerts.

To return a channel to the organization destination, select its Use organization option again and select Save changes. The group’s own destination for that channel is removed.