India’s Leading Domain & Web Hosting Provider
Support
Domain & Login
Blog
SAP on Azure: S/4HANA Hosting, HANA HA and DR Services
SAP on Azure means running SAP NetWeaver, ECC, S/4HANA and SAP HANA workloads on SAP-certified Azure infrastructure such as M-series VMs, Azure NetApp Files and Premium SSD v2, with Azure-native backup, high availability and disaster recovery. NTSPL designs, migrates and operates SAP landscapes on Azure for Indian manufacturers and regulated industries, including ECC to S/4HANA conversions.
Microsoft Azure services in scope
The Problem Azure M-series and Mv2 VMs and Azure NetApp Files and Premium SSD v2 Solve
SAP is the one workload where infrastructure mistakes show up directly in month-end close and plant dispatch. HANA needs storage that meets SAP's KPIs for log write latency, VMs that are certified for the memory size, and a high-availability cluster whose fencing actually works when a node hangs. Many Indian SAP landscapes still run ECC on Oracle or HANA appliances bought in 2016, with DR as a tape copy and a manual runbook nobody has rehearsed. With SAP ECC mainstream maintenance ending in 2027, every one of these customers faces both a platform and an application decision in the same window.
NTSPL designs SAP on Azure from SAP's certification lists and Microsoft's SAP reference architectures, not from generic VM sizing. We size HANA from an SAP sizing report or early-watch data, choose between Azure NetApp Files and Premium SSD v2 per system, build HANA System Replication with Pacemaker clusters across availability zones in Central India, and protect the landscape with Azure Backup for SAP HANA through Backint and Site Recovery for application servers. Azure Center for SAP solutions and Azure Monitor for SAP solutions are used for deployment and day-two visibility.
When to Run SAP on Azure (and When RISE with SAP or Staying Put Makes More Sense)
Signals that point to sap on azure on Microsoft Azure
- HANA appliances or ECC database servers are due for hardware refresh within 18 months.
- SAP ECC must move to S/4HANA before the end of mainstream maintenance in 2027 and you need a target platform first.
- DR for SAP is a tape copy or an untested runbook, and the business RTO is under 4 hours.
- Month-end and quarter-end close jobs run long because hardware cannot be scaled for peak.
- Sandbox, training and project systems for an S/4HANA programme are delayed by hardware procurement.
- A regulated plant (GxP, FSSAI or export-audited) needs documented, qualified infrastructure for SAP.
When a different approach is better
- If you want SAP to take full responsibility for infrastructure, basis and the S/4HANA licence as a subscription, RISE with SAP on Azure may suit better than a self-managed landscape; NTSPL can still handle connectivity, integration and surrounding Azure services.
- Very small SAP Business One installations rarely justify an M-series and Pacemaker architecture; run them on a single E-series VM with Azure Backup, or use a SaaS-hosted Business One partner.
- If your SAP hardware was refreshed in the last two years and an S/4HANA conversion is not planned before 2029, moving now may duplicate cost; plan the migration to coincide with the conversion.
SAP on Azure Building Blocks: M-Series VMs, ANF and Premium SSD v2, Center for SAP Solutions, Backint Backup and Monitor for SAP
| Service | Role in the architecture | Choose it when |
|---|---|---|
| Azure M-series and Mv2 VMs | Memory-optimized, SAP HANA-certified VMs, with Mv2 sizes up to 11,400 GiB (about 11.1 TiB) of memory, for HANA databases; E-series and D-series VMs host SAP application servers and ASCS. | HANA memory requirements exceed what E-series certified sizes provide, typically above about 1.5 to 2 TiB for production. |
| Azure NetApp Files and Premium SSD v2 | Azure NetApp Files provides NFS 4.1 volumes certified for HANA data and log with snapshot-based backup; Premium SSD v2 provides block storage where IOPS and throughput are set independently of capacity. | ANF when you want fast snapshots, volume resizing without downtime or shared /hana/shared; Premium SSD v2 when you want lower cost with granular performance tuning. |
| Azure Center for SAP solutions | Deploys SAP S/4HANA infrastructure and installs software according to SAP and Microsoft reference architectures, registers existing systems and provides quality checks against best practices. | You are building new S/4HANA landscapes or want a central view and configuration checks across registered SAP systems. |
| Azure Backup for SAP HANA | SAP-certified Backint-based backup of HANA databases running in Azure VMs, with full, differential, incremental and 15-minute log backups and point-in-time restore, plus snapshot-based options. | You want HANA-aware backups without running a third-party backup server or file-based dumps to disk. |
| Azure Site Recovery | Replicates SAP application servers, ASCS and web dispatchers to a DR region and orchestrates their start-up, complementing database-level HANA System Replication. | The SAP DR plan needs the application layer brought up in a secondary region in minutes, not rebuilt. |
| Azure Monitor for SAP solutions | Collects telemetry from SAP HANA, NetWeaver, Pacemaker clusters, the operating system and SQL or Db2 databases into Log Analytics, with workbooks and alerts for SAP-specific metrics. | Your basis team needs one view of HANA replication status, cluster health and SAP work process metrics alongside Azure infrastructure. |
Zonal HANA System Replication landscape with cross-region DR
Zonal HANA System Replication landscape with cross-region DR
SAP GUI and Fiori users reach the landscape over ExpressRoute and through SAP Web Dispatcher into application servers in Central India, which connect to a HANA primary replicated synchronously to a secondary in another availability zone behind a Pacemaker cluster and Azure Load Balancer. HANA System Replication runs asynchronously to South India for DR, application servers replicate with Site Recovery, and Azure Backup for SAP HANA plus Azure Monitor for SAP solutions protect and observe the system.
Select any component
Zonal HANA System Replication landscape with cross-region DR: click any of its 9 components to see its role and the design choice NTSPL makes for it, or trace the 7-step primary path.
SAP Landscape Engineering Decisions: HANA Sizing, Storage Choice, Zonal HSR Clusters and DR Topology
HANA sizing and VM selection
Size from SAP Quick Sizer for greenfield or from HANA sizing reports run against the current ECC database for conversions, then choose from SAP's certified IaaS directory, not general VM listings. Leave headroom for 2 to 3 years of growth since moving between M-series sizes requires a restart. For DR VMs, a smaller certified size with a resize step in the runbook reduces cost, provided the DR VM can hold the column store with preload off.
ANF versus Premium SSD v2 for HANA
Azure NetApp Files suits large or scale-out HANA systems, gives near-instant snapshots for backup and system copies, and allows volume and throughput changes without downtime, but costs more per TiB and needs capacity pools planned per zone. Premium SSD v2 is usually cheaper for single-node systems below about 4 TiB and lets you tune IOPS and throughput for log volumes precisely. Both must meet SAP HANA storage KPIs; validate with HCMT before go-live.
Zonal HA and latency
Deploy HANA primary and secondary in different availability zones of Central India with synchronous HSR, and measure inter-zone latency before deciding; SAP application-to-database latency should stay low enough that dialog response times hold. Keep application servers in the same zones as the active database and use proximity placement groups only when needed. Configure Pacemaker with the Azure fence agent using managed identity, and test fencing by killing a node.
DR topology and RPO
For HANA, use asynchronous HSR to South India, giving RPO of seconds to minutes depending on log volume and bandwidth. For application servers and ASCS, use Site Recovery or redeploy from images. Backups with cross-region restore are a third line of defence for logical corruption. Write the DR runbook to include DNS, interface endpoints for banks, GST and e-way bill integrations, and printers at plants, which commonly fail in drills.
Conversion path to S/4HANA
Decide whether to migrate first and convert later, or combine. A two-step approach (ECC on AnyDB to Azure, then convert to S/4HANA) reduces risk and lets you exit hardware quickly. A combined move using SUM with Database Migration Option to Azure suits landscapes with stable custom code and a fixed go-live window. Simplification item checks and custom code remediation, not infrastructure, usually determine the timeline.
How NTSPL Migrates and Converts an SAP Landscape onto Azure
SAP sizing and landscape design
Use SAP sizing reports or EarlyWatch data to choose certified M-series and E-series VMs and storage for production, QA, development and sandbox systems.
SAP landing zone and ExpressRoute
Build SAP-specific spokes in Central India and South India, ExpressRoute from plants and head office, and private DNS for SAP hostnames.
Infrastructure deployment and KPI validation
Deploy VMs and ANF or Premium SSD v2 with Azure Center for SAP solutions or infrastructure-as-code, then run HCMT to prove HANA storage KPIs.
HA cluster build and fencing tests
Configure HSR and Pacemaker for HANA and ASCS/ERS with Azure Load Balancer and fence agent, then run documented failover and fencing tests.
Migration dress rehearsals
Run at least two mock migrations or conversions with SUM DMO or HANA backup-restore, timing each phase to fit the business downtime window.
Go-live, backup and DR drill
Cut over, enable Azure Backup for SAP HANA and Site Recovery, onboard Azure Monitor for SAP solutions, and complete a DR drill within the first quarter.
What you receive
Securing SAP on Azure: Network Isolation, Pacemaker Fencing, Encryption and SAP-Aware Threat Detection
SAP landscapes concentrate financial, HR and plant data, and their specific risks are exposed SAP ports, weak inter-system RFC trust, unpatched HANA and kernel versions, and HA cluster misconfiguration that causes split-brain. Controls isolate SAP subnets behind Azure Firewall with only required ports, encrypt HANA data and backups, use managed identity for Pacemaker fencing, and monitor SAP security logs with Microsoft Sentinel's SAP solution.
- Dedicated SAP spokes with network security groups and Azure Firewall rules limited to SAP dispatcher, gateway and message server ports
- HANA data volume and backup encryption, with Azure disk or ANF encryption and keys in Key Vault
- Managed identity for the Azure fence agent instead of a service principal secret
- Microsoft Sentinel solution for SAP applications to detect suspicious transactions and privilege changes
- Just-in-time VM access and Azure Bastion for basis administrators instead of public RDP or SSH
SAP on Azure Cost Model: M-Series Reservations, Storage Throughput, Non-Production Snoozing and Licensing
SAP on Azure cost is dominated by HANA VM hours on M-series, followed by storage provisioned for performance (ANF capacity pools and service levels, or Premium SSD v2 IOPS and throughput) and the DR footprint. Production runs 24x7, so reservations matter most; non-production systems can be stopped outside working hours. SAP licences are separate, and operating-system licences for SLES or RHEL for SAP are included in marketplace images or brought by subscription.
- Three-year reserved instances for production HANA and ASCS VMs, which run continuously
- Snooze schedules for sandbox, training and development systems outside project working hours
- Smaller certified DR VMs with a resize step in the runbook, or a cost-optimized secondary running QA
- Premium SSD v2 with tuned IOPS and throughput for single-node HANA instead of over-provisioned capacity
- ANF cool access or snapshot-based backup policies to reduce backup storage for large HANA systems
Self-managed SAP on Azure vs RISE with SAP on Azure: which should an Indian SAP customer choose?
Judge on four criteria. Control: self-managed SAP on Azure gives you full control over sizing, HA design, patch timing, add-on products and third-party tools; RISE bundles infrastructure and technical operations under SAP's standard service definitions. Licensing: RISE converts licences to a subscription, which suits customers wanting S/4HANA Cloud Private Edition commercial terms; self-managed keeps existing perpetual licences and lets you bring support contracts and partners. Integration: if SAP is tightly coupled with plant MES, Azure data platforms and custom extensions, self-managed makes network and integration design simpler. Operations: if your basis team is thin and you want one throat to choke, RISE reduces scope. Many Indian manufacturers with in-house basis teams choose self-managed for cost and flexibility; those planning a full licence reset often choose RISE.
Key facts about sap on azure on Microsoft Azure
SAP on Azure on Microsoft Azure in Practice
3 sap on azure scenarios from Pharmaceutical API manufacturing, Consumer durables manufacturing, Agro-chemicals: the starting position, the services chosen, the architecture, the rollout and the measured outcome.
API manufacturer moves a GxP-validated SAP landscape to Azure without re-validation delays
Consumer-durables maker converts ECC to S/4HANA on Azure in one programme
Agro-chemicals company gets tested SAP HA and DR during the kharif peak
Automotive OEM unifies dealer sales and stock data from 600 outlets
EPC company vacates its owned data centre in 7 months and halves run cost
SAP on Azure on Microsoft Azure: Frequently Asked Questions
What does SAP on Azure cost each month for a mid-size S/4HANA landscape?
It depends mainly on HANA memory size and whether you run HA and DR. A mid-size landscape with a 2 to 3 TiB production HANA, zonal HA, QA, development and a DR copy typically lands between INR 25 lakh and 50 lakh a month on reserved pricing, excluding SAP licences. NTSPL produces a system-by-system bill of materials before you commit.
Is Azure certified for SAP HANA?
Yes. Specific Azure VM sizes, including M-series, Mv2 and selected E-series VMs, are listed in SAP's Certified and Supported SAP HANA Hardware Directory for IaaS, along with supported storage configurations such as Azure NetApp Files and Premium SSD v2. NTSPL designs only from that directory and validates storage with SAP's HCMT tool before go-live.
How do we move from ECC on Oracle to S/4HANA on Azure?
Either migrate ECC to Azure first and convert later, or use SAP's Software Update Manager with Database Migration Option to convert and move in one programme. The two-step route exits hardware faster and reduces risk. The combined route saves one downtime but depends on custom-code and simplification-item readiness. Either way, plan at least two dress rehearsals.
Can SAP data stay in India with DR in a different seismic zone?
Yes. Run production in Central India (Pune) with availability zones for HA, and DR in South India (Chennai), which is its paired region and geographically separate. HANA System Replication, Site Recovery and Azure Backup cross-region restore all operate between these regions, keeping SAP data in India to meet DPDP Act and auditor expectations.
How does Azure Backup for SAP HANA work?
Azure Backup integrates with HANA through SAP's Backint interface, which SAP has certified. It runs full, differential or incremental backups and log backups as frequently as every 15 minutes directly to a Recovery Services vault, without staging to local disk. You restore to a point in time from the Azure portal, including to a different VM for system copies.
What RPO and RTO can we achieve for SAP on Azure?
Within a region, synchronous HSR across availability zones gives near-zero RPO and automatic failover in a few minutes with Pacemaker. Across regions, asynchronous HSR to South India typically gives RPO of seconds to minutes and RTO of 1 to 4 hours including application layer and interface checks. Backups add point-in-time recovery for corruption.