
Introduction
Azure SQL vCore pricing lets you choose database compute capacity more transparently than bundled purchasing models. But the advertised vCore rate is only one line on the bill.
Your final cost depends on deployment model, service tier, region, hardware generation, vCore count, compute model, storage, backup retention, redundancy, licensing, and how long the database runs.
Flexera estimates 29% of cloud spend is wasted, so pricing mistakes are common.
This guide covers current East US list-price examples, provisioned versus serverless compute, cost components, DTU comparisons, budgeting steps, and the charges people overlook.
Key Takeaways
- Price the exact region, tier, hardware, and compute model, not a generic vCore rate.
- Budget compute, storage, backup, licensing, and replicas as separate lines.
- Provisioned suits always-on production; serverless suits genuinely intermittent use.
- Compare Azure Hybrid Benefit and reservations against pay-as-you-go.
- Weigh performance and availability alongside the hourly rate.
How Much Does Azure SQL vCore Cost? (Pricing Overview)
There is no single fixed price. Microsoft prices deployment models, tiers, regions, hardware, and compute models separately. Misreading this causes three common problems:
- Budgets cover compute but omit storage, backup, replicas, or licensing.
- A low hourly rate becomes a large monthly bill when capacity runs continuously or is oversized.
- Serverless estimates miss that health checks, monitoring, or traffic can prevent auto-pause.
Typical Cost Range
The figures below are list prices from Microsoft's pricing page, retrieved November 18, 2026. They cover East US, single databases, Standard-series Gen5, pay-as-you-go, License Included, in USD. Provisioned prices are per configured database-hour, not per vCore-hour.
| Configuration | Compute price | Data storage |
|---|---|---|
| GP provisioned, 2 vCores | $0.505/hour | $0.115/GB-month |
| GP provisioned, 4 vCores | $1.009/hour | $0.115/GB-month |
| GP provisioned, 8 vCores | $2.018/hour | $0.115/GB-month |
| BC provisioned, 8 vCores | $5.436/hour | $0.25/GB-month |
| Hyperscale primary, 8 vCores | $1.462/hour | $0.25/GB-month |
| GP serverless | $0.0001450/vCore-second (about $0.5218/vCore-hour) | $0.115/GB-month |
These figures exclude billable backups, long-term retention, replicas, network transfer, support, and discounts. For a monthly equivalent, the Azure calculator assumes 730 hours, so multiply the hourly rate by that figure and add storage.

Microsoft advertises up to 55% savings from Azure Hybrid Benefit and up to 33% from reservations. Neither is guaranteed for every configuration.
Price Range 1: Small or Intermittent Workloads
What's typically included: a 2-vCore General Purpose database or a serverless configuration, plus separately billed storage.
For serverless, document the minimum and maximum vCores (the smallest minimum is 0.5, the largest maximum for General Purpose is 80) and the auto-pause delay (15 to 10,080 minutes, default 60). Paused compute costs nothing, but storage keeps billing.
Best for: development, testing, staging, proof-of-concept, and low-traffic internal workloads, but only if usage genuinely goes idle.
Price Range 2: Standard Production Workloads
What's typically included: provisioned General Purpose compute (4 to 8 vCores in the table above), provisioned storage, backup allocation, monitoring, and any required availability setup. Zone redundancy on General Purpose carries an additional charge.
Best for: steady business applications that need predictable performance, continuous availability, and a stable monthly forecast.
Price Range 3: High-Performance or Large-Scale Workloads
What's typically included: Business Critical or Hyperscale, high vCore counts, zone redundancy, read replicas, and enhanced data protection. Each can add its own cost line. The 8-vCore Business Critical rate above is more than 2.6 times the General Purpose rate.
Best for: low-latency transactional systems, high-throughput applications, large databases, and strict resilience requirements.
Key Factors That Affect Azure SQL vCore Pricing and Cost Breakdown
Cost follows technical requirements, workload behavior, availability expectations, licensing choices, and capacity consumed or reserved.
Deployment Model and Service Tier
Single databases, elastic pools, and Managed Instance are priced differently. Don't mix their rates in one comparison. Elastic pools share compute at the pool level, while Managed Instance is a separate service with near-complete SQL Server feature parity.
The three tiers differ in architecture:
- General Purpose: premium remote storage, up to 4 TB, no built-in read replica.
- Business Critical: local SSD, up to 4 TB, a primary plus three secondaries, and a free built-in read-only replica.
- Hyperscale: decoupled storage, 0 to 4 HA replicas, up to 30 named replicas. Microsoft's pages cite both 128 TB and 100 TB ceilings, so confirm the limit for your SKU.

