Stage 1 of 9 · 7 lessons · ~2 weeks
How cloud billing works
Learn what Azure actually charges for: the pricing units behind every line, how billing accounts, billing profiles and subscriptions relate, list versus effective cost, actual versus amortised cost, the lines nobody estimates and why cost data is always a little late.
Start: What you are billed for: time, quantity and requestsLessons· one lesson for each topic, in this order
- 1What you are billed for: time, quantity and requestsLesson
- 2Billing accounts, billing profiles and subscriptionsLesson
- 3List, discounted and effective costLesson
- 4Actual versus amortised costLesson
- 5The lines nobody estimatedLesson
- 6Billing data is late and keeps changingLesson
- 7Estimating before you buildOptionalLesson
Do this
- Open your cost tool and switch between service, region and usage type views.
- Find one line each for compute, storage, data transfer and a managed service.
- Switch between actual and amortised cost and note any difference.
- Write down how far behind your cost data is today.
- Estimate one small app in the pricing calculator and keep the estimate to compare later.
Start with· follow one of these
- CourseFreeIntroduction to FinOps (free course)
FinOps Foundation · Beginner
Free: the FinOps Foundation's own first course, so you start with the right picture of what FinOps is
- CourseFreeMicrosoft Learn FinOps modules
Microsoft · Beginner
Free: do "Get started with FinOps" now and keep the Azure module for later stages
Practise
Keep handy
Also worth your time
Before moving on: A one-page note on your own cloud bill (a student or sandbox account is fine): every line explained with its pricing unit, which view you used (actual or amortised), and three charges a compute-only estimate would have missed.

You do not need a big company bill to learn this. A sandbox account with a few dollars of spend has every kind of line in miniature. If cloud basics such as regions, VMs and networks are still new to you, do the cloud engineering roadmap at sefism.com/roadmaps/cloud-engineer/ first, then come back: FinOps is much easier when you know what each service does.