I recently learned an important Azure cost lesson while deploying an AI-powered essay review app.

The app used Python, Flask, LangGraph, the OpenAI API, and several services running on Azure Kubernetes Service.

At one point, I stopped the AKS cluster because I wanted to control costs. Later, I was surprised to see more than $170 on my Azure bill.

The lesson was that stopping an AKS cluster is not the same as assuming every related cloud cost has disappeared.

AKS depends on several underlying Azure resources, such as virtual machines, disks, load balancers, public IP addresses, networking, storage, and databases. Some costs may also come from resources outside the cluster or from usage that had already been accumulated before the cluster was stopped.

For me, the key lesson was:

Stopping a cloud service is not the same as reviewing the full cloud bill.

When deploying apps to Azure, especially with AKS, it is important to regularly check Cost Management, related resource groups, node resource groups, disks, public IPs, load balancers, storage, and databases.

This experience reminded me that cloud deployment is not only about getting an app online. It is also about understanding infrastructure, monitoring cost, and choosing a setup that fits the stage of the project.

I am now much more careful about cloud cost management, especially when building MVPs and AI-powered applications.