AKS Pricing Tier: Free, Standard and Premium Explained AKS pricing has two layers. The first is the cluster-management tier. The second is everything that actually runs your workloads: node VMs, disks, load balancers, public IPs, monitoring and add-ons. A free control plane does not make the cluster free.

Teams get surprised here. They pick a tier based on the fee, then find the node and storage bill dwarfs it.

This article compares Free, Standard and Premium, covers who each suits, what the fee changes, and which costs stay separate. It closes with a practical way to choose based on reliability and Kubernetes support needs. Prices are USD, East US, hourly retail, checked November 18, 2026.

Key Takeaways

  • Free removes the management fee, not the worker-node or Azure resource charges.
  • Standard is the production choice when you need a financially backed control-plane SLA.
  • Premium adds long-term Kubernetes version support; buy it only if you need that runway.
  • Nodes, storage, networking and monitoring usually outweigh the tier fee.

AKS Pricing Model Overview

Control plane versus data plane

Azure operates the control plane: the Kubernetes API server, etcd, scheduler and controllers. Worker nodes are the VMs that run your applications, with a kubelet and container runtime on each.

The tier changes management features, availability commitments and support. It does not change how workloads consume compute and storage. In every tier, Azure's AKS pricing page states that node compute and other resources are billed separately.

Tier Per cluster-hour
Free $0.00
Standard $0.10
Premium $0.60

These are management fees only, not all-in estimates. Actual prices depend on your agreement, so confirm on Microsoft's pricing page before committing.

What drives the rest of the bill

Worker-node cost depends on VM family, node count, operating system, region and scaling behavior. VM charges track VM type and running time.

Modeling it in the Azure Pricing Calculator

  1. Add Azure Kubernetes Service and choose the cluster-management tier.
  2. Enter each node pool's OS, VM instance, count and hours.
  3. Add managed OS disks (tier, size, count) in the AKS estimate.
  4. Separately add persistent disks, Load Balancer, public IPs and Azure Monitor.
  5. Add other services the workload uses, without double-counting node VMs or OS disks already in the AKS inputs.

Five-step Azure Pricing Calculator AKS cost estimation workflow

Free, Standard, and Premium AKS Tiers Explained

Attribute Free Standard Premium
Intended use Dev, test, learning Production, enterprise Production plus LTS
API-server SLA None (best effort) 99.95% with zones; 99.9% without Same as Standard
Max nodes 1,000 (under 10 recommended) 5,000 5,000
Long-term support No No Yes, with LTS plan enabled

The percentages cover the Kubernetes API server, not your application's availability.

Free tier

Free suits learning, experimentation, development, and testing. Microsoft recommends fewer than 10 nodes and positions it for nonproduction.

There is no financially backed SLA. Microsoft's internal goal of above 99.5% monthly API-server uptime is not a commitment.

Nodes, disks, and everything else still bill normally.

Standard tier

Standard adds the financially backed uptime SLA and supports up to 5,000 nodes. It is the sensible default for production and customer-facing workloads.

Note the zone distinction: 99.95% when you use Availability Zones, 99.9% without. If the SLA drives your decision, design for zones.

Premium tier

Premium includes everything in Standard plus long-term support (LTS). You need the Premium tier and the AKSLongTermSupport plan, enabled together.

The runway is approximately 24 months total from GA: one year of community support plus one year of LTS. It is not 24 additional months.

Per Microsoft's LTS documentation, once community support ends for your version you must upgrade before switching back to the regular plan.

Premium fits regulated, mission-critical, or upgrade-constrained environments. Standard's policy covers N, N-1, and N-2 minor versions with 12 months of support, so teams that cannot upgrade that fast are Premium's audience.

AKS Free Standard Premium tier capabilities and support comparison

Setting or changing the tier

  • Azure CLI: --tier free, --tier standard or --tier premium on az aks create or az aks update. Premium also needs --k8s-support-plan AKSLongTermSupport.
  • Portal: Basics > AKS pricing tier at creation.
  • Bicep/ARM/Terraform AzAPI: sku.name = 'Base' with sku.tier set to Free, Standard or Premium.

Standard can move down to Free. Moving off Premium also resets the support plan to KubernetesOfficial, subject to version eligibility. Microsoft says Free-to-Standard should not cause downtime, but it gives no blanket guarantee for every transition.

AKS Cost Drivers Beyond the Tier Fee

Worker nodes

Nodes are usually the biggest line item. The levers:

  • VM size, family and node count, including GPU SKUs for training or inference.
  • System pools need at least two nodes; Microsoft recommends three for a single production system pool. User pools can scale to zero.
  • Windows user pools can use Azure Hybrid Benefit with eligible licenses.
  • The cluster autoscaler removes underused nodes, but it scales on pod resource requests, not observed utilization. Inflated requests keep nodes alive.

Persistent storage

Disk cost follows type, provisioned size, performance tier, snapshots and redundancy:

  • Premium SSD, Standard SSD and Standard HDD bill on provisioned size
  • Premium SSD v2 and Ultra also bill IOPS and throughput
  • ZRS costs more than LRS
  • Snapshots bill on used data

