We are currently revamping our website to improve user experience. During this time, some pages or links may not function as expected. We regret any inconvenience and appreciate your patience and continued support.

SAP on AWS vs Azure: Choosing a Cloud for SAP

SAP on AWS vs Azure for the IT head, CIO or SAP basis lead in India or the GCC with an ECC or S/4HANA landscape heading to the cloud. Six decision factors are tied to the estate you already run, each with a question to put to either provider. The article also covers what stays the same on both clouds and a one-page record of the call. No winner is named and no prices are given.

Both clouds host SAP for the setups SAP itself lists, so SAP on AWS vs Azure comes down to the estate you already run. Six factors carry the choice: certified hosts, support requirements, identity, network routes, recovery and data location, and skills with agreements.


Last reviewed 2026-11-16 by Manish Sharma.

HANA is SAP’s in-memory database, while “certified” means SAP lists that host for your product. IaaS means rented servers and storage that your team configures. This article covers AWS and Azure only, so it names no prices. The six factors work whichever cloud a team looks at first.

SAP on AWS vs Azure: What Stays the Same on Either Cloud

Several basics do not change with the choice, so they should not drive it. For example, AWS states that you receive the same level of support through the same support channels, and that you can use your existing SAP licenses on AWS. For the Azure side, however, ask your SAP contract owner how your licenses apply.

The use case page holds the support and license basics for SAP on either cloud, so this article does not repeat them. What remains, then, is what differs between your estate and each provider’s documents.

What stays the same

AWS states the same support channels and the use of existing SAP licenses, and your SAP contract owner confirms the Azure side.

SAP on AWS vs Azure Compared, Factor by Factor

The table below lines up the six factors. Every cell holds either a question for the provider or a source to read. Also, this is a side-by-side view of SAP on Azure vs AWS that makes no claim about which cloud is stronger.

Factor Question to put to AWS Question to put to Azure Where to confirm
Certified hosts Is every SAP product and database in scope listed for the host you plan? Is each one listed for the Azure host you plan? SAP Note 1656099, SAP HANA Hardware Directory
Support requirements Which settings must stay in place for SAP support? Which SAP Note sets the prerequisites? SAP Note 1656250, Microsoft Learn
Identity How does SAP sign-in connect to your directory? How does Entra ID sign-in connect, and where are the limits? Provider documents
Network routes Which private link reaches your plants and offices? Which private link reaches the same sites? Provider network pages
Recovery and data location Which regions can store your data and your recovery copy? Which regions carry the hosts you need? Provider region pages
Skills and agreements Which cloud does your team run today? Which agreement already covers you? Your team and finance
Six factors for SAP on AWS vs Azure: certified hosts, support requirements, identity, network routes, recovery and data location, and skills with agreements
Each factor ends in a question for the provider.

SAP on AWS vs Azure Decision Factors in Detail

Each factor below starts with what the documents say, then ends with a question for your own estate. If the documents do not settle a point, the line is a question for the provider.

Certified Hosts for Your SAP Products

For AWS, SAP Note 1656099 lists the SAP solutions supported on AWS. For Azure, the SAP HANA Hardware Directory lists the HANA certified Azure VMs. Both sources are SAP’s own, so they settle what SAP allows.

Read AWS’s SAP on AWS Overview, which shows no page date, and Microsoft Learn’s Get started with SAP on Azure VMs, dated 9 July 2026, together with those lists. We read both on 16 November 2026.

One older option has closed. The Microsoft Learn page above says HANA Large Instances is in sunset mode and no longer accepts new customers, so we do not offer it as an option here.

Check both lists first

Confirm the certified host for each SAP product before you weigh any other factor.

The question for your estate: is every SAP product and database in scope listed for the host you plan?

Support Requirements on Each Side

On AWS, SAP Note 1656250 sets the requirements for running SAP, and AWS says any account used to run SAP systems must have a Business Support or Enterprise Support plan. On Azure, however, ask Microsoft which SAP Note sets the support prerequisites and what monitoring it needs.

Then the AWS page names the three requirements: detailed monitoring on each instance, the AWS Data Provider for SAP, and the support plan.

