We encountered a support case where a customer using Azure Database for PostgreSQL Flexible Server was unaware of when planned maintenance occurred and what steps they could take to stay informed. This blog explains how notifications work, why some users miss them, and best practices to ensure you never miss critical updates.
Co‑authored with HaiderZ-MSFT
Symptoms
- Customer reported no visibility into the timing of planned maintenance.
- Uncertainty about how to receive alerts or verify maintenance status.
Root Cause
Azure sends planned maintenance notifications only to subscription owners via email. If you are not a subscription owner, you will not receive these emails by default.
Why This Happens
Azure uses role-based access control (RBAC) for notifications. Subscription owners are considered the primary contacts for service-impacting events.
Contributing Factors
- Customer is not listed as a subscription owner.
- No Service Health alerts configured in the Azure portal for maintenance events.
Specific Conditions We Observed
- Flexible Server under a planned maintenance window.
- Customer role: Contributor or Reader (not Owner).
Operational Checks
To confirm your notification setup:
- Check your role in the subscription (Owner vs Contributor).
- Review Azure Portal → Service Health → Planned Maintenance.
Mitigation
Goal: Ensure you receive timely alerts even if you’re not a subscription owner.
Option 1: Subscription Owners
- Owners automatically receive email notifications for planned maintenance.
Option 2: Non-Owners
- Go to Azure Portal → Service Health → Planned Maintenance.
- Use Azure Service Health to view notifications about upcoming and performed scheduled maintenance on your Azure Database for PostgreSQL flexible server instance.
- Set up alerts in Azure Service Health to get notifications about maintenance events.
Post‑Resolution
Customer set up Service Health alerts and now receives proactive notifications for future maintenance windows.
Prevention & Best Practices
- Verify subscription roles and ensure critical contacts are Owners if possible.
- Standardize alert rules for planned maintenance across all environments.
- Regularly review the Service Health dashboard for upcoming events.
Why This Matters
Missing maintenance notifications can lead to unexpected downtime or delayed troubleshooting. Proactive alerting ensures operational readiness and minimizes impact.
Key Takeaways
- Issue: Non-owners don’t receive planned maintenance emails by default.
- Fix: Use Service Health alerts to stay informed regardless of role.
References
- Scheduled Maintenance - Azure Database for PostgreSQL | Microsoft Learn
- View service health notifications from the Azure portal - Azure Service Health | Microsoft Learn
- Resource Health Alerts in Azure portal - Azure Service Health | Microsoft Learn
- Create Service Health alerts for Azure service notifications in Azure portal - Azure Service Health | Microsoft Learn
Microsoft