Reserved Instances in Azure & OCI: Save Smart, Not Sorry

Got a workload that's always-on like your coffee addiction? Reserved Instances (Azure) and Commitment Plans (OCI) are your FinOps power-ups for predictable usage.

Introduction

Reserved Instances (RIs) and capacity commitments are like cloud subscription plans β€” commit to a resource for a year or three, and the cloud gods reward you with sweet discounts (think 40–72% off vs. pay-as-you-go chaos).

This isn't about locking yourself into a cloud prison β€” it's about smart forecasting and budget control. Whether you're rolling with Azure or cooking with OCI, this guide gives you the lowdown on how to save big without breaking flexibility.

Cloud smarter, not harder. πŸ’Έβš™οΈ

Why Use Reserved Instances

Cost Savings

Reserved instances provide significant discounts compared to on-demand pricing for predictable workloads.

Up to 72% savings
1-3 year terms

Budget Predictability

Fixed pricing helps with accurate budgeting and forecasting for stable workloads.

100% predictable savings
Upfront payment options

Capacity Priority

Some reservation types provide capacity prioritization in addition to pricing benefits.

Variable savings
Capacity guarantees

Operational Simplicity

Automatic application of discounts without changes to your resources or architecture.

No management overhead savings
Automatic application
Reserved Instances vs. Savings Plans

While this guide focuses on reserved instances and capacity reservations in Azure and OCI, it's worth noting that some cloud providers offer alternative commitment-based discount models like Savings Plans. These alternatives typically provide more flexibility but potentially lower discounts compared to traditional reserved instances.

Azure offers Azure Savings Plans for compute, while OCI offers Universal Credits as a flexible commitment option.

Azure Reserved Instances

Azure offers several types of reservations that provide significant discounts on various Azure services, including virtual machines, database services, and storage.

Types of Azure Reservations

Azure offers reservations for multiple resource types, each with its own pricing model and commitment options.

Reservation TypeDiscount RangeTerm OptionsKey Benefits
Virtual Machine ReservationsUp to 72%1 or 3 yearsSignificant savings on predictable VM workloads
Azure SQL Database ReservationsUp to 55%1 or 3 yearsDiscounts on vCore-based SQL databases
Cosmos DB Reserved CapacityUp to 65%1 or 3 yearsSavings on provisioned throughput (RU/s)
App Service Stamp FeeUp to 55%1 or 3 yearsDiscounts on Isolated tier App Service plans
Azure Synapse AnalyticsUp to 65%1 or 3 yearsSavings on dedicated SQL pools (formerly SQL DW)
Azure Dedicated HostUp to 70%1 or 3 yearsDiscounts on physical servers hosting VMs

Azure: VM Reservation Example

Here's an example of potential savings with Azure VM reservations:

Scenario: D8s v3 VM in East US region

  • On-demand price: ~$280/month
  • 1-year reserved instance: ~$190/month (32% savings)
  • 3-year reserved instance: ~$120/month (57% savings)

Annual savings with 3-year reservation: ~$1,920 per VM

These savings can be substantial when applied across multiple VMs in your environment.

Reservation Scope Options

Azure offers three scope options for reservations, which determine how the reservation discount is applied.

Azure: Reservation Scope Options

Shared Scope

Reservation discount applies to matching resources in any subscription within the enrollment/billing context.

Best for: Centralized FinOps teams managing multiple subscriptions

Single Subscription

Reservation discount applies only to matching resources in a specific subscription.

Best for: Departmental subscriptions with dedicated budgets

Single Resource Group

Reservation discount applies only to matching resources in a specific resource group.

Best for: Project-specific resource groups with dedicated budgets

The shared scope option provides the most flexibility, as the discount can be applied to any matching resource across your organization, maximizing utilization of the reservation.

Exchange and Refund Options

Azure provides flexibility to adjust your reservations as your needs change.

Azure: Reservation Flexibility

Exchange Options

You can exchange an existing reservation for another reservation of equal or greater value. The remaining prorated value of the original reservation is applied to the new reservation.

Common exchange scenarios:

  • Changing VM size or series to match changing workload requirements
  • Switching between regional and zonal reservations
  • Changing the term length (e.g., from 1 year to 3 years)