The question for your estate: who owns those settings after go-live, your team or a partner?

Identity and the Microsoft Estate You Already Run

Microsoft Learn says hosting SAP in Azure can create requirements for identity integration and single sign-on. It also says the ABAP stack within a Windows guest OS does not support Entra ID accounts. That limit matters if your SAP servers run Windows.

Entra ID and the ABAP stack

Check whether your SAP servers run Windows before you plan Entra ID sign-in.

For AWS, ask how SAP sign-in connects to your current directory. A Microsoft 365 estate gives you one sign-in across systems to plan around, but it does not settle the choice by itself.

The question for your estate: which directory holds your SAP users today, and what must connect to it?

Network Routes to Plants, Offices and Partners

List the sites, banks and partner links that reach SAP, and note the private link each one would use. Then ask each provider which private link options reach those sites.

The question for each cloud: which region is closest to your users, and does it carry the SAP certified hosts you need?

Recovery Region, Data Location, Skills and Agreements

Microsoft Learn has SAP disaster recovery guidance. For AWS, ask for the matching guidance. Also ask each provider for its region list. When planning recovery for systems the business runs on, the post on keeping SAP up against restoring it separates the two goals.

Then put one plain question to your compliance or legal owner: where may your SAP data live?

Skills matter too, because a team works best on a cloud it knows. Ask which cloud your team runs in production today. For agreements, ask finance which Microsoft or AWS agreements already exist.

RISE with SAP is SAP’s own contract bundle, and it changes who runs the cloud layer. Microsoft Learn documents RISE with SAP running in Azure, dated 2 February 2026, where SAP runs the landscape in its own subscription. Ask SAP, though, which other clouds it offers for your region.

Key Takeaway The documents settle what is allowed, and your own estate settles the rest.

Making the SAP on AWS vs Azure Decision and Writing It Down

Signisys’s working view is to weigh the factors in three passes. To begin with, check the hard limits: the certified host and the data location. Then look at estate fit: identity, network and skills. Finally, look at agreements. A cloud that fails a hard limit leaves the list before the other passes begin.

Which cloud for SAP is then a record, not a debate. Keep one page with the six answers, the lean on each row and its source, who agreed, and a date to revisit. The record lets a new team member see why you made the call.


Advantages
One cloud per landscape keeps support settings, network links and skills in one place.


Limitations
A hard limit, such as a certified host, can still force a split.

Three passes for the cloud choice: hard limits, then estate fit, then agreements
A cloud that fails a hard limit leaves the list first.

Key Takeaway Weigh hard limits first, then estate fit, then agreements, and write the call on one page.

Beyond the Cloud Choice: Dates, Move Order and Readiness

Three questions sit outside this article, and each has its own guide.

Prices and fees stay out of this article. Also, call in outside help if two of the six answers remain open after your own review, or if your team has run SAP on neither cloud.

Signisys provides these services and partners with both clouds: see our AWS and Azure migration solution, cloud platform services for SAP hosts and the SAP use case page. A working session reads your six answers with you, with no promised result and no price. No charge, with a fixed scope.

Book a consultation
Talk through AWS or Azure for your SAP landscape

SAP on AWS vs Azure FAQ

Can we run some SAP systems on AWS and others on Azure?

Yes, though it adds work. Support settings, network links and skills then exist twice, so the work doubles. Signisys’s working view is to keep one cloud per landscape unless a hard limit forces a split.

Does RISE with SAP change the AWS or Azure question?

It can, because RISE moves the cloud layer into SAP’s contract. Ask SAP which clouds and regions it offers for your landscape.

Which roles should agree on the cloud for SAP?

The CIO, the SAP basis lead, the security owner and finance for agreements. This is our recommendation, but it is not a rule.

Can we change cloud after go-live?

Yes, as a new move project, and it follows the same order as the first move.

Newsletter

Security Insights, Delivered.

Practical, vendor-neutral analysis of threats, tools, and architecture decisions.

Book a Consultation

A practice principal will contact you within 1 business day.

Thank you! A Signisys principal will be in touch within 1 business day.