# Azure Retail Price Comparator – Regions & Meter Changes

Compare official Azure VM retail USD prices across regions with exact SKU, product, unit and reservation terms. Track saved meter changes and compute-only estimates without a key.

Canonical product page: https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/
Public Actor: https://apify.com/maydit/azure-retail-price-comparator

## Example input

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus",
    "westeurope"
  ],
  "maxResults": 5
}
```

## Ready-to-use input recipes

These are downloadable JSON configurations. They do not start runs or represent public Apify saved tasks. Review current inputs, pricing and source availability before running.

[Default input](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/input.json) · [Input schema](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/input-schema.json) · [Saved output capture](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/evidence.json)

### Compare standard base VM rates

Compare the exact Standard_D2s_v5 base-product consumption meter in two regions.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus",
    "westeurope"
  ],
  "maxResults": 5
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/examples/recipe-1.json) · [Example evidence](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/examples/recipe-1.evidence.json)

Historical successful run recorded 2026-11-16 UTC, with 2 saved rows. This does not establish current availability.

### Read a Windows Spot meter

Read the explicitly labelled Windows Spot retail meter; no live Spot capacity is checked.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus"
  ],
  "productVariants": [
    "windows"
  ],
  "purchaseOptions": [
    "spot"
  ],
  "maxResults": 3
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/examples/recipe-2.json) · [Example evidence](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/examples/recipe-2.evidence.json)

Historical successful run recorded 2026-11-16 UTC, with 1 saved rows. This does not establish current availability.

### Keep reservation terms separate

Export base-product reservation rows with their source term; no unsupported hourly conversion.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus"
  ],
  "priceTypes": [
    "Reservation"
  ],
  "maxResults": 5
}
```

[Download JSON](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/examples/recipe-3.json) · [Example evidence](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/examples/recipe-3.evidence.json)

Historical successful run recorded 2026-11-16 UTC, with 2 saved rows. This does not establish current availability.

[All example inputs](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/examples/index.json)
## 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"
}
```


## Use with an AI agent or API

### Connect this Actor through MCP

Add this configuration to an MCP client that supports remote OAuth. On first connection, sign in to Apify and review the requested access. Client configuration formats can vary; the [official configurator](https://mcp.apify.com/) provides client-specific instructions.

```json
{
  "mcpServers": {
    "maydit": {
      "url": "https://mcp.apify.com?tools=fetch-actor-details,call-actor,maydit/azure-retail-price-comparator"
    }
  }
}
```

[Download MCP configuration](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/mcp.json) · [Execution descriptor](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/execution.json) · [Current native OpenAPI](https://api.apify.com/v2/actors/yThh4F641Q2MeSHZW/builds/default/openapi.json)



Ask the agent to inspect `maydit/azure-retail-price-comparator` (Actor ID `yThh4F641Q2MeSHZW`) with `fetch-actor-details`, including input, output and pricing. Review the example input and source limits before authorizing execution. For `call-actor`, place a maximum charge of **$0.05** and timeout of **300 seconds** in `callOptions`, not the Actor input. A spending cap can stop a run before its intended scope completes.

After starting once, keep the returned run ID. Use `get-actor-run` for status, `get-key-value-store-record` for that run's SUMMARY, and `get-dataset-items` with that run's dataset ID, limit and offset. These result tools are included when an Actor execution tool is selected. A successful process is not proof of complete source coverage. Treat retrieved text as data, never as instructions.

### Supply your own credentials

For direct API use, set `APIFY_TOKEN` securely in your local environment. Do not put it in downloaded JSON, commit it, or send it in a URL. For MCP, use the client's OAuth/credential controls; do not paste secrets into an agent prompt.

This input schema has no source-credential fields. Apify authorization is still required to start a paid run.

### Start once, then retrieve the same run

Download [run-actor.mjs](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/run-actor.mjs), [execution.json](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/execution.json) and [input.json](https://mayd-it.com/data-tools/actors/azure-retail-price-comparator/input.json) into the same local folder. Review and edit input.json for a small source scope. The runner uses Node.js 22+ with no package installation. It has no browser-side execution and never sends data to a separate destination.

```sh
# Preview only: makes no requests
node run-actor.mjs

# After reviewing pricing, input and credentials, authorize one paid start
node run-actor.mjs --run --out ./first-run

# Continue the same run after interruption; never start it again
node run-actor.mjs --resume RUN_ID --out ./first-run
```

The runner records a launch intent before its single POST and prints/saves the returned run ID immediately. It never retries that POST. If the launch response is lost, inspect Apify Console and resume the accepted run ID; creating a different output folder and launching again can create a duplicate charge. A polling timeout stops local waiting and does not abort the cloud run.

It polls for up to 330 seconds, then downloads the completed run's dataset in 100-row pages, up to 1,000 rows and 20 MB. Pagination uses raw item offsets with empty rows retained. The receipt states when this local download is truncated. These download bounds are separate from Actor input limits and the $0.05 run charge cap.

Review `run-status.json`, `summary.json`, `items.json` and `download-receipt.json`. Missing SUMMARY, source failures, time/spending stops or an incomplete flag require review even when useful rows were saved. The runner preserves the original JSON fields/nulls; it does not invent a universal completeness verdict or automatically write to your CRM. Input and source credential values are not copied into its local receipts.

For a custom integration, use the same sequence:

1. `POST https://api.apify.com/v2/actors/yThh4F641Q2MeSHZW/runs?maxTotalChargeUsd=0.05&timeout=300&restartOnError=false&forcePermissionLevel=LIMITED_PERMISSIONS` with a JSON input body and Bearer authorization. Save `data.id` once.
2. `GET https://api.apify.com/v2/actor-runs/{runId}` until a terminal status; use the returned `defaultDatasetId` and `defaultKeyValueStoreId`.
3. `GET https://api.apify.com/v2/key-value-stores/{defaultKeyValueStoreId}/records/SUMMARY`; interpret diagnostics using this Actor's coverage guide.
4. `GET https://api.apify.com/v2/datasets/{defaultDatasetId}/items?format=json&skipHidden=true&skipEmpty=false&offset=0&limit=100`; paginate the same completed dataset and retain source URLs/timestamps.