Refund Options

Azure allows you to return reservations for an early termination fee (12% of the remaining reservation value, up to $50,000 per year).

Refunds are limited to $50,000 per year per enrollment/billing account.

OCI Reserved Capacity

Oracle Cloud Infrastructure (OCI) offers several commitment-based discount options that provide significant savings compared to on-demand pricing.

Compute Capacity Reservations

OCI Compute Capacity Reservations allow you to reserve compute capacity in a specific availability domain.

OCI: Compute Capacity Reservations

Key features of OCI Compute Capacity Reservations:

  • Capacity Guarantee - Ensures capacity is available when you need it
  • No Upfront Commitment - Pay only for the capacity you reserve
  • Flexible Duration - Create reservations for as long as you need
  • Specific Availability Domain - Reservations are AD-specific

Unlike Azure RIs, OCI Compute Capacity Reservations are primarily focused on capacity guarantees rather than pricing discounts. For pricing discounts, OCI offers Universal Credits commitments.

Universal Credits Commitments

OCI Universal Credits provide a flexible way to commit to OCI spending and receive significant discounts.

OCI: Universal Credits

Key features of OCI Universal Credits:

  • Flexible Spending - Credits can be used for any OCI service
  • Significant Discounts - Up to 60% off on-demand pricing
  • Commitment Terms - 1-year or 3-year options
  • Payment Options - Monthly or upfront payment
  • Overages - Usage beyond commitment is charged at discounted rates

Universal Credits Discount Example

  • 1-year commitment, monthly payment: ~33% discount
  • 1-year commitment, upfront payment: ~40% discount
  • 3-year commitment, monthly payment: ~50% discount
  • 3-year commitment, upfront payment: ~60% discount

Universal Credits provide more flexibility than traditional reserved instances, as they can be applied to any OCI service, not just specific resource types.

Bring Your Own License (BYOL)

OCI offers additional savings through its Bring Your Own License (BYOL) program for Oracle software.

OCI: BYOL Benefits

Key benefits of OCI BYOL:

  • License Mobility - Use existing Oracle licenses in OCI
  • Additional Savings - Up to 50% off the already discounted Universal Credits prices
  • Flexible Deployment - Use licenses across different deployment options
  • License Management - Centralized license management through My Oracle Support

When combined with Universal Credits commitments, BYOL can provide substantial savings for workloads running Oracle software.

Implementation Strategy

Implementing reserved instances and capacity commitments requires careful planning and analysis to maximize savings while maintaining flexibility.

6-Step Implementation Process

  1. Analyze Historical Usage

    Review 3-6 months of usage data to identify stable, predictable workloads that are good candidates for reservations.

  2. Forecast Future Needs

    Consider upcoming projects, application changes, and business growth that might affect resource requirements.

  3. Start Conservative

    Begin with reservations for 60-70% of your stable workload to avoid over-committing. You can always add more later.

  4. Mix Commitment Terms

    Use a mix of 1-year and 3-year terms based on confidence in workload stability and potential for change.

  5. Implement Governance

    Establish clear ownership, review processes, and reporting for reservation management.

  6. Monitor and Optimize

    Regularly review reservation utilization and adjust as needed to maximize savings.

Phased Approach

Consider a phased approach to reservation implementation:

  • Phase 1: Reserve core infrastructure that rarely changes (e.g., domain controllers, database servers)
  • Phase 2: Add reservations for stable application workloads with predictable usage
  • Phase 3: Optimize and expand reservations based on utilization data and changing needs

Reservation Analysis

Regular analysis of your reservation portfolio is essential to maximize savings and ensure optimal utilization.

Azure Analysis Tools

  • Azure Cost Management - Built-in reservation utilization reports
  • Azure Advisor - Provides reservation purchase recommendations
  • Reservation Utilization API - For custom reporting and analysis
  • PowerBI Templates - For advanced visualization and analysis

OCI Analysis Tools

  • Cost Analysis - Built-in cost analysis and reporting
  • Usage Reports - Detailed usage data for all resources
  • OCI Console - Reservation management and monitoring
  • Oracle Analytics Cloud - For advanced visualization and analysis

Key Metrics to Monitor

