Cost by Region
Cost by Region breaks down spend by geographic region across Azure and AWS — for data-residency checks, spotting unexpected cross-region egress, and understanding how concentrated (or spread out) your footprint really is.
What you see
Section titled “What you see”- KPI strip — total regional spend, number of regions in use, your top region and its share, and the Azure/AWS split.
- Concentration insight — a plain-language note on whether your spend is concentrated in one region (and therefore likely low on cross-region egress) or spread across several (worth a quick check that egress and residency requirements are being met).
- Region table — every region with its Azure cost, AWS cost, total, and share of overall spend, plus a stacked bar visualizing the provider split at a glance. Click any row to expand its per-service breakdown.
Global and No region
Section titled “Global and No region”Region names arrive from the providers in inconsistent formats (westeurope vs West Europe),
and some charges have no region at all. CloudOptify normalizes all of this into one clean
dimension:
- Global — real usage by services that legitimately have no region: CDN (CloudFront / Front Door), IAM / Entra ID, DNS (Route 53 / Azure DNS), and similar. This is workload spend and sorts with the other regions.
- No region — charges the provider attributes to no region at all: tax, support plans, Marketplace purchases, reservation purchases. This isn’t workload spend, so it’s pinned to the bottom of the table and excluded from the “regions in use” count.
Expand either row to see exactly which services make it up — the bucket is always explainable.
Like every cost view, Cost by Region follows the global filter and the date range you’ve selected.
Related
Section titled “Related”- AWS per-resource cost (CUR) and Azure per-resource cost (Cost Management Export) — how to connect the billing exports this page reads from.
- Cloud Map — the visual topology view of your estate.