Azure Platform Event / Maintenance Risk
Surface known or emerging Azure platform events before they become customer incidents.
Unacknowledged
Risk score
48/ 100Elevated
+13 vs. 24h ago
Status
Elevated risk
Confidence: 90%
Estimated lead time
~3–6 hours
Based on current trend
Risk score trend
Evidence
Scheduled Eventsazure
Planned host maintenance on 6 VMs in East US 2, zone 1
Service Healthazure
Advisory: storage degradation under investigation, East US 2
How this risk score works
- What it is
- A 0–100 estimate of how likely Azure Platform Events are to cause customer impact soon. Higher means more signals are moving away from normal at the same time.
- How it is calculated
- Each signal is compared with its own baseline (same hour, last 14 days). The further it is above baseline, the more points it adds, up to a fixed weight per signal. The points add up to the score, capped at 100. Method: event ingestion + topology mapping + severity rules.
- This score
- Scheduled host maintenance +22, Service Health advisories +12, Resource Health degraded +9, other signals +5 = 48 (Elevated), +13 vs. 24h ago.
- 0–25 Normal26–50 Elevated51–75 High76–100 Critical
- What it tells you
- Impact is likely in ~3–6 hours if the trend continues. Start with Scheduled host maintenance, which adds the most points. Confidence 90% reflects how many expected data feeds reported.
Contributing signals
Score breakdown48 / 100
| Signal | Current | Baseline | Points | Impact |
|---|---|---|---|---|
| Scheduled host maintenance | 6 VMs | 0 | +22 | high |
| Service Health advisories | 1 active | 0 | +12 | medium |
| Resource Health degraded | 2 | 0 | +9 | medium |
| Platform change events (24h) | 3 | 1 | +5 | low |
Affected resources (4)
| Resource | Type | Region / AZ | Current Risk |
|---|---|---|---|
| rg-anq-prod-eus2-c0217 | Qumulo Cluster | East US 2 / 1 | 72 |
| vm-anq-c0217-n01 | Virtual Machine | East US 2 / 1 | 52 |
| vm-anq-c0217-n02 | Virtual Machine | East US 2 / 1 | 48 |
| rg-anq-prod-cus-c0609 | Qumulo Cluster | Central US / 1 | 35 |
Affected clusters (2)
| Cluster | Resource group | Current Risk |
|---|---|---|
| ANQ-0217 · Life Sciences | rg-anq-prod-eus2-c0217 | 72 |
| ANQ-0609 · Financial Services | rg-anq-prod-cus-c0609 | 35 |
Recommended actions
- 1Confirm the maintenance window for the 6 affected VMs and check redeploy options.
- 2Check whether affected Qumulo nodes can be drained before the window.
- 3Notify exposed customers if maintenance overlaps their peak hours.