Inside a RISE contract, the hyperscaler is selected by the buyer from AWS, Azure or Google Cloud. The selection reads against the existing hyperscaler footprint, the data-residency surface, the embedded margin and the renewal-time portability. The Admodum read on the architecture, the renewal-time levers and the disposition framework.
RISE is the SAP-managed subscription bundle that includes the S/4HANA Cloud Private Edition product and the embedded hyperscaler-pass-through infrastructure. The hyperscaler is selected by the buyer from three published options: Amazon Web Services, Microsoft Azure or Google Cloud Platform. The selection is recorded in the order form and is read against the contracted region map at the adoption moment.
The architecture differs from the on-prem architecture: on the on-prem track, the infrastructure is procured by the buyer directly from the hyperscaler (or run on-premises), and the SAP licence is BYOL onto that infrastructure; on the RISE track, the infrastructure is procured by SAP from the hyperscaler and passed through to the buyer inside the RISE contract. The wider RISE bundle anatomy spoke reads the bundle structure; the wider SAP RISE renewal spoke reads the renewal-time hyperscaler-pass-through margin.
The selection reads against the existing hyperscaler footprint. A buyer with a strategic AWS commitment, typically an Enterprise Discount Program agreement at AWS, has reasons to select RISE-on-AWS: the ingress-egress traffic between the RISE-hosted S/4HANA and the surrounding AWS-hosted application estate reads at network-internal rates rather than network-egress rates; the operational tooling (CloudWatch monitoring, IAM identity, KMS encryption) reads against the existing AWS estate. The same reading applies to a buyer with an MACC commitment at Microsoft Azure (the MACC consumes in part against the RISE-on-Azure hyperscaler-pass-through line, but only under the specific MACC pass-through arrangement) and to a buyer with a strategic Google Cloud commitment.
The footprint adjacency does not, however, override the SAP-side architecture: the RISE-hosted S/4HANA Cloud Private Edition is a managed-service instance, not a customer-managed instance on the customer's hyperscaler tenancy. The buyer does not get the same level of operational access as on a BYOL deployment. The wider SAP Private Cloud spoke reads the Private Edition architecture.
The data-residency surface is the regulatory read. The hyperscaler region selected for the RISE-hosted S/4HANA Cloud Private Edition instance carries the data-residency obligation: EU buyers (under GDPR) typically select an EU region (Frankfurt, Dublin, Paris, Amsterdam on AWS; West Europe, North Europe, France Central on Azure; europe-west on Google Cloud); UK buyers typically select a UK region; APAC buyers select an APAC region; US buyers select a US region; and so on.
The published region map differs across the three hyperscalers, and the SAP-side region availability inside RISE is a subset of the hyperscaler region map (not every hyperscaler region is enabled for RISE). The buyer reads the SAP-side RISE region map against the regulatory obligation at the original-selection moment. The wider SAP data residency spoke reads the residency obligation in detail.
The embedded margin reads against the published hyperscaler list. The hyperscaler price itself is set by the hyperscaler and procured by SAP under the SAP-side hyperscaler master agreement; the SAP-side procurement discount is not disclosed to the buyer. The buyer reads the embedded RISE-side margin against the published hyperscaler list price as a benchmark: the typical RISE-side margin on the embedded infrastructure runs at fifteen to twenty-five percent above the published hyperscaler list price.
The margin reading is not the same across the three hyperscalers: the margin against AWS list typically reads at the lower end of the published range; the margin against Azure list typically reads at the higher end; the margin against Google Cloud list typically reads at the middle. The variance is a function of the SAP-side procurement discount at each hyperscaler (not disclosed) and the SAP-side margin policy on each hyperscaler product line. The wider SAP RISE renewal spoke reads the renewal-time margin reconciliation.
The renewal-time portability is the lock-in surface. The contracted hyperscaler at the original RISE term is the contracted hyperscaler at renewal: the buyer cannot migrate from RISE-on-AWS to RISE-on-Azure (or any other pair) without a substantive replatforming exercise. The replatforming carries direct cost (the migration project, the cutover risk) and indirect cost (the rebuild of network-internal integrations against the new hyperscaler estate).
The portability reading is therefore part of the original-selection discipline, not the renewal-time discipline. The buyer prices the lock-in cost at the original-selection moment: what does it cost to migrate from this hyperscaler to another, given the surrounding application estate, the network-integration estate, the operational-tooling estate? The wider SAP BATNA spoke reads the leverage at renewal; the wider RISE versus on-prem spoke reads the wider portability framework.
At the original-selection moment, the buyer is in one of four positions on the hyperscaler-choice question. The first is the strategic-adjacency position: the buyer has a strategic commitment at one of the three hyperscalers and selects the matching hyperscaler for RISE. The second is the data-residency position: the buyer selects the hyperscaler with the strongest regional footprint against the regulatory obligation. The third is the margin-economics position: the buyer selects the hyperscaler with the lowest embedded RISE-side margin against the published hyperscaler list. The fourth is the hybrid-architecture position: the buyer selects a hyperscaler for RISE that differs from the surrounding application-estate hyperscaler and prices the network-integration cost into the architecture.
The wider engagement sits in the SAP practice; the aggregated reading list sits in the SAP knowledge hub; active renewal moments route to the Renewal Programme; active audit moments route to Audit Defence.
The subscription-renewal architecture and the embedded-margin reading.
The Private Edition architecture against the customer-managed alternative.
A senior Admodum SAP advisor will read your hyperscaler-selection question against your existing AWS, Azure or Google Cloud footprint, your data-residency obligation, your embedded-margin reading and your renewal-time portability cost on a private call. Active renewal moments route to the Renewal Programme.