Azure Files bills by provisioned capacity or pay-as-you-go usage, depending on model.

The sneaky one is leftovers. Unattached managed disks keep charging, and the reclaim policy on a PersistentVolume decides whether storage is retained after deletion. Pod rightsizing does nothing about those.

For managed disks, Lucidity can give visibility into volume utilization and help optimize supported block storage without infrastructure changes. Confirm current AKS compatibility first. It does not manage the AKS tier or worker-node compute.

Networking

These bill independently of the tier:

  • Standard Load Balancer: rules and processed data.
  • Standard public IPs: hourly, and allocated static IPs charge even when unattached.
  • Egress bandwidth, and VNet peering ingress and egress.
  • Private endpoints: endpoint-hours plus data processed.
  • Application Gateway v2: fixed plus capacity-unit charges.

Add-ons and services

  • Azure Monitor and Log Analytics: ingestion and retention beyond allowances.
  • Managed Prometheus: samples ingested and queried.
  • Defender for Containers: per worker-node vCore.
  • Azure Container Registry: its own tiers, storage, geo-replication, egress.
  • AKS backup: protected instances, snapshots, backup storage.
  • AI workloads: GPU node pools provisioned for tools like KAITO; delete them to stop compute charges.

AKS additional cost categories beyond cluster management fees

Put each selected service into your estimate.

How to Choose the Right AKS Pricing Tier

A practical decision path

  1. Free: non-production work where having no financially backed SLA is acceptable.
  2. Standard: most production workloads that need dependable control-plane availability.
  3. Premium: only when extended version support is a documented business, compliance or operational requirement.

Don't decide on cluster size alone

A small cluster can be business-critical. Weigh factors beyond size:

  • Workload criticality and recovery objectives
  • Zone design and upgrade cadence
  • Regulatory needs
  • Your team's capacity to upgrade
  • What control-plane disruption would cost you

Mix tiers by environment

A sensible split:

  • Free for disposable dev and test
  • Standard for customer-facing production
  • Premium for the few clusters that truly need long-term support

Do not run production on Free just to dodge a $0.10 hourly fee. That is roughly $73 a month for a cluster, small next to the cost of an outage.

Practical Ways to Manage and Optimize AKS Costs

Rightsize first

Review pod CPU and memory requests; oversized requests waste capacity.

Autoscalers cover different layers:

  • Vertical Pod Autoscaler tunes request sizes
  • Horizontal Pod Autoscaler adjusts replica counts
  • Cluster autoscaler adds or removes nodes

Fewer replicas do not guarantee fewer nodes. Split workloads into suitable node pools, then buy commitments.

Discounts and stop/start

Option Stated savings Watch for
Reserved VM Instances Up to 72% 1- or 3-year term, specific VM and region
Savings plan for compute 11%-65% Hourly commitment billed regardless of usage
Spot VMs Up to 90% Eviction risk, no SLA, secondary pools only

These are VM discounts, not whole-cluster savings. Stopping a cluster saves compute and preserves state for up to 12 months, but disks and static public IPs keep billing. It works for VM Scale Set-backed clusters, not Node Auto Provisioning. Restarts can hit capacity limits.

Azure VM discount options savings and usage risks comparison

Governance

  • AKS cost analysis allocates costs by cluster and namespace. It needs Standard or Premium and an Enterprise Agreement or Microsoft Customer Agreement; enable with --enable-cost-analysis.
  • Tags alone don't split shared-resource usage across teams.
  • Budgets alert on actual or forecast spend but won't stop resources.

Optimize compute, storage, networking, and observability separately. Each has different levers.

Conclusion

Tier pricing buys control-plane management, availability assurance and Kubernetes support. It does not replace budgeting for nodes, storage, networking, monitoring and add-ons.

In short: Free for experiments, Standard for production, Premium when long-term version support is required. Verify current rates and features in Microsoft's documentation and the Azure Pricing Calculator before you deploy or migrate.

Frequently Asked Questions

What is included in the AKS free tier?

Free removes the cluster-management fee. Workloads still pay for node VMs and any storage, networking, monitoring or security resources they use.

Is AKS considered PaaS?

Microsoft describes AKS as a mix of IaaS and PaaS with a fully managed control plane. You still own workload configuration, node patching coordination, version upgrades, identities and resource consumption.

What is the difference between AKS Free and Standard tiers?

Standard costs $0.10 per cluster-hour and adds a financially backed API-server SLA for production use. Free has no SLA. Both bill underlying Azure resources.

Does AKS Premium include long-term support?

Yes, when the AKSLongTermSupport plan is enabled, for roughly 24 months total from GA. Check current eligible versions in Microsoft's documentation.

What does AKS charge for besides the control plane?

Worker-node compute, persistent storage, networking and egress, monitoring, Defender, container registry, backup and any other enabled Azure services.

How can I estimate my total AKS cost?

Model the tier, node pools, storage, networking, monitoring and add-ons in the Azure Pricing Calculator. After deployment, validate actual usage in Azure Cost Management.