RISE with SAP Hyperscaler Choice: The Complete Enterprise Guide for 2026

What RISE with SAP Hyperscaler Choice Actually Means

RISE with SAP is marketed as a single, simplified cloud contract. One subscription, one price, one vendor relationship. What it actually is: a bundle of SAP S/4HANA Private Cloud licences, SAP Enterprise Support, SAP Business Technology Platform (BTP) credits, and managed infrastructure hosted on one of three hyperscalers — AWS, Microsoft Azure, or Google Cloud Platform (GCP). The hyperscaler choice is the infrastructure component of that bundle, and it is far more commercially significant than the "simplified cloud" marketing suggests.

When you sign a RISE with SAP contract, the Order Form specifies which hyperscaler will host your S/4HANA environment. That choice determines: the compute, storage, and network infrastructure that forms the basis of the infrastructure fee; which BTP regions and services are available to you; what data residency options exist for your specific compliance requirements; what the data egress costs will be when your SAP environment communicates with non-SAP systems; and what the costs and mechanics of exit or hyperscaler migration will look like if your requirements change.

SAP's account team will present the hyperscaler choice as a straightforward technical decision — which cloud provider you prefer, or where your data centre team has expertise. That framing serves SAP's interests, not yours. The commercially correct framing is: which hyperscaler choice minimises your total cost of ownership over the RISE contract term, maximises your negotiating leverage, preserves the most flexibility, and most efficiently converts your existing cloud commitments into RISE cost reductions? The answer requires independent analysis of your organisation's specific situation — not a slide deck from your SAP account team.

AWS vs Azure vs GCP for RISE with SAP: The Enterprise Comparison

Each of the three major hyperscalers offers materially different commercial propositions for RISE with SAP deployments. The technical differences between the platforms for running S/4HANA are largely managed by SAP — your infrastructure team does not need to operate the hyperscaler directly. The commercially relevant differences are in pricing structure, BTP service availability, EDP mechanics, data residency coverage, and SAP's internal commercial relationship with each hyperscaler.

The commercially optimal hyperscaler choice for your organisation depends on the intersection of three factors: your existing hyperscaler commitments and discount structures; your data residency and BTP service requirements; and the relative negotiating leverage each choice creates in the RISE commercial discussion. Our RISE with SAP advisory service conducts this analysis as the first step in every RISE engagement.

Why SAP Defaults to Azure — And Why That Should Concern You

The commercial relationship between SAP and Microsoft is one of the most significant in enterprise software. SAP and Microsoft operate a deep co-sell agreement, co-development arrangement, and joint go-to-market initiative that creates measurable financial incentives for SAP's commercial team to propose Azure for RISE deployments. This is not conjecture — it is reflected in SAP's internal deal support processes, the speed and resourcing of Azure RISE proposals versus AWS or GCP proposals, and the default infrastructure assumptions embedded in standard RISE Order Forms.

The practical consequence for enterprise buyers is significant. If you do not explicitly specify your hyperscaler preference, you will receive an Azure proposal. If you do not explicitly challenge the infrastructure pricing in that proposal, you will pay Azure-era pricing that was set at contract signature — which for contracts signed in 2022–2023 means you are paying against hyperscaler list prices that have since declined significantly. And if you do not explicitly negotiate multi-cloud provisions, migration rights, or benchmarking rights, you will have none of them — because SAP's standard terms do not include them.

None of this means Azure is the wrong choice for every enterprise. For organisations with large Azure EAs, significant Azure EDP credits, or Microsoft 365 deep integration requirements, Azure RISE may genuinely be the most commercially efficient option. The point is that the choice should be made on the basis of independent analysis of your specific commercial position — not on the basis of SAP's default preference.

How Hyperscaler Choice Affects Your BTP Credits

The BTP credit package included in RISE with SAP is not hyperscaler-agnostic. The services available within BTP, and the regions in which they can be consumed, vary materially between hyperscaler platforms. This means the hyperscaler choice you embed in your RISE Order Form is simultaneously a BTP strategy decision — and most enterprises make it without understanding that connection.

The critical dimensions to validate before finalising hyperscaler choice are: which specific BTP services you plan to consume over the contract term; whether those services are available in your required data residency region on your preferred hyperscaler; and whether the BTP credit allocation in the RISE proposal is sufficient for your projected consumption pattern — or whether it is overspecified in services you will not use and underspecified in services you will.

The average enterprise consumes fewer than 60% of the BTP credits included in their RISE contract before they expire. This is partly a utilisation planning failure, but it is also partly a consequence of choosing a hyperscaler that restricts access to the BTP services the enterprise actually needs. Independent analysis of BTP service availability by hyperscaler before contract signature can prevent this mismatch. Our detailed guide to RISE with SAP BTP credits provides the complete framework for this analysis.

Cost Optimisation: Turning Hyperscaler Choice into Savings

The hyperscaler choice in RISE with SAP creates multiple cost optimisation opportunities that most enterprises miss entirely. The two most significant are infrastructure benchmarking — challenging the embedded infrastructure fee against current hyperscaler market rates — and EDP/CUD alignment — structuring your existing hyperscaler enterprise discount commitments to generate credits that offset the RISE infrastructure fee.

