Most FinOps initiatives operate reactively: a CFO receives an unexpectedly high cloud bill, flags the cost spike, and platform engineers spend days retroactively hunting down unattached disks or over-provisioned clusters. Simply asking developers to "care about cloud costs" without providing automated, real-time feedback loops rarely changes engineering behavior.

This session reframes cloud cost management as a platform engineering discipline: FinOps-as-Code. Instead of relying on monthly audit reports, platform teams can embed financial guardrails directly into Infrastructure-as-Code (IaC), CI/CD pipelines, and Kubernetes node provisioning.

We’ll explore practical patterns for automated cloud cost control on Azure Kubernetes Service (AKS), leveraging Karpenter for dynamic, cost-optimized node management, automated policy enforcement, and shift-left cost estimation.

Key Takeaways:
- How to move FinOps from reactive monthly auditing to proactive CI/CD enforcement.
- Implementing dynamic, cost-aware Kubernetes node scaling with Karpenter on AKS.
- Practical techniques to give developers immediate cost visibility before infrastructure is ever provisioned.