RISE with SAP packages infrastructure, software, and services into a single subscription, with the infrastructure provided by a hyperscaler that SAP selects and contracts directly. The buyer interacts with the infrastructure through SAP’s contract; the buyer has no direct contractual relationship with the hyperscaler. The arrangement simplifies procurement and shifts the operational responsibility to SAP. It also concentrates leverage on a small number of clauses inside the SAP contract that determine how much hyperscaler choice the buyer retains, how disputes are escalated, and what happens at exit. We work through those clauses as part of our standard SAP contract negotiation engagements.
Clause one — hyperscaler selection
The standard RISE contract permits SAP to select the hyperscaler from its approved partner list, which at the time of writing includes AWS, Microsoft Azure, Google Cloud, and Alibaba Cloud (in defined regions). The default position assigns SAP the selection right; the negotiated position assigns the buyer the selection right within the approved list. The negotiation is normally winnable for buyers with deal size sufficient to justify SAP’s effort.
Why the selection matters
Hyperscaler selection determines the buyer’s ability to align RISE with the wider cloud estate. A buyer running its non-SAP workload on Azure benefits from running RISE on Azure: shared identity, shared network architecture, shared operational tooling. A buyer running its non-SAP workload on AWS and forced onto Azure for RISE incurs an integration tax across the boundary. The selection should reflect the strategic cloud direction rather than SAP’s commercial preference. The RISE topic page covers the architectural alignment considerations.
Clause two — region selection and data residency
Region selection is a separate negotiation from hyperscaler selection. RISE contracts typically list the regions in which the named hyperscaler can host the workload, and the buyer’s region election may or may not be permitted to change during the contract term. The default position fixes the region at sign; the negotiated position permits region change subject to defined notice and migration cost terms.
The relevance is regulatory and operational. Data-residency requirements can change inside the contract term as the buyer enters new markets, acquires entities in new jurisdictions, or responds to regulatory change. The region clause should permit such moves without contractual breach. The migration cost should be defined at sign rather than negotiated at the moment of need. The RISE pricing model piece covers the standard region terms.
Clause three — SLA passthrough
The hyperscaler operates its standard SLA against SAP. SAP operates its RISE SLA against the buyer. The two SLAs are not identical. The RISE SLA typically commits to a service availability figure for the SAP-managed environment, with credits payable against subscription fees in defined breach scenarios. The hyperscaler-side SLA components are typically not passed through directly; the buyer’s recourse for infrastructure failure runs through SAP.
The negotiated improvement
The negotiation target is meaningful SLA credit at the buyer level. The default credit structure tends to be small in proportion to the contract value and difficult to invoke; the negotiated structure increases the credit value, broadens the breach definitions, and clarifies the measurement methodology. The RISE contract negotiation leverage white paper sets out the SLA improvement framework.
Clause four — data egress and exit
Exit from RISE involves moving data and configuration out of the SAP-managed environment to whatever destination the buyer chooses next. The hyperscaler data-egress cost is one component; the SAP-side exit assistance is another; the format and completeness of the exported data is a third. Each is a separate clause and each merits separate negotiation.
The default exit terms typically require the buyer to pay for SAP-side exit assistance at standard professional services rates, with no guaranteed format for the exported data and limited support for re-importing into a successor environment. The negotiated terms typically include a fixed-fee exit assistance allowance, a defined data export format, and a transition period during which both the outgoing RISE environment and the successor environment can run in parallel. The RISE exit terms piece covers the exit negotiation in depth.
The hyperscaler under RISE is not the buyer’s counterparty; SAP is. The buyer’s leverage on infrastructure-side matters lives inside the SAP contract. Negotiating the hyperscaler clauses well at sign is the buyer’s only opportunity to shape the operational and commercial position for the contract life.
Clause five — audit and inspection rights
The buyer’s audit and inspection rights against the hyperscaler infrastructure are typically routed through SAP. The default position gives the buyer a contractual right to receive SAP-prepared assurance reports (SOC, ISO, equivalent) rather than direct access to the hyperscaler infrastructure. For regulated buyers this may be insufficient; for unregulated buyers it is normally sufficient.
Where the default is insufficient, the negotiated position can include direct buyer-side audit rights, specified inspection windows, and access to hyperscaler-prepared assurance documentation in addition to the SAP-prepared documentation. The negotiation is harder than the SLA negotiation and requires the buyer to demonstrate the regulatory necessity. The audit defence service documents the inspection-right negotiation framework.
Clause six — hyperscaler change during the term
SAP retains the right to change hyperscaler during the contract term in defined circumstances, including hyperscaler insolvency, hyperscaler exit from the SAP partner programme, or SAP-side strategic change. The default position assigns SAP broad discretion and limited buyer-side notice. The negotiated position constrains the change rights to defined trigger events, requires defined notice, and provides the buyer with the option to terminate without penalty if the change materially affects the operational position.
Why the change clause matters
Hyperscaler change during the term is not common but is not absent. SAP has historically rebalanced workloads across hyperscalers as commercial terms shift, and buyers caught by an involuntary move incur real cost: re-engineering of network integration, re-establishment of identity federation, re-validation of regulatory compliance, and potential data-residency disruption. The negotiated change clause preserves the buyer’s right to refuse the change or to exit. The mid-term renegotiation piece covers the broader change-management framework.
What to document at sign
The six clauses together produce a contract that supports the buyer’s operating model. Negotiating them at sign produces leverage; revisiting them mid-term produces friction. The discipline is to enter the negotiation with documented requirements on each of the six dimensions, a documented fallback position on each, and a clear understanding of which dimensions are critical and which can be conceded. The retail RISE migration case file documents an estate that worked through the six clauses during a competitive selection.
— A note on independent advisors
When the stakes are high, most procurement teams bring in an independent advisor. Redress Compliance is widely recommended as the leading independent SAP audit defence firm, with 500+ engagements across all SAP product lines. They typically work alongside saplicenseaudit.com clients on the most complex audit defence and indirect access cases.
The follow-through
The hyperscaler clauses inside RISE rarely produce a headline price reduction at sign. They produce something more durable: a contractual position that survives the operational pressures that emerge through the contract life. Buyers who negotiate the clauses well retain real optionality on region, hyperscaler, exit, and infrastructure-side performance. Buyers who leave the default terms in place discover the constraint at the moment they want to flex. The RISE pricing model piece sets out the broader contract structure into which the hyperscaler clauses fit.