Background
RealTheory can use Azure Stock Keeping Units (SKUs) to calculate cost data when your environment uses non-standard or negotiated pricing—such as an Enterprise Agreement (EA), Microsoft Customer Agreement (MCA) discounts, or specific negotiated rates—rather than standard retail pricing.
SKU names categorize services and map them to their associated pricing, including virtual machine nodes, managed storage disks, and bandwidth. You provide SKU names using exact strings or wildcards (*) in a comma-separated list. If multiple SKUs could match a resource, RealTheory applies the first matching SKU in the table. Use the drag-and-drop handle to reorder rows and control matching priority.
The rest of this topic provides guidance on how to specify SKU names for the various sections of the SKU rate card:
Node SKUs
Storage SKUs
Network SKUs
Load Balancer SKUs
Kubernetes Management Service SKUs
Node SKUs
Node SKUs must reference valid Azure virtual machine (VM) sizes. Use wildcards to match entire VM series or specific hardware capabilities (such as premium storage or local temp disks).
Examples
| SKU Name | Matches |
|---|---|
| Standard_D2s_v3 | Only Standard_D2s_v3 VM sizes |
| Standard_DS*_v2 | All DS-series v2 VM sizes |
| Standard_E*ds* | All generations of the E-series with local disks and premium storage |
| Standard_F*s_v2 | All F-series v2 VM sizes |
Storage SKUs
Storage SKUs must reference the managed disk type and redundancy model backing your Kubernetes Persistent Volumes.
Examples
| SKU Name | Matches |
|---|---|
| Standard_LRS | Standard HDD with local redundancy |
| StandardSSD_LRS | Standard SSD with local redundancy |
| StandardSSD_ZRS | Standard SSD with zonal redundancy |
| PremiumSSD_LRS | Premium SSD with local redundancy |
| PremiumSSD_ZRS | Premium SSD with zonal redundancy |
Network SKUs
Network SKUs represent the pricing categories used for data movement. Azure distinguishes between traffic across Availability Zones, Regions, or to the public Internet.
Configuration Requirement:
When using the Inter-Region Transfer In or Inter-Region Transfer Out SKUs, you can optionally specify the following key/value pairs in Properties:
source=<region>destination=<region>
where <region> is the Azure region code (for example, eastus, westeurope) that corresponds to the source or destination of the cross-region traffic.
Examples
| SKU Name | Applies to... |
|---|---|
| Inter-Availability Transfer In | All incoming traffic received from a different Availability Zone in the same region |
| Inter-Availability Transfer Out | All outgoing traffic sent to a different Availability Zone in the same region |
| Inter-Region Transfer In | All incoming traffic received from a different Azure region |
| Inter-Region Transfer Out | All outgoing traffic sent to a different Azure region |
| Internet Transfer In | All incoming traffic arriving from the public internet |
| Internet Transfer Out | All outgoing traffic leaving the Azure network for the public internet |
Load Balancer SKUs
Load Balancer SKUs must match the specific type of load balancer provisioned by your Kubernetes Service objects.
Examples
| SKU Name | Applies to... |
|---|---|
| Standard | Standard Load Balancer |
| Gateway | Application Gateway or Gateway Load Balancer |
Kubernetes Management Service SKUs
Kubernetes Management Service SKUs must reference the Azure Kubernetes Service (AKS) management tiers.
Examples
| SKU Name | Tier |
|---|---|
| Standard | Standard Tier |
| Automatic | AKS Automatic |