Azure Retail Price Comparator – Regions & Meter Changes avatar

Azure Retail Price Comparator – Regions & Meter Changes

Pricing

from $1.20 / 1,000 saved observations

Go to Apify Store
Azure Retail Price Comparator – Regions & Meter Changes

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.

Pricing

from $1.20 / 1,000 saved observations

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Categories

Features

Limited permissions

Share

Azure Retail Price Comparator — illustrative workflow

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.

{
"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.

{
"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.

{
"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

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

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.