Not receiving Service Health Alerts for Planned maintenance specific to Azure SQL DB

Hi Nate Morrical

It sounds like you're having an issue receiving notifications for planned maintenance specifically for Azure SQL Databases. Here’s what you can check or try to potentially resolve this:

Check Your Alerts Configuration: Make sure you have set up health alerts for Azure SQL Database correctly. You can do this by going to the Service Health Planned Maintenance page, then selecting Health alerts and Add service health alert. Make sure to select Azure SQL Database as the service and specify the desired regions.

Review Notification Settings: It's important to ensure that notifications are enabled for the relevant action groups. If you haven't defined any action groups, you'll need to set those up to receive notifications via email, SMS, or webhooks.

Permissions Check: Verify that you have the necessary permissions based on Azure's RBAC policies. Ensure your user role allows you to receive these notifications, especially if they need to query resource graphs.

Consult the Activity Log: Since you noted that there is maintenance happening based on the Activity Log JSON output, it’s worth double-checking that the events align with the maintenance notifications you expect.

Troubleshoot Missing Notifications: If you've confirmed everything above and still aren't receiving notifications, follow the troubleshooting steps provided in the No maintenance notification received article.

Documentation on Notifications: For more details, you can refer to the Configure advance notifications for planned maintenance events documentation for specific configurations and examples.

Hopefully, these steps help you get your notifications set up correctly! If the problem persists, let’s gather some additional details:

• What specific configurations have you set for your service health alerts?
• Are there any error messages or indications in the Azure portal when checking notifications?
• Which region are your Azure SQL Databases located in?

Feel free to share more info, and we can dive deeper!

Hello Nate Morrical,

Thanks for raising this question in Azure Q&A forum.

Not receiving Service Health alerts for planned maintenance is a very common configuration issue, and there are several specific things to check.

The most frequent reason is that the alert rule scope is misconfigured specifically, the subscription, service type, and region combination in your alert rule doesn't match the maintenance event that occurred. Planned maintenance notifications are highly scoped, meaning if your alert rule was set to monitor "Virtual Machines in East US" but the maintenance event was for "Virtual Machine Scale Sets in West Europe," you would not get notified even though the alert rule is active.

Here's a step-by-step checklist to diagnose and fix the issue:

1. Verify the alert rule covers all required event types. In Azure Portal → Monitor → Service Health → Health alerts, open your alert rule and check the Condition section. Make sure Planned Maintenance is explicitly checked as an event type. Service Issues, Health Advisories, Security Advisories, and Planned Maintenance are each separate checkboxes having one enabled does not automatically include others.

2. Avoid selecting "Global" as the region. This is a well-known gotcha when configuring the region filter, do not select "Global." Instead, select your specific regions or select "All Regions" explicitly. Global is treated as a separate region identifier and does not cover all regions.

3. Check if the alert actually fired using Azure Monitor history. Go to Azure Portal → Monitor → Alerts → Alert history. Filter by signal type "Activity Log" and check whether the alert was triggered. If it shows as "Fired" but you didn't receive the email, the issue is with the Action Group, not the alert rule itself.

4. Enable the Common Alert Schema on the Action Group. This is a subtle but critical setting. In Azure Portal → Monitor → Action Groups → your action group → Email/SMS/Push/Voice → make sure "Enable the common alert schema" is turned ON. Without this, Service Health alert emails can silently fail to deliver.

5. Check email spam/quarantine filters. Azure Service Health alert emails originate from azure-noreply@microsoft.com. Ask your IT/mail admin to verify this sender is not being blocked or quarantined by your organization's email security policies.

6. Confirm the Action Group is correctly linked. Open your alert rule and under Actions, confirm the action group is attached. It's possible the action group was deleted or accidentally unlinked after an Azure Policy update or subscription-level change.

7. For specific services like App Service or VMs, opt-in is required. Some services like Azure App Service and Virtual Machines require explicit opt-in for planned maintenance notifications they are not enabled by default. For Virtual Machines, set Event Type = Planned Maintenance and Services = Virtual Machines and/or Virtual Machine Scale Sets.azure.github+1

8. Automate alerts across all subscriptions with Azure Policy. If you manage multiple subscriptions, use Azure Policy to deploy Service Health alert rules uniformly across all subscriptions so none are missed. The built-in policy definition Deploy Service Health alerts handles this automatically.

To quickly test your setup end-to-end, go to your Action Group → Test → select "Service Health" as the sample type and trigger a test notification. If you receive the test email, your setup is correct and the issue is likely event-scope mismatch. If the test email also doesn't arrive, the action group itself needs to be fixed first.

If it helps kindly accept the answer.

Best Regards,

Jerald Felix