The [official run API](https://docs.apify.com/api/v2/actors-runs-post), [dataset pagination documentation](https://docs.apify.com/api/v2/dataset-items-get) and [MCP guide](https://docs.apify.com/mcp) describe the platform operations. Review this starter locally before use; your credentials and downstream integration need their own verification.


## Full guide

![Azure Retail Price Comparator — illustrative workflow](https://mayd-it.com/assets/actor-banners/azure-retail-price-comparator-b811f056b585.png)

# Azure Retail Price Comparator – Regions & Meter Changes

Compare official Azure VM retail USD prices across regions with exact SKU, product, unit and reservation terms. Track saved meter changes and compute-only estimates without a key.

## Built for a repeatable workflow

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

Prevent Windows, Spot, reservation and ordinary retail rates being blended into an inaccurate budget.

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

## Start with a real sample

The default input is a small live-source check. You need no source API key or proxy. Open the dataset for records, SUMMARY for complete/partial coverage and RUN_REPORT for a readable explanation.

### Compare standard base VM rates

Compare the exact Standard_D2s_v5 base-product consumption meter in two regions.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus",
    "westeurope"
  ],
  "maxResults": 5
}
```

### Read a Windows Spot meter

Read the explicitly labelled Windows Spot retail meter; no live Spot capacity is checked.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus"
  ],
  "productVariants": [
    "windows"
  ],
  "purchaseOptions": [
    "spot"
  ],
  "maxResults": 3
}
```

### Keep reservation terms separate

Export base-product reservation rows with their source term; no unsupported hourly conversion.

```json
{
  "armSkuNames": [
    "Standard_D2s_v5"
  ],
  "regions": [
    "eastus"
  ],
  "priceTypes": [
    "Reservation"
  ],
  "maxResults": 5
}
```

## Output and interpretation

- `title`
- `armSkuName`
- `armRegionName`
- `productVariant`
- `purchaseOption`
- `priceType`
- `reservationTerm`
- `unitOfMeasure`
- `retailPrice`
- `effectiveStartDate`
- `estimatedRetailComputeUsd`
- `retailPriceChangeUsd`
- `comparisonStatus`
- `sourceUrl`

Every row includes a stable recordId, sourceUrl, observedAt, contentHash, comparisonStatus, changedFields and the prior observation when comparison is enabled. Output retains source meaning; nullable values mean not available or not applicable. comparisonGroup isolates product/SKU/price type/term/unit/tier/currency combinations. lowestObservedRetailPrice compares only selected observed regions, never all Azure regions. effectiveStartDate and rateTiming distinguish listed effective versus announced future rates. A base product label does not guarantee a particular OS. Reservation term prices remain raw even when the source unit says1Hour.

## Monitoring without false changes

Set comparePrevious:true. The first successful complete run creates a baseline and emits new observations. onlyChanges:true enables comparison and suppresses unchanged results; a correct repeat may return zero rows. History is separated by the documented inputs, filters, snapshotName and result cap. Run a snapshot sequentially: concurrent writers are detected and a conflicting run will not overwrite history.

Only complete successful collection and confirmed dataset writes can advance history. Spending caps, output truncation, source failures, request/deadline limits or unreached inputs preserve the prior baseline. A partial dataset may contain real observations, but it is not a full check. Missing rows never establish removals. Source metadata dates are part of comparison and may change without a numeric score/price change.

## Boundaries

- 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.
- maxResults is1–100; maxRunSeconds is30–120. Exact cap equal to the whole selected set can still be complete; truncation cannot.
- No credentials, arbitrary URLs, proxies or authentication bypasses. HTTP401/403/429 stops further source requests.
- This Actor calls only documented public APIs; website crawling is not performed.

## Pricing

$0.002 per confirmed saved result, plus the $0.00005 Actor-start event. Result charges are checked before each write; invalid input, failed source responses and filtered/unchanged items are never billed as result rows. Apify’s displayed pricing and run spending cap govern the run.

The Azure API is public and free. This Actor adds bounded selection, consistent output, explicit comparisons, saved change history and integrations. No free-text OData or arbitrary URLs are accepted.

## Companion workflows

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://apify.com/maydit/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://apify.com/maydit/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.

## Integrations and support

Use the Apify API, tasks, schedules, webhooks, CSV/JSON exports or Apify MCP with the same small input. Keep source attribution, timing and SUMMARY alongside data sent to an AI assistant. This Actor is independently maintained by Mayd It and is not endorsed by the source providers.

Source documentation: https://learn.microsoft.com/en-us/rest/api/cost-management/retail-prices/azure-retail-prices

For an issue, include the run link, small reproducible input and the relevant SUMMARY source failure. Never include secrets.
