Before you begin
- The Administrator role for the Notifications page (every user can set their own preferences under My Preferences)
- A webhook URL (Microsoft Teams, Slack, or a generic HTTPS endpoint) and/or an SMS provider account (Twilio or Azure Communication Services) if you want those channels
Alerts Active switch and summary
The page header carries the Alerts Active switch. Turning it off asks you to confirm (Pause all alerts?) and then suppresses every alert delivery until you switch it back on; your rules and webhooks are kept. Below the header, four tiles show Active Rules, the number of alerts triggered in the selected window, Critical alerts, and Active Webhooks. The page then splits into four tabs: Alert Health, Notification Channels, Delivery History, and Settings.
Alert Health and alert rules
Alert Health lists every alert rule with its category, severity, status, and when it last triggered. Status reads Triggered, Noisy (fired three or more times in the window), Inactive (enabled but quiet), or Disabled, and you can search, filter, export the list to CSV, or test, edit, and enable or disable a rule from its row. Rules marked System-managed are raised by Atlas's built-in monitors and are always on. The Settings tab holds the Alert Rules card, where you set each rule's threshold, duration, and severity and click Save Rules, and the Alert Cooldown card, which suppresses repeat alerts for a set number of minutes (10 by default).
Notification destinations (webhooks)
On the Notification Channels tab, Notification Destinations lists your webhooks. Click Add Webhook and enter a name, a type (Teams, Slack, or Generic), and an HTTPS webhook URL. Each row shows the masked URL, whether it is Active, its last test result, and a delivery success rate, with Test, edit, and delete actions. The key icon on a row shows its signing secret: every delivery is signed with HMAC-SHA256, so a generic endpoint can verify that a request really came from your Atlas deployment.
Email appears next to Add Webhook marked Soon: email is not yet a notification channel. Use Email Settings for outbound mail and scheduled report delivery.
SMS / text notifications
The SMS / Text notifications card, also on the Notification Channels tab, sends alerts by text message. Click Add SMS target, choose a provider (Twilio or Azure Communication Services), and enter the recipient number in E.164 format (for example +15551234567), the sender, and the provider details (Account SID and auth token for Twilio, or the ACS endpoint and access key). Every SMS target receives all alerts. Each target has an on/off switch, a Test action, and delete.
The provider credential is written to Azure Key Vault and is never stored in the app or shown again. On a GCC High tenant, SMS and webhook deliveries to endpoints outside the Government boundary are blocked by default until an operator attests that each destination is approved; the page shows a notice explaining this.
Delivery history and failures
The Delivery History tab shows Recent Alerts, with a filter for the last hour, 24 hours, or 7 days and a Load more button; each entry is marked Delivered or Failed. When a webhook delivery fails, a Recent Delivery Failures panel appears above it. Failed deliveries are retried automatically every minute, up to six attempts, and each row shows the next retry time and a Retry button to send it again straight away.
Your own notification preferences
Every user can decide which alerts reach their own notification bell. Open My Preferences and go to Notifications: under Choose what notifies you, turn a category off (for example Cost & licensing or Software updates) to stop its alerts reaching your bell and unread badge. This affects only you; alerts are still generated for the tenant and still go to webhooks and SMS. The Sound alerts card can play a siren, alarm, or chime in this browser when a new alert arrives, which suits a monitoring screen.