You support mission-critical workloads across several subscriptions in North Europe and West Europe. You must: 1) Receive alerts for Azure-wide service issues impacting your selected services in those regions. 2) Be notified about planned maintenance affecting your VM hosts. 3) Track service health advisories such as feature deprecations. 4) Route different Service Health notifications to different action groups (email vs. ITSM). What should you configure?

The correct answer directly addresses all requirements using Azure Service Health, which is designed for platform-level events like service issues, planned maintenance, and health advisories. Scoping alerts to specific subscriptions, services, and regions ensures relevance, and linking to different action groups allows for varied notification methods. Resource Health alerts are mentioned as a complementary solution for individual resource health, though not a primary requirement here. Incorrect options: RSS feed parsing is a manual and less reliable method compared to native Azure Service Health alerts, and Activity Log alerts are not the primary mechanism for planned maintenance notifications. Azure Monitor metric alerts on 'ServiceAvailability' are for resource performance, not Azure-wide service issues or planned maintenance. Azure Advisor provides recommendations, not real-time service health notifications. A single Service Health alert at the tenant root without filters would be overly broad and inefficient, and relying on email subject parsing for routing is fragile. Azure Policy is for enforcing standards and compliance, not for detecting real-time service events or generating alerts for planned maintenance. Azure Monitor autoscale notifications are for scaling events, not service issues.