Setting the file. One moment.
Subchapter 24.34
prepare/references/pricing-guide.mdMarkdown4 KBView on GitHub
⛔ SELF-CHECK: If
costEstimate.breakdown[]has ANYmonthlyUsd > 0, at least onepricing_getoraz restpricing API call MUST appear in this session. Estimating from memory or training data is NEVER acceptable — reference values in this file may be outdated. If API fails after 2 attempts, use the reference value WITH disclaimer:
Also bundled
PHASEdeploy"⚠️ Estimated from reference — live API unavailable."⛔ Check this FIRST. If ALL services use free-tier SKUs → write $0 cost estimate, add disclaimer “Estimate assumes usage within free grant limits”, skip to Step 7.
| Service | Free SKU | Skip API? |
|---|---|---|
| App Service | F1 | Yes |
| Static Web Apps | Free | Yes |
| Functions | Consumption (≤1M exec) | Yes |
| Cosmos DB | Free tier (1000 RU/s) | Yes |
| Container Apps | Consumption (≤180K vCPU-s) | Yes |
| SKU | skuName | Monthly |
|---|---|---|
| B1 Linux | B1 | ~$13.14 |
⛔ Case-sensitive: use
B1notb1. UseskuName(notarmSkuName) for Basic/Standard.
mcp_azure_mcp_pricing (VS Code) / azure-pricing (CLI) — with intent, command: "pricing_get", and a parameters object (NOT --flags). Parallel OK. ⛔ At least one filter inside parameters: sku, service, region, service-family, or filter. ⛔ sku matches armSkuName, not skuName — use it ONLY when armSkuName is populated (App Service, MySQL/PostgreSQL, Redis). Empty-armSkuName services (ACR, Storage, Cosmos, Key Vault) return [] or 400 for sku/service — use a raw filter on serviceName + meterName instead.unitOfMeasure (see § Monthly Multiplier) — NOT a per-service constant.retailPrice against planned SKU.⛔ Read unitOfMeasure per price record — NEVER blanket × 730 (one service mixes units, e.g. ACR returns 1/Day + 1 Second + 1 GB/Month):
unitOfMeasure | Monthly formula |
|---|---|
1 Hour / 1/Hour | retailPrice × 730 |
1/Day / 1 Day | retailPrice × 30 |
1 GB/Month | retailPrice × estimatedGB (already monthly) |
1 Second / 1 GiB Second | retailPrice × activeUnitsPerMonth (usage-based) |
10K / 1M operations | retailPrice × estimatedOps ÷ unitSize |
When AI/OpenAI/LLM components detected: add "💸 Usage-based — excluded from total" to costEstimate.breakdown[] and "⚠️🤖 AI inference costs excluded" to assumptions[]. Surface at EVERY approval gate.
See pricing-guide-services.md for per-service filter strings, meter names, and monthly formulas.
Key rules:
armSkuName is empty for most PaaS — filter by meterName or productNameunitOfMeasure (§ Monthly Multiplier) — never assume ×730isPrimaryMeterRegion eq true + priceType eq 'Consumption' — but check the service section in pricing-guide-services.md first; some drop isPrimaryMeterRegion (Service Bus, Cosmos 100 RU/s, Redis Basic).When pricing_get returns empty: (1) Check armSkuName populated/case-sensitive? (2) HTTP fallback: https://prices.azure.com/api/retail/prices?$filter={filter}. (3) After 2 failures, use pricing-guide-services.md with disclaimer. (4) Log to costEstimate.apiFailures[].
⛔ Never claim user has free credits remaining. Use: “Check balance at portal.”