Read Azure pricing line items and cost fields

This lesson explains how to interpret one row in the Microsoft Azure Cloud Computing Payment Plan Comparison Dataset by reading the service name, region, configuration details, and cost columns.

Reading an estimate row

Each line item typically identifies the service, region, configuration, and one or more cost values. Start with the service name, check the region, break the configuration into type, tier, capacity, usage, redundancy, and storage, then read the displayed cost fields. Examples include Azure SQL Database in East US with a displayed cost of $1,476.43, Azure Cosmos DB at $23.36, and Azure Database for MySQL at $128.47.

Configuration examples

• Azure SQL Database: single database, vCore/general-purpose provisioned compute, Gen 5, 730 hours, and 32 GB storage.
• Azure Cosmos DB: manual provisioned throughput, single-region write in East US, 400 RU/s for 730 hours, periodic backups, and no dedicated gateway.
• Azure Database for MySQL: single-server deployment, general-purpose tier, 2 vCores for 730 hours, and 5 GB storage.
• VPN Gateway: basic tier with tunnel counts and zero gateway hours.
• Azure DDoS Protection: protection for 100 resources, shown at $2,943.55.
• Storage Accounts: block blob storage, General Purpose V2, LRS redundancy, hot tier, reserved capacity, and operation counts.

Cost interpretation

Some detailed rows show $0.00, so never infer cost from the presence of a service alone. Verify the amount in the cost columns. The estimate shows a total of $26,404.31, prices in USD, and a disclaimer that it is a summary estimate rather than a quote. Review the estimate date and use current Azure pricing for present-day decisions.

Checklist

1. Identify the service.
2. Find the region, including any region embedded in the configuration.
3. Parse type, tier, size, usage, redundancy, and storage.
4. Read each cost field and distinguish zero from nonzero amounts.
5. Use the total, currency, date, and disclaimer for context.