# Azure Retail Price Comparator – Regions & Meter Changes — workflow

## Choose this tool

FinOps consultants, MSPs and cloud buyers comparing retail meters before quoting or choosing a region.

Useful output columns: `title`, `armSkuName`, `armRegionName`, `productVariant`, `purchaseOption`, `priceType`, `reservationTerm`, `unitOfMeasure`, `retailPrice`.

## Practical workflow

Choose exact VM SKUs and regions. Compare only matching comparisonGroup values and read priceType, unit and reservationTerm. Export planning assumptions or repeat the same snapshot to identify changed published rates.

## Check the fit

USD retail list prices only; other cloud services and currencies are outside this first release. No negotiated bill, live inventory, deployment or savings guarantee. Cross-region comparisons include only successful observed selected meters; partial runs are explicitly marked. Only non-reservation 1 Hour meters get compute-hour arithmetic.

## Real output sample

One selected row from a 2026-11-16 run. Selected original scalar fields from one actual saved observation; nested data and private artifact links omitted.

Run: lIe2D5ZcOArAmkGhV. Summary status: ok. Incomplete: false.

Dated bounded private release evidence for this exact input/build. This does not establish current values, whole-source coverage or fleet health.

```json
{
  "recordId": "azure:1474c292c7f0b68d459f8ecdfc457c47c41fa1a6",
  "title": "Standard_D2s_v5 · eastus · base · standard · Consumption",
  "armSkuName": "Standard_D2s_v5",
  "armRegionName": "eastus",
  "productVariant": "base",
  "purchaseOption": "standard",
  "priceType": "Consumption",
  "reservationTerm": null,
  "unitOfMeasure": "1 Hour",
  "retailPrice": 0.096,
  "effectiveStartDate": "2021-11-01T00:00:00Z",
  "estimatedRetailComputeUsd": 70.08,
  "retailPriceChangeUsd": null,
  "comparisonStatus": "not_requested"
}
```

## Combine with companion tools

Each Actor runs separately with its own inputs, authorization and pricing. These instructions do not configure automatic execution.

### [GPU Cloud Rate Monitor – Runpod & Lambda Price Changes](https://mayd-it.com/data-tools/actors/gpu-cloud-rate-monitor/)

Build a compute sourcing worksheet with Azure VM meters beside separately selected Runpod/Lambda GPU rental rates.

1. Choose the relevant GPU providers and models in the companion Actor’s own input form.
2. Keep GPU-hour rates, instance-hour meters, memory, region and reservation terms in separate columns; compare a defined workload’s total costs manually.

These are retail observations with different resource allocations. They do not establish equal performance, current capacity, negotiated costs or a cheapest provider.

### [AI Model Price & Capability Monitor - Models.dev](https://mayd-it.com/data-tools/actors/ai-model-price-capability-monitor/)

Add model API rates when comparing a hosted inference API with a self-managed deployment budget.

1. Select the exact model/provider rates relevant to your workload in the companion tool.
2. Estimate token usage separately from VM hours, storage and network costs; retain units, source URLs and dates.

Token rates and VM-hour rates are different costs. This combination supplies inputs for your budget model; it does not calculate equivalent throughput or guarantee savings.
