After a platform incident, a city compliance officer wants to review Microsoft's status history and related communications for services the city uses. Which service family supports that describe-level need?
Select an answer to reveal the explanation.
Short Explanation
Service Health keeps the story of what happened on Azure's side—status, history, and follow-up communications. Compliance folks lean on that when they need a clear record of platform events.
Full Explanation
Azure Service Health, including related health history views, supports a city compliance officer who needs Microsoft's status history and communications after a platform incident. At describe depth, Service Health provides personalized incident details, planned maintenance records, and historical context for services the city uses—material that helps explain impact windows during audits or after-action reviews.
Azure Advisor alone without any health portal fails because Advisor recommendations are not a substitute for Microsoft platform incident history. Azure Pricing Calculator export history fails because calculator estimates are not operational incident records. Azure Bastion session recordings only fail because Bastion provides secure remote access to VMs; it is not the repository of Azure service health history for compliance storytelling.
Exam caveat: Service Health history documents Microsoft's service events; it does not replace the city's own change tickets, application logs, or business impact assessments required for a full compliance narrative.
Operational check: after an incident closes, open Service Health history for the affected service and region, save or note the official timeline and RCA communications Microsoft provides, and attach them to the municipal incident record alongside internal Monitor evidence.