Cloud cost decisions,
grounded in evidence

What AWS, Azure and Google Cloud emissions data covers, where it sits in ESRS E1 and which gaps remain. CSRD scope after the 2026 Omnibus.

Who NIS2 covers, which Article 21 measures create cloud cost, and how to budget logs, backups, keys and MFA. Status as of October 2026.

The cloud cost lines DORA creates for financial entities and their SaaS suppliers: register, Article 30 contracts, exit plans, testing and logs.

Map egress, cross-AZ, inter-Region and NAT charges in CUR 2.0: usage types, Frankfurt list prices, a SQL query, flow logs and fixes.

AWS, Azure and Google Cloud compared: latency, thresholds and recipients for budget, forecast and anomaly alerts, with a decision table.

Three layers for AI feature costs: deployments and inference profiles, tags and identities, and token logs reconciled to the bill.

Read Azure OpenAI meters and Bedrock usage types, spot PTU and model-unit charges, and prepare allocation with resources, profiles and tags.

Rule out data artefacts, narrow the increase to a resource, separate volume from rate and prove the cause: a diagnostic sequence with worked SQL.

Separate non-production spend, schedule idle time, expire previews and review monthly: tables, YAML and a checklist for AWS, Azure and GCP.

Production, platform, development, data, AI inference and credits: a classification table and rules that finance and auditors can follow.

Database, cluster, queue, observability: which key fits each shared component, what AWS, GKE and AKS provide, and how totals stay exact.

Direct cost, a measured usage driver and a visible remainder: build a defensible per-customer number from FOCUS billing data and product usage.

Switch AWS to euro billing, see how Azure and Google Cloud fix the billing currency by agreement, and which rate and payment method the invoice uses.

Which cloud costs could qualify under HGB, IAS 38 or FRS 102, the evidence engineering must keep, and a questionnaire for your adviser.

Build the 2027 cloud budget from twelve months of billing data: cleaned baseline, cost drivers, scenarios, monthly phasing and a formula template.

Which entity bills you, when reverse charge applies, where to enter your VAT number, and an invoice check for AWS and Azure in the EU and UK.

Distribute node cost to namespaces by requests and usage, keep idle visible and avoid double counting: the method and the cluster agent.

When AWS and Azure cost data settles, a reconciliation sheet per provider, and the evidence finance needs before deciding on an accrual.

Detailed BigQuery export in the EU multi-region: roles, backfill from the previous month, a cost and credits query, and keyless dataset access.

What ends for switching charges on 12 January 2027, which costs remain, which provider programmes apply now and what FinOps should evidence.

Executive Strategy Alignment, six renamed capabilities and Scopes as decision contexts: what a small team should actually adopt.

A practical framework for the EU Data Boundary, Sovereign Public Cloud, Azure Local, and a defensible architecture cost baseline.

When CUR 2.0 is right for AWS detail, when FOCUS 1.2 provides the better shared cost model, and when running both is justified.