i
Use a short label that can travel with exported estimate data. i
Example estimate settings Lean web platform, monthly USD, starter catalog Preset and basis controls must update totals, tables, and JSON together.
Lean web platform
Catalog Starter Azure mix Virtual Machines use a compact purchase-model catalog. Storage, Azure Functions, API, and egress use visible starter rates that you can override.
Output USD monthly run rate Use the result as a planning estimate, then verify material decisions in Azure pricing, billing, or agreement data.

Azure VM Compute

VM count, runtime, and purchase model.

D2s v5 - 2 vCPU - 8 GiB
Pay-as-you-go

Custom size uses the VM hourly override in Custom. Set the custom vCPU and memory here, then price it with the override field.

Managed Disk Storage

Premium SSD-style capacity plus optional IOPS and throughput.

Blob Storage

Object storage, request volume, and outbound transfer.

Azure Functions

Requests, duration, and memory drive the bill.

API Management

HTTP and REST requests with response egress.

Consumption gateway

Shared Egress And Overhead

Network, support uplift, and blended buffer.

Custom
Use direct overrides below when you know the real regional rate.

Virtual Machines

Managed Disks

Blob Storage

Azure Functions

API Management

Network

Build an estimate to review line-item cost drivers, service mix, and exportable JSON.

Line-Item Breakdown

# Service Driver Usage Unit basis Monthly Annual Copy

Service Mix

# Service Monthly Annual Share Signal Copy

Assumptions

# Assumption Value Note Copy

Recommendations

Methodology

JSON Output Exported estimate state should include inputs, assumptions, line items, totals, and generated output.