Compute Model, vCore Count, and Hardware
Provisioned compute bills the configured allocation. Serverless bills per second of actual use between your minimum and maximum, and is available for General Purpose and Hyperscale on Gen5. It is not available for Business Critical.
Memory depends on hardware: Standard-series Gen5 provides 5.1 GB per vCore, premium-series 5.2 GB, and premium-series memory optimized 10.2 GB (Hyperscale). Hours of operation and scaling frequency also move the estimate.
Data Storage and Performance Requirements
Compute charges don't include data storage. General Purpose and Business Critical storage is provisioned separately, while Hyperscale charges for actual allocation. Budget for growth, transaction logs, temporary space, and headroom, not just today's size.
Limits scale with the tier. A 2-vCore General Purpose database allows 640 data IOPS; an 8-vCore Business Critical database allows 32,000.
Backup, Retention, and Data Protection
General Purpose and Business Critical include point-in-time restore storage equal to your maximum configured data size. You pay only for backup storage above that, and write-heavy workloads can exceed it fast.
East US rates per GB-month:
| Redundancy | Billable PITR | Long-term retention |
|---|---|---|
| LRS / ZRS | $0.10 | $0.025 |
| RA-GRS / RA-GZRS | $0.20 | $0.05 |
Default PITR retention is 7 days (configurable 1 to 35). Long-term retention runs up to 10 years and bills on actual stored data. Hyperscale uses a separate backup calculation.
Availability, Replicas, Networking, and Shared Resources
- General Purpose zone redundancy costs extra; Business Critical includes it.
- Geo-replication and failover group secondaries are billed separately.
- A DR-only geo-secondary can be designated standby to save on licensing, though other resource charges remain.
- Elastic pools complicate team-level allocation.
To handle allocation, use resource tags (they aren't inherited automatically from resource groups), Azure Cost Management exports, Azure Monitor metrics, and written allocation rules.
Licensing, Discounts, and Operational Costs
Azure Hybrid Benefit applies to provisioned vCore databases with Software Assurance-enabled licenses, not serverless. Reservations run 1 or 3 years, cover compute only (not storage, software, or networking), and don't apply to serverless. Verify stacking rules before you commit.
Costs outside the vCore line include monitoring, security, migration, testing, data transfer, and engineering time.
Azure SQL vCore Cost Breakdown
A realistic estimate follows a formula: compute + data storage + backup and retention + resilience or replication + licensing and related services. Document each assumption.
| Component | Type | What to account for |
|---|---|---|
| Initial configuration or migration | Mostly one-time | Migration tooling, schema conversion, testing, downtime planning, and professional services. Keep Azure charges separate from internal engineering effort. |
| Compute | Recurring | Provisioned vCore-hours or serverless vCore-seconds, minimum and maximum capacity, runtime, and auto-pause. |
| Data storage | Recurring | Allocated storage, growth, and tier. |
| Backup, retention, and DR | Recurring or usage-based | PITR overage, LTR, geo-redundancy, geo-replication, failover resources. |
| Scaling and replicas | Periodic | Temporary scaling, extra replicas, failover environments, and tier changes. |

Low-Cost vs High-Cost Azure SQL vCore — What's the Difference?
Higher price doesn't automatically mean better value. Match spend to measured need.
Performance
- Lower cost: fewer vCores and less memory mean lower throughput, concurrency, and burst tolerance. Test your workload.
- Higher cost: more compute, memory, and faster storage support demanding workloads when your benchmarks require them.
Availability and Resilience
- Lower cost: often no zone redundancy, no replicas, and no geographic protection.
- Higher cost: zone redundancy, HA replicas, geo-replication, and failover groups add resilience you pay for.
Cost Predictability and Flexibility
- Lower cost: a small database still gets expensive if it is oversized, runs nonstop, or sees unplanned backup and storage growth.
- Higher cost: reservations, Azure Hybrid Benefit, elastic pools, and consolidation improve value when utilization is steady. Commitments create waste when it isn't.
Long-Term Value
Under-sizing causes slow queries, incidents, emergency scaling, and engineering overhead. Premium capacity pays off only when measured performance, availability, compliance, or recovery needs justify it.
How to Estimate the Right Budget for Azure SQL vCore
Start with the workload, then choose the configuration. Not the other way around.
- Document the workload: database size, read/write mix, transaction volume, concurrency, latency targets, peaks, and growth.
- Estimate runtime: active hours, seasonal peaks, idle periods, and whether auto-pause is realistic.
- Set requirements: SLAs, backup retention, RPO and RTO, redundancy, encryption, audit, and regional rules.
- Count the supporting costs: network design, monitoring, security, migration, and the skills to operate it.
- Model long-term cost: storage and backup growth, resizing, replicas, DR, licensing, reservations, and utilization.

Then price it in the official Azure Pricing Calculator using the exact US region and configuration. After deployment, compare the estimate with Azure Cost Management and Azure Monitor data.
Model at least three scenarios: smaller, expected, and peak. One point estimate hides uncertainty.
What Most People Miss When It Comes to Azure SQL vCore Cost
Several factors outside the headline vCore price routinely inflate Azure SQL bills:
- Focusing only on the vCore rate. Storage, backup, redundancy, licensing, replicas, and continuous runtime change the bill materially.
- Missing secondary meters. Internet egress (first 100 GB/month free, then $0.087/GB for the next 10 TB in North America), Defender for SQL ($15 per instance per month), and Log Analytics ingestion for diagnostics.
- Assuming serverless is always cheaper. Frequent queries, monitoring probes, minimum vCore settings, geo-replication, failover groups, or long-term retention can block auto-pause. Always-on workloads usually cost less provisioned.
- Ignoring the wider Azure storage environment. Self-managed databases on Azure block storage bill separately from Azure SQL Database.
- Leaving block storage unoptimized. Lucidity provides real-time visibility and autonomous optimization across cloud block storage without infrastructure changes, and can lower that spend by up to 70%. It does not change native Azure SQL Database compute or storage charges.
- Sizing by maximum capacity. Review performance metrics, peak usage, and storage and backup growth before resizing or committing to a discount.

Conclusion
Azure SQL vCore cost varies with several factors:
- Deployment model, tier, and compute model
- Capacity, storage, backup, and redundancy
- Licensing, region, and usage pattern
Separate each component and validate assumptions in the official Azure Pricing Calculator.
The right configuration balances performance, availability, utilization, and long-term value, not just the lowest hourly price.
Frequently Asked Questions
What is the pricing for Azure vCores?
It depends on service, region, tier, hardware, vCores, compute model, storage, backup, and licensing. A 2-vCore General Purpose database in East US lists at $0.505 per hour before storage. Confirm rates in the Azure Pricing Calculator.
What is vCore in Azure SQL Database?
A vCore is a virtual compute core, a logical CPU, used in the vCore purchasing model. It exposes compute capacity more transparently than the bundled DTU model.
What is the difference between DTU and vCore?
DTU bundles CPU, memory, and I/O into preset tiers. vCore separates compute and storage and supports serverless, Azure Hybrid Benefit, and reservations where eligible. Rough guide: at least 1 vCore per 100 Basic/Standard DTUs.
What are the limits for vCore in Azure SQL Database?
Limits vary by deployment model, tier, hardware, size, and capacity settings. Gen5 provisioned General Purpose and Business Critical scale to 128 vCores. Check Microsoft's current limits for your configuration.
How do I improve Azure SQL Database performance?
Tune queries and indexes first, and use Query Store and automatic tuning to find problems. Then confirm service tier, vCore, memory, and storage sizing against monitoring data. Test before paying for more capacity.
Is Azure SQL different from SQL?
SQL is a database language. Azure SQL is Microsoft's managed SQL Server services: Azure SQL Database, Managed Instance, and SQL Server on Azure VMs. VMs give OS control and bill VM and disks separately.