// sample report

A typical Friday-afternoon environment.

One resource group, eight resources, zero zone redundancy. Sound familiar?

COMPOSITE SLA · YOUR ENVIRONMENT

99.631%

≈ 32.4 h/yr downtime budget · 2.4 nines · 6 resources in 1 group(s), worst-case serial

99999.999.9999.999

How critical is this workload?

TARGET UNREACHABLE WITH TIER UPGRADES. Even maxing every ladder gets you to 99.775%. This target needs architecture, not tiers: redundant sets across zones, multi-region. WAF: redundancy ↗

Worth doing (in this order):

st-assets-lrs lrs → geo-redundant −7.9 h/yr

redis-session-c1 standard → zone-redundant −4.4 h/yr

sql-orders-prod standard → zone-redundant −0.4 h/yr

Weakest links

top 5 across the environment · h/yr

#Resource · current tierCostsNext rung

vm-web-01Azure Virtual Machines · single-premium-disk · rg-shop-prod

8.8 h/yr —

st-assets-lrsAzure Storage Account · lrs · rg-shop-prod

8.8 h/yr geo-redundant −7.9 h/yr

redis-session-c1Azure Cache for Redis · standard · rg-shop-prod

8.8 h/yr zone-redundant −4.4 h/yr

appgw-edge-01Azure Application Gateway (v2) · v2 · rg-shop-prod

4.4 h/yr —

sql-orders-prodAzure SQL Database · standard · rg-shop-prod

0.9 h/yr zone-redundant −0.4 h/yr

● Unknown bucket

1 resource(s) have no published Microsoft SLA in our dataset, so we excluded them from the composite rather than guess. They're not hidden — they're just not counted.

eventgrid-topic-orders

Not counted (by design):func-webhooks-consumption

Methodology & SLA sources →

ⓘ Designed availability, not a guarantee.