A county operations lead needs advance notice of planned Azure maintenance for services the county uses. Which Azure capability is intended for that communication?
Select an answer to reveal the explanation.
Short Explanation
Planned maintenance is on Service Health's bulletin board. Advisor might help you tune VMs later, but the heads-up that Microsoft is scheduling work on a service you depend on comes from Service Health.
Full Explanation
Azure Service Health is intended to communicate planned maintenance and other Azure service health events for the services a county uses. Operations leads rely on it for advance notice so they can schedule change freezes, notify agencies, or shift traffic before Microsoft performs platform work. That proactive communication role is a staples AZ-900 Service Health theme alongside incidents and health history.
Azure Advisor rightsizing tips only fail because Advisor addresses utilization and best-practice recommendations, not Microsoft's planned maintenance bulletin for platform services. Azure Resource locks fail because locks prevent accidental delete or modify of resources; they do not announce Microsoft maintenance windows. Azure tags on resource groups fail because tags are metadata for organization and cost allocation, not a maintenance notification channel.
Exam caveat: planned maintenance entries are still personalized—verify the services and regions the county actually consumes rather than assuming every Azure maintenance event worldwide applies.
Operational check: in Service Health, open planned maintenance (or equivalent health views), filter to the county's critical services, and confirm notification contacts or action groups will receive advance alerts before the maintenance window starts.