Weekly briefing

Week of September 7, 2026

Review idle disks before deletion, and keep cost reports comparable

Check disk ownership before approving removal, separate GPU invoice costs from consumption costs, and keep tag compliance separate from allocated spend. These guides help storage owners and finance teams decide what needs review.

1AWS

Review EBS volumes before approving removal

Deleting an EBS volume by status alone can lose needed data. Verify ownership and retention for every volume marked available before approving removal.

Who this affects

For AWS storage owners, DescribeVolumes provides a review list, not proof of waste, charges or deletion approval. CreateTime does not show how long a volume has been available.

What to do

Read the guide, or ask an authorized AWS colleague to run its read-only inventory for your account and Region. Request JSON results, account, Region and run time, then compare VolumeId values with ownership and retention records.

Read guide
This does not apply if: Skip a fresh inventory if you already have current available-status results for the same AWS account and Region. Use those results for ownership and retention review.
Source: docs.aws.amazon.com
2Multi-cloud

Choose billed or effective cost for GPU reporting

Purchase timing can look like GPU savings if reports mix cost measures. Use EffectiveCost for consumption trends and BilledCost for invoice-aligned reporting.

Who this affects

Finance teams need both views kept distinct: BilledCost reflects invoiced charges, while EffectiveCost assigns costs to consumption or commitment recognition. Their difference alone is not savings.

What to do

Read the guide. Ask an authorized billing colleague for a read-only FinOps Open Cost and Usage Specification (FOCUS) export for named providers, dates and GPU workload. Request BilledCost and EffectiveCost totals by currency, GPU row mapping, periods and commitment breakdown.

Read guide
This does not apply if: Skip this comparison if you only need an issued invoice's payable total. Reconcile BilledCost across all rows with the same InvoiceId and InvoiceIssuerName. Stop if GPU rows cannot be identified.
Source: focus.finops.org
3Multi-cloud

Keep tag compliance separate from allocated spend

Tag compliance can give a misleading picture of allocated spend. Record Azure, AWS and GCP metadata results separately before combining allocation figures.

Who this affects

Allocation owners can miss gaps: AWS tag policies do not evaluate untagged resources, GCP project labels do not automatically reach child resources, and some Azure resource types do not support tags.

What to do

Read the guide. Request dated Azure policy definitions and scope, AWS tag-policy availability and compliance results, and GCP project-label lists. Ask service owners for resource-label details below project level. Confirm comparable billing definitions before calculating a percentage.

Read guide
This does not apply if: Use an approved allocation report instead if it already covers the required clouds and scope with comparable costs, missing-metadata treatment, currencies, denominator and billing periods.
Source: www.finops.org
4Azure

Review Azure disks left behind after VM deletion

Unattached Azure managed disks keep generating storage charges after VM deletion. Review whether each disk is still needed before removing it.

Who this affects

Storage owners need to balance ongoing charges against data loss. A null managedBy property identifies an unattached disk, not disposable data.

What to do

Read the guide. Run its Azure CLI command for the intended subscription, or send the command and subscription name or ID to an authorized colleague. Request disk IDs and az disk show details, including LastOwnershipUpdateTime.

Read guide
This does not apply if: Skip this guide for unmanaged VHD page blobs in storage accounts. Their attachment status uses LeaseStatus rather than managedBy.
Source: learn.microsoft.com