Infrastructure benchmarking is straightforward in principle but requires both the contractual right to conduct it and the technical expertise to produce a defensible comparison. SAP's standard RISE terms do not include a benchmarking right, so it must be negotiated. For enterprises currently in RISE negotiations, inserting a 24-month infrastructure benchmarking right — with a contractual mechanism to adjust the infrastructure fee to within 10–15% of the benchmark result — is one of the highest-value contractual provisions available. For enterprises already contracted, this becomes a renewal-point negotiation.

EDP and CUD alignment requires simultaneous negotiation with both SAP and your chosen hyperscaler. The mechanism is to structure your hyperscaler enterprise agreement to include the RISE workload as eligible committed spend, generating credits that flow back against the infrastructure component of the RISE ACV. This is complex but achievable — we have helped enterprises achieve effective infrastructure cost reductions of 20–28% through well-structured EDP alignment arrangements. The detailed mechanics are covered in our article on RISE with SAP hyperscaler choice cost optimisation tactics.

Negotiation: The Five Hyperscaler Provisions That Protect Your Position

When negotiating RISE with SAP, five hyperscaler-specific provisions should be on every enterprise buyer's must-have list. None of them will appear in SAP's standard Order Form. All of them are achievable for enterprise customers with sufficient deal value — but they require knowing to ask, and understanding how to frame the request in terms SAP's commercial team can take through their approval process.

1. Hyperscaler migration rights: The contractual right to move the RISE workload to a different hyperscaler at defined points in the contract term (annually or at the two-year review) without triggering early termination fees or significant infrastructure reconfiguration costs. This is both a cost protection mechanism and an exit flexibility provision.
2. Infrastructure benchmarking rights: The right to conduct an independent benchmark of the infrastructure fee against current hyperscaler market rates at 24-month intervals, with a pricing adjustment mechanism if the benchmark identifies a defined level of divergence. This protects against hyperscaler pricing decay over a multi-year contract term.
3. EDP/CUD credit portability: Contractual confirmation that the RISE infrastructure workload revenue will flow through your organisation's enterprise agreement with the hyperscaler, enabling credits from your EDP or CUD arrangement to offset the infrastructure fee. Requires parallel negotiation with the hyperscaler.
4. Multi-cloud BTP access: The ability to consume BTP credits across regions on more than one hyperscaler, subject to service availability. Critical for enterprises with multi-region requirements or where BTP service coverage varies between hyperscalers.
5. Data egress cost cap: A contractual limit on data egress charges arising from the RISE environment communicating with non-SAP systems, with any excess above the cap shared between SAP and the customer. Prevents unbudgeted infrastructure cost accumulation from high-volume API integrations.

The sequencing of these provisions in the negotiation is as important as the provisions themselves. Hyperscaler terms must be agreed before the software licence and support components of the RISE deal are finalised — once the BoM is locked, inserting new infrastructure provisions becomes significantly more difficult. Our complete guide to RISE with SAP hyperscaler choice negotiation strategies covers the full tactical framework.

Key Questions to Ask SAP Before You Sign

SAP's account team will not volunteer the commercial information you need to make an informed hyperscaler choice. The right questions force transparency and create a documented record that can be used in subsequent negotiation. The most important questions to ask, and the answers to demand in writing, are covered in detail in our guide to RISE with SAP hyperscaler choice key questions to ask SAP.

At a minimum, before finalising the hyperscaler choice in your RISE Order Form, you should have written answers from SAP to: the per-unit infrastructure cost breakdown by compute, storage, and network in the Order Form BoM; the BTP service availability map for your required data residency regions on each hyperscaler option; whether your existing hyperscaler EDP or CUD arrangement applies to the RISE workload; and the data egress charges applicable when the RISE environment communicates with non-SAP systems at your projected integration volume.

Exit Mechanics: What the Hyperscaler Choice Means for Your End-of-Contract Position

The hyperscaler choice embedded in your RISE contract will directly determine your exit costs when the contract ends or is terminated. This connection is rarely surfaced in the initial RISE commercial discussion — and that omission is not accidental. Understanding exit mechanics before signature is essential for protecting your long-term commercial position.

The three exit cost dimensions that are most directly affected by hyperscaler choice are: data egress costs at contract termination (which scale with data volume and vary by hyperscaler pricing structure); infrastructure reconfiguration costs for migrating to a different hyperscaler or to on-premises (which depend on the architecture of the RISE deployment on the chosen hyperscaler); and BTP credit expiry at contract end (where unused credits tied to specific hyperscaler regions do not transfer automatically to a new environment).

Addressing these risks requires explicit exit provisions in the initial RISE contract — provisions that will not appear in SAP's standard Order Form. The specific contract language needed to protect against exit cost overruns is covered in our guide to RISE with SAP exit strategy for 2026.

Frequently Asked Questions

Explore the Full RISE Hyperscaler Series

Related RISE with SAP Resources