MetricDescriptionTargetAction if Below Target
Reservation UtilizationPercentage of reserved capacity being used>90%Adjust reservation scope or exchange for different resources
CoveragePercentage of eligible usage covered by reservations60-80% of stable workloadsPurchase additional reservations for stable resources
Savings RatePercentage saved compared to on-demand pricingDepends on commitment termConsider longer terms or different reservation types
Expiration ForecastUpcoming reservation expirationsNo gap in coveragePlan renewals or replacements 30-60 days before expiration
Utilization vs. Coverage

Don't confuse utilization with coverage:

  • Utilization measures how much of your purchased reservations are being used
  • Coverage measures how much of your eligible usage is covered by reservations

Low utilization suggests you've over-purchased or have mismatched reservations. Low coverage suggests opportunity to purchase more reservations for additional savings.

Reservation Automation

Automating reservation management can help optimize utilization, reduce administrative overhead, and maximize savings.

Azure Automation Options

  • Azure PowerShell - Script reservation management tasks
  • Azure Functions - Create serverless automation workflows
  • Logic Apps - Build visual automation workflows
  • Azure CLI - Command-line automation for reservations

OCI Automation Options

  • OCI CLI - Command-line automation for reservations
  • OCI SDK - Programmatic access to OCI APIs
  • Terraform Provider - Infrastructure as code for reservations
  • OCI Functions - Serverless automation for reservation management

Automation Use Cases

  • Utilization Monitoring - Automated alerts for under-utilized reservations
  • Expiration Management - Notifications and renewal workflows for expiring reservations
  • Recommendation Processing - Automated analysis and implementation of reservation recommendations
  • Reservation Rightsizing - Periodic adjustment of reservations based on changing usage patterns
  • Reporting - Automated generation and distribution of reservation utilization reports
PowerShell
# Example Azure PowerShell script to get reservation recommendations
$recommendations = Get-AzReservationRecommendation -LookBackPeriod "Last7Days" -Term "P1Y" # 1 year term

# Filter for high-confidence recommendations
$highConfidence = $recommendations | Where-Object { $_.Confidence -ge 0.9 -and $_.RecommendedQuantity -ge 1 }

# Output recommendations
$highConfidence | Select-Object ResourceType, SkuName, RecommendedQuantity, CostWithNoReservedInstances, CostWithReservedInstances, Savings

Best Practices

Planning

  • Start with stable, predictable workloads
  • Consider business cycles and seasonal variations
  • Align reservation terms with application lifecycles
  • Document reservation strategy and governance

Implementation

  • Use shared scope for maximum flexibility
  • Start with 1-year terms to minimize risk
  • Consider instance size flexibility options
  • Implement in phases to validate approach

Management

  • Review utilization monthly
  • Establish clear ownership and responsibilities
  • Create a reservation calendar for expirations
  • Automate monitoring and reporting
Reservation Maturity Model

Reservation management typically evolves through these maturity stages:

  1. Basic - Manual purchase of obvious reservation candidates
  2. Intermediate - Regular analysis and optimization of reservation portfolio
  3. Advanced - Automated monitoring, recommendations, and adjustments
  4. Optimized - Fully integrated with financial planning and application lifecycle management

Common Challenges

ChallengeImpactSolution
Workload volatilityUnderutilized reservations when workloads changeStart with shorter terms; use instance size flexibility; maintain a mix of reserved and on-demand resources
Over-commitmentWasted spend on unused reservationsBegin with conservative coverage (60-70%); gradually increase based on utilization data
Reservation management overheadAdministrative burden of tracking and optimizing reservationsImplement automation for monitoring, reporting, and recommendations
Organizational resistanceReluctance to commit to long-term reservationsStart with 1-year terms; document and share savings achievements; create clear governance
Expiration managementCoverage gaps when reservations expireCreate a reservation calendar; set up automated alerts for upcoming expirations
Overcoming Organizational Resistance

Reserved instances often face resistance due to concerns about long-term commitments. To overcome this:

  • Start small with a pilot program focused on stable workloads
  • Document and share savings achievements to build confidence
  • Create clear governance and approval processes
  • Educate stakeholders on flexibility options (exchanges, refunds)

Was this documentation helpful?

Have suggestions for improving this document? Contact us.