> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/azure-faq/do-vm-reservations-cover-aks.md).

# Do Azure VM Reservations Cover AKS Nodes?

Yes, for the nodes. Azure Kubernetes Service agent nodes are [billed as standard virtual machines](https://learn.microsoft.com/en-us/azure/aks/faq), so a VM reservation applies to them like any other VM in the same region and scope. Instance size flexibility applies within the reservation's flexibility group, so the discount follows node pools that scale across sizes in the same family.

## What Isn't Covered

**The cluster management charge** on the Standard and Premium tiers. It's a per-cluster hourly fee rather than VM consumption, and no reservation applies. The Free tier carries no such charge.

**Virtual nodes** backed by Azure Container Instances, which bill as ACI rather than as VMs.

In practice the agent nodes are the overwhelming majority of an AKS bill, so reservation coverage still applies to most of the spend.

## Related Resources

* [What does Azure RI 'Instance Size Flexibility' Mean?](https://docs.archera.ai/help-center/azure-faq/instance-size-flexibility.md)
* [What Reservable Azure Services Does Archera Insure?](https://docs.archera.ai/help-center/azure-faq/reservable-services.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archera.ai/help-center/azure-faq/do-vm-reservations-cover-aks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
