Before you begin
- An Atlas administrator account: the Notifications page is admin-only
- Alerting is included on Atlas AVD
Opening Notifications
In the sidebar, open Settings → Notifications. The page opens with the master switch in its header, four summary tiles (Active Rules, alerts triggered in the last 24 hours, Critical alerts, and Active Webhooks), and four tabs: Alert Health, Notification Channels, Delivery History and Settings.
The same page also appears as the Notifications tab of the Admin System page.
Alert Health: what is firing
The Alert Health tab lists every rule with its category, severity, status and when it last triggered. Filter by status (Noisy, Triggered, Inactive, Disabled), category or severity, or search by name. Each row's actions let you edit its threshold, enable or disable it, or send a test. An insights badge flags noisy rules (worth a higher threshold or longer cooldown) and enabled rules that haven't fired recently.
Rules marked System-managed are raised by Atlas's own built-in monitors and are always on; you can't disable them.
Alert rules, thresholds and cooldown
Open the Settings tab to tune the rules. Each rule has an enabled switch, a threshold, a severity (Info, Notice, Warning, Error or Critical) and, where it applies, a duration in minutes. Click Save Rules to apply your changes.
- Host Pool at Capacity (default 100% of the pool's session limit)
- High CPU (default 85% for 5 minutes) and High Memory (default 90% for 3 minutes)
- Low Disk Space (default 15% free) and High Disk Latency (default 50 ms for 5 minutes), which need the Azure Monitor Agent on your session hosts
- FSLogix Slow Profile Load (default 8 seconds) and Slow User Login (default 20 seconds)
Alert Cooldown, beside the rules, suppresses repeat alerts for the same rule within a window (default 10 minutes) so a flapping rule doesn't flood your channels.
The master switch
The switch in the page header (Alerts Active) pauses or resumes every alert notification at once. Pausing asks for confirmation; your rules, webhooks and SMS targets are kept and resume when you switch it back on.
Notification channels: webhooks
On the Notification Channels tab, click Add Webhook under Notification Destinations. Give it a name, choose a type (Teams, Slack or Generic), paste the webhook URL (it must start with https://) and click Add. Use Test to send a test message, and edit or delete a destination from its row. Saved URLs are masked, and each row shows the share of recent alerts it delivered.
Every webhook delivery is signed with HMAC-SHA256; the Signing secret action on a webhook row shows the secret and how to verify a delivery. Email as a destination type is marked Soon and can't be selected yet.
SMS / text notifications
On the same tab, SMS / Text notifications lets you receive alerts by text message through Twilio or Azure Communication Services. Click Add SMS target and enter a name, the provider, the recipient number (E.164 format, for example +14255550100), the sender and the provider credential. The credential is written to Key Vault and never shown again. Every SMS target receives all alerts, and you can pause or test each one.
Delivery History
The Delivery History tab shows Recent Alerts, the notifications Atlas sent with their delivery status, filtered to the last hour, 24 hours or 7 days. Above it, Recent Delivery Failures lists webhook deliveries that failed; Atlas retries them automatically every minute, and you can click Retry to send one straight away.