Tauseef FayyazA to Z
Glossary
Every concept in this sheet, plus the smaller terms it uses. Select a concept to open its card.
A
- Actual versus amortised cost
- Actual cost shows charges when they are billed, so an upfront commitment appears as one big charge.
- Azure billing and resource hierarchy
- A billing account holds the agreement.
- Azure Policy and tag inheritance
- Azure Policy can require tags or copy them from the resource group.
B
- Billing data latency
- Cost data arrives in batches, hours behind usage, and a month keeps changing for a few days after it ends.
- Billing queries in SQL
- SQL over a billing export answers what the console cannot: cost by tag and service, top resources, week-on-week change.
C
- Cost analysis
- The Azure portal view for exploring cost at any scope, with smart views, grouping by service, resource, location or tag, actual or amortised cost, and forecasts.
- Cost Management exports
- Scheduled daily or monthly exports to Azure Storage, as CSV or Parquet: actual, amortised and FOCUS cost details, price sheets and reservation data, split into parts with a manifest.
- Cost tools on each provider
- The same FinOps job has a different tool name on each cloud.
H
- Hidden cost lines
- Charges compute-only estimates miss: data transfer, NAT gateways, load balancers, public IPv4 addresses, logs, snapshots, idle managed databases, marketplace software and the support plan.
L
- List, contracted, billed and effective cost
- List is the public price.
P
- Pricing calculators
- Free tools from each provider to estimate a design: every resource, size, hours, storage, requests and data transfer, with assumptions written down.
- Pricing units
- Every charge is a quantity times a unit price: seconds or hours for compute, GB per month for storage, requests or invocations for serverless and APIs, GB for data transfer, tokens for AI models.
T
- Tagging policy
- A short written agreement on required tag keys, allowed values, who owns each list, where tags are applied, how compliance is measured and what happens to untagged resources.
- Tagging policy template
- A starting template with five required keys, their allowed values, and how the policy is applied and measured.
- Tags and labels for cost
- Key-value pairs on resources, such as team=payments, that flow into billing data so cost can be grouped by team, product, environment or cost centre.
U
- Untaggable and shared spend
- Cost that cannot carry your tags: support, taxes, some data transfer, marketplace charges, centrally bought commitments and shared platforms.