Service Health event tags

This article explains the differences between Event level, Event subtypes, and Event tags in Azure Service Health.

Event tags are metadata labels that help users understand the nature of service health communications.

Event subtypes tags give you more information about what aspect of that issue is involved.

Event level tags categorize the severity of these events into informational, warning, and critical.

Event tags help users understand the type of action required, while event levels indicate the urgency and effect of the issue, and the subtype events give more information about the issue. Together, they enable more effective management of service communications.

Event tags

Event tags are metadata labels attached to individual service health communications to help you quickly understand the nature and status of an event. These tags are predefined and include:

• Action Recommended - Indicates that user action is needed.
• False Positive - Marks events that were later determined to be nonissues.
• Preliminary PIR - Refers to Post-Incident Reviews (PIR) that provide an early summary of the root cause and resolution.
• Final PIR - Refers to post-incident reviews that provide the final summaries of the root cause and resolution.

These tags are visible on the Azure Service Health portal and are especially useful for customers managing many subscriptions, helping them filter and prioritize which events to focus on.

For example, tags like “Action Recommended” are often highlighted in red to draw attention.

Event subtypes

Event subtypes are more granular classifications within each event type. They help further specify the nature of the event and can tell you specifically what aspect of that issue is involved.

For example:

A Health advisory displays a Retirement (subtype) indicating a product is being phased out.

A Billing update might have an FX Rate Change (subtype) indicating adjustments in foreign exchange rates that affect billing.

These subtypes can help you filter information and set up automatic replies or actions based on specific criteria.

Event levels

Event level tags are a separate metadata field used to help users assess the severity of a service health event. It categorizes events into:

• Informational - No current impact, but potential future issues.
• Warning - Possible service problems that could affect performance or availability.
• Critical - Immediate attention is required due to widespread issues.

Unlike event tags, which describe the type or status of the communication, event level tags indicate the urgency and impact of the event. This field is available on the Service issues, Security advisories, Health advisories, and Billing updates panes, and can be used to filter and sort events for better prioritization.

Event tags, Event levels, and Event subtypes are shown on the following panes:

For more information on Event level tags, see Filter Service Health notifications by event level.