πŸ”’ Guided

Pre-launch preview. Authorised access only.

Incorrect code

Guided by A Guide to Cloud
Explore AB-900 AI-901 aws-aif-c01
Guided AZ-120 Domain 4
Domain 4 β€” Module 6 of 7 86%
27 of 28 overall

AZ-120 Study Guide

Domain 1: Migrate SAP Workloads to Azure

  • SAP on Azure: The Big Picture Free
  • Assessing SAP Workloads for Migration Free
  • Migration Strategies: The Decision Framework Free
  • RISE with SAP on Azure Free
  • Migration Execution: DMO, Classical, and Beyond Free
  • HANA System Replication for Migration Free
  • Post-Migration: Validation, Health, and HLI Migration Free

Domain 2: Design and Implement an Infrastructure to Support SAP Workloads

  • SAP-Certified Virtual Machines on Azure
  • Storage Architecture for SAP on Azure
  • Networking for SAP on Azure
  • HANA Architecture on Azure
  • SAP Application Tier on Azure
  • Proximity Placement and Availability Options
  • Azure Center for SAP Solutions (ACSS)
  • SAP Deployment Automation Framework (SDAF)

Domain 3: Design and Implement High Availability and Disaster Recovery

  • High Availability Concepts for SAP
  • High Availability for ASCS/SCS
  • HANA System Replication for HA
  • Shared Storage and Load Balancer Deep Dive
  • Disaster Recovery Strategy for SAP
  • Disaster Recovery Implementation

Domain 4: Maintain SAP Workloads on Azure

  • Azure Monitor for SAP Solutions
  • Backup for SAP HANA
  • Backup for SAP Application Servers
  • Security and Encryption for SAP
  • Microsoft Sentinel for SAP
  • Cost Optimization for SAP on Azure
  • SAP Operations and Lifecycle Management

AZ-120 Study Guide

Domain 1: Migrate SAP Workloads to Azure

  • SAP on Azure: The Big Picture Free
  • Assessing SAP Workloads for Migration Free
  • Migration Strategies: The Decision Framework Free
  • RISE with SAP on Azure Free
  • Migration Execution: DMO, Classical, and Beyond Free
  • HANA System Replication for Migration Free
  • Post-Migration: Validation, Health, and HLI Migration Free

Domain 2: Design and Implement an Infrastructure to Support SAP Workloads

  • SAP-Certified Virtual Machines on Azure
  • Storage Architecture for SAP on Azure
  • Networking for SAP on Azure
  • HANA Architecture on Azure
  • SAP Application Tier on Azure
  • Proximity Placement and Availability Options
  • Azure Center for SAP Solutions (ACSS)
  • SAP Deployment Automation Framework (SDAF)

Domain 3: Design and Implement High Availability and Disaster Recovery

  • High Availability Concepts for SAP
  • High Availability for ASCS/SCS
  • HANA System Replication for HA
  • Shared Storage and Load Balancer Deep Dive
  • Disaster Recovery Strategy for SAP
  • Disaster Recovery Implementation

Domain 4: Maintain SAP Workloads on Azure

  • Azure Monitor for SAP Solutions
  • Backup for SAP HANA
  • Backup for SAP Application Servers
  • Security and Encryption for SAP
  • Microsoft Sentinel for SAP
  • Cost Optimization for SAP on Azure
  • SAP Operations and Lifecycle Management
Domain 4: Maintain SAP Workloads on Azure Premium ⏱ ~12 min read

Cost Optimization for SAP on Azure

Reduce SAP on Azure costs with Reserved Instances, Savings Plans, right-sizing, non-production snoozing with Automation runbooks, constrained vCPU VMs for SAP licensing, Azure Hybrid Benefit, and Cost Management tools.

Making SAP affordable

πŸ”§ Aisha opens the cost report. β€œTradeCorp’s SAP environment costs over 50,000 USD per month β€” production HANA, application servers, non-production systems, storage, networking, and backups. Carlos wants to cut that by 30 percent without impacting performance or availability.”

Carlos confirms. β€œThe CFO is asking hard questions. We need a cost optimization plan that the finance team can understand.”

β˜• Simple explanation

Think of it like reducing your household electricity bill.

You can negotiate a fixed-rate contract (Reserved Instances) instead of paying variable rates. Turn off lights in rooms you are not using (snooze non-prod VMs). Replace old appliances with energy-efficient ones (right-size VMs). Use a smart meter to see where the money goes (Cost Management). And if you have solar panels from another house (Windows Server licenses), bring them with you (Hybrid Benefit). Each saves a bit β€” together they save a lot.

SAP on Azure cost optimization operates across multiple levers: compute reservations (Reserved Instances, Savings Plans) for 30-60 percent discount on committed workloads; right-sizing using AMS and Azure Monitor data to match VM sizes to actual usage; scheduling (snooze non-production VMs during off-hours); SAP licensing optimization (constrained vCPU VMs to reduce per-core license costs); storage optimization (right-tier storage, delete orphaned disks); and Azure Hybrid Benefit for reusing existing Windows Server or SQL Server licenses. Cost Management and Advisor provide visibility and recommendations.

Reserved Instances and Savings Plans

Cost commitment options for SAP
FeatureReserved Instances (RI)Savings Plans
CommitmentSpecific VM size and regionHourly compute spend (any VM size/region)
DiscountUp to 72 percent (3-year)Up to 65 percent (3-year)
FlexibilityExchange or cancel with restrictionsAutomatically applies to cheapest eligible resource
Best forProduction SAP VMs that will not change sizeDynamic workloads or VMs that may be resized
Term1-year or 3-year1-year or 3-year
SAP recommendationHANA production VMs (M-series β€” stable size)Application servers (may scale up/down)

πŸ”§ Aisha calculates. β€œOur production HANA M192ms will not change for at least 3 years. That is a perfect fit for a 3-year Reserved Instance β€” saving us about 60 percent on compute. The application servers might be resized as user count changes, so Savings Plans give us more flexibility there.”

πŸ’‘ Exam tip: RI for stable, Savings Plans for dynamic

The exam tests whether you know when to recommend Reserved Instances vs Savings Plans. The key: RI locks you to a specific VM size for maximum discount. Savings Plans commit to a spend level with flexibility to change VM sizes. For SAP HANA (stable size), RI is ideal. For app servers (may scale), Savings Plans work better.

Right-sizing with monitoring

Right-sizing means matching VM resources to actual workload demands:

  1. Collect data β€” use AMS and Azure Monitor to track CPU, memory, and I/O utilization over 30+ days
  2. Identify over-provisioned VMs β€” if a VM consistently uses less than 50 percent CPU and 60 percent memory, it may be too large
  3. Check Azure Advisor β€” Advisor flags under-utilized VMs with specific resize recommendations
  4. Validate with SAP sizing β€” before resizing, verify the smaller VM still meets SAPS requirements
  5. Resize during maintenance β€” resizing requires VM deallocation (brief downtime)
Right-sizing caution for HANA

Never right-size HANA VMs based on CPU alone. HANA is memory-bound β€” even if CPU utilization is low, the VM needs enough memory for the entire database plus overhead. Right-sizing application servers is safer because they are compute-bound and can be validated against SAPS benchmarks.

Snoozing non-production VMs

Non-production SAP systems (dev, QA, training) often run 24/7 but are only used during business hours. Snoozing saves 50-70 percent on these VMs.

Azure Automation runbooks:

  • Schedule start/stop operations based on business hours
  • Tag VMs with schedule groups (e.g., β€œbusiness-hours-nz” for 8 AM to 6 PM NZST)
  • Runbooks can stop SAP services gracefully before VM deallocation
  • Deallocated VMs incur no compute charges (only disk storage)

πŸ”§ Aisha sets up the schedule. β€œTradeCorp’s dev and QA systems now run 10 hours a day instead of 24. That is a 58 percent savings just from snoozing. And weekends? Completely off.”

SAP licensing optimization

SAP licenses can be a bigger cost than Azure infrastructure. Two Azure features help:

Constrained vCPU VMs (covered in Domain 2) β€” same memory, fewer active cores. SAP licenses that charge per-core cost less. Example: M64-32ms has 32 cores instead of 64, with the same 1.7 TB memory.

Azure Hybrid Benefit (AHUB) β€” if TradeCorp owns Windows Server or SQL Server licenses with Software Assurance, those licenses can be reused on Azure VMs. This eliminates the Windows/SQL license cost from the Azure bill (up to 40 percent savings on Windows VMs).

Storage optimization

Storage costs add up across a large SAP landscape:

  • Right-tier storage β€” use Standard SSD for non-production instead of Premium SSD
  • Delete orphaned disks β€” VMs leave behind unattached disks when deleted
  • Premium SSD v2 β€” pay for actual IOPS/throughput instead of over-provisioning capacity
  • Archive tier for old backups β€” move backups older than 90 days to cheaper tiers
  • Review ANF tier β€” use Standard ANF for non-production shared storage

Azure Cost Management

Azure Cost Management provides SAP cost visibility:

  • Cost analysis β€” break down costs by resource group, tag, or meter
  • Budgets β€” set spending limits with alerts at 80 percent, 90 percent, 100 percent thresholds
  • Cost allocation β€” allocate shared costs (networking, Bastion) across SAP SIDs
  • Exports β€” automated cost reports for Carlos’s finance meetings
Question

When should you use Reserved Instances vs Savings Plans for SAP?

Click or press Enter to reveal answer

Answer

Reserved Instances for production HANA VMs (stable size, maximum discount up to 72 percent). Savings Plans for application servers (flexible sizing, discount up to 65 percent). RI locks to a specific VM size. Savings Plans commit to a spend level with flexibility to change VM sizes and regions.

Click to flip back

Question

How does snoozing non-production VMs save money?

Click or press Enter to reveal answer

Answer

Azure Automation runbooks schedule non-production VMs to start during business hours and deallocate after hours. Deallocated VMs incur no compute charges (only disk storage). Dev/QA systems running 10 hours instead of 24 save approximately 58 percent, plus weekends off saves more.

Click to flip back

Question

How do constrained vCPU VMs reduce SAP costs?

Click or press Enter to reveal answer

Answer

Constrained vCPU VMs have fewer active cores but the same memory as the full variant. SAP licenses that charge per-core cost less with fewer cores. Example: M64-32ms has 32 cores instead of 64 with the same 1.7 TB memory. Azure VM cost stays the same, but SAP license cost drops.

Click to flip back

Question

What is Azure Hybrid Benefit and how does it help SAP costs?

Click or press Enter to reveal answer

Answer

Azure Hybrid Benefit lets you reuse existing Windows Server or SQL Server licenses (with Software Assurance) on Azure VMs, eliminating the license cost from the Azure bill. Savings can reach up to 40 percent on Windows VM costs. Applies to SAP application servers running on Windows.

Click to flip back

Knowledge check

Knowledge Check

TradeCorp's production HANA M192ms VM will run for at least 3 years. Which cost commitment gives the deepest discount?

Knowledge Check

Carlos wants to reduce non-production SAP costs by 50 percent without deleting any systems. What should Aisha implement?

Knowledge Check

TradeCorp has existing Windows Server licenses with Software Assurance. How can Aisha reduce Azure costs for Windows-based SAP application servers?

Summary

You now have a comprehensive cost optimization toolkit: Reserved Instances for stable HANA VMs, Savings Plans for dynamic app servers, right-sizing based on monitoring data, snoozing non-production during off-hours, constrained vCPU for SAP licensing, Hybrid Benefit for Windows licenses, storage optimization, and Cost Management for visibility. Together these can reduce SAP Azure costs by 30-50 percent.

Next and final module: SAP operations lifecycle β€” the ongoing care and feeding of SAP systems on Azure.

🎬 Video coming soon

← Previous

Microsoft Sentinel for SAP

Next β†’

SAP Operations and Lifecycle Management

Guided

I learn, I simplify, I share.

A Guide to Cloud YouTube Feedback

© 2026 Sutheesh. All rights reserved.

Guided is an independent study resource and is not affiliated with, endorsed by, or officially connected to Microsoft. Microsoft, Azure, and related trademarks are property of Microsoft Corporation. Always verify information against Microsoft Learn.