The Private Pricing Agreement aggregate commitment, the Vertex AI overlay, the BigQuery edition mapping, the marketplace pull through, the egress credit, the price protection, and the staged renewal posture against the AWS EDP and Microsoft Azure MACC alternatives.
A working framework for CIOs, CFOs, and procurement teams running the Google Cloud Private Pricing Agreement at the upper customer scale, with the nine buyer side moves that recover twenty four to forty one percent against the Google Cloud account team's opening commitment proposal across the contracted three year PPA term.
The Google Cloud Private Pricing Agreement is the upper customer scale commitment vehicle that wraps the customer's aggregate Google Cloud spend in a single multi year agreement. The PPA carries the contracted minimum commitment, the enterprise discount band against the published list price catalog, the Vertex AI overlay, the BigQuery edition mapping, the marketplace pull through credit, the egress credit clause, and the enterprise commercial provisions across the contracted term. The PPA discount band scales with the contracted commitment tier and reaches the upper enterprise end of the band at the contracted commitment above one hundred million dollars across the contracted three year term. The buyer side discipline at the PPA negotiation determines whether the enterprise captures the upper end of the discount band or settles for the middle of the band on the aggregate commitment.
This paper sets out the Redress Compliance Google Cloud PPA negotiation framework, refined across more than five hundred enterprise software engagements at Industry recognized scale, with over two billion dollars under advisory across the broader buyer side practice. The framework coordinates nine commercial moves across a single PPA commitment cycle: the aggregate commitment sizing against the customer's eighteen to twenty four month consumption forecast, the underlying CUD portfolio structured against the steady state workload baseline, the Vertex AI overlay as a distinct line item, the BigQuery edition mapping against the lowest viable edition, the Google Cloud Marketplace pull through credit against the third party software register, the egress credit clause against the workload portability narrative, the price protection clause across the contracted term, the shortfall recovery clause, and the staged renewal posture that anchors the PPA against the AWS EDP and Microsoft Azure MACC alternatives. Read the related Google Cloud services practice, the Google Cloud CUD negotiation, the Vertex AI and Gemini negotiation, the BigQuery cost governance negotiation, the multi cloud competitive framework, the GCP negotiation leverage framework, and the multi vendor negotiation scorecard. Run against the practice corpus, the coordinated framework typically delivers twenty four to forty one percent recovery against the Google Cloud account team's opening commitment proposal across the contracted three year PPA term, plus measurable reductions in the embedded Vertex AI overlay price and the storage and egress overflow exposure.
The Google Cloud enterprise account at the upper customer scale sits at a different commercial position than it did three years ago. Google Cloud cleared forty billion dollars in 2025 on a run rate basis, with the underlying business growing above thirty percent year over year and the Vertex AI overlay growing above one hundred eighty percent year over year. Google Cloud now hosts measurable production workloads inside the majority of the upper customer scale enterprise installed base, with a defined catalog of regulated workloads running in the customer's contracted region against the customer's contracted data residency requirement. The PPA mechanic has become the structural commitment vehicle for the customer running an aggregate Google Cloud spend above the contracted twenty to thirty million dollar three year threshold, with the PPA discount band scaling with the contracted commitment tier across the broader hundred million dollar three year scale.
The PPA mechanic differs structurally from the AWS Enterprise Discount Program and the Microsoft Azure Microsoft Customer Agreement Consumption Commitment. The AWS EDP operates as a single multi year aggregate commitment with a defined discount band against the published list price catalog. The Microsoft Azure MACC operates as an aggregate consumption commitment with a defined discount band typically negotiated against the broader Microsoft Enterprise Agreement. The Google Cloud PPA operates as the aggregate enterprise commitment layered on top of the underlying CUD portfolio, with the underlying CUD portfolio carrying the resource specific, flexible, and Spend CUD structures sized against the customer's measured workload baseline. The structural difference is that the Google Cloud PPA does not replace the underlying CUD portfolio. The PPA wraps the underlying CUD portfolio inside a single multi year agreement with the broader enterprise commercial provisions.
The Google Cloud account team operates a documented commercial framework inside each enterprise account at the upper customer scale. The framework defines the cadence on the PPA renewal, the upgrade path from the CUD portfolio to the PPA aggregate commitment, the cross sell into the Vertex AI commitment overlay, the BigQuery edition migration, the marketplace pull through, and the staged renewal preparation. The Google Cloud account teams are typically the most pricing flexible of the three hyperscaler account teams at the upper customer scale because Google Cloud sits as the third place hyperscaler and carries the most aggressive net new commitment incentives at the upper enterprise scale. The buyer side response capitalizes on the structural pricing flexibility by anchoring the PPA against the AWS EDP and the Microsoft Azure MACC alternatives.
The financial stakes scale with the customer footprint at the upper enterprise scale. A mid market enterprise running ten to twenty million dollars per year on Google Cloud typically falls below the PPA threshold and runs against the CUD portfolio mechanism. A large enterprise running twenty five to seventy million dollars per year on Google Cloud faces a seventy five to two hundred ten million dollar three year PPA decision at the renewal. An upper customer scale enterprise running one hundred to two hundred million dollars per year on Google Cloud faces a three hundred to six hundred million dollar three year PPA decision. The discount band differences across the PPA tier breakpoints translate into ten to ninety million dollar swings in the all in Google Cloud cost across the contracted three year term, which means the buyer side discipline at the PPA negotiation is one of the highest leverage commercial activities the CIO and procurement team run at the upper customer scale.
The market context also includes the Vertex AI commitment overlay. Google Vertex AI revenue grew at a published rate above one hundred eighty percent year over year in 2025. Vertex AI surfaces the Gemini family, the Anthropic Claude family through Google Cloud, the Meta Llama family, and the Mistral family. The Google Cloud account teams are heavily incentivized to anchor Vertex AI spend inside the underlying PPA, because the Vertex AI overlay is the commercial vehicle the account team has the most pricing latitude on in 2026. The buyer side response treats the Vertex AI commitment as a distinct line item at the PPA negotiation rather than as an embedded service inside the aggregate commitment. Read the Vertex AI and Gemini negotiation, the enterprise AI procurement strategy, and the AI platform contract negotiation.
The market context also includes the BigQuery edition mapping. Google Cloud restructured the BigQuery commercial model into three editions in 2023: Standard, Enterprise, and Enterprise Plus. The editions carry distinct compute slot pricing, distinct governance feature catalogs, and distinct commitment discount bands. The restructure created a parallel commitment conversation alongside the underlying PPA. The buyer side response runs the BigQuery edition mapping as a distinct line item at the PPA negotiation rather than allowing the account team to anchor the BigQuery commitment against Enterprise Plus by default. Read the BigQuery cost governance negotiation.
The competitive pressure between Google Cloud, AWS, and Microsoft Azure is real and documented at the upper enterprise scale. Google Cloud account teams will move aggressively on the PPA discount band, on the Vertex AI commitment overlay, on the BigQuery edition mapping, on the marketplace pull through credit, and on the data egress credit when the buyer credibly opens the AWS EDP or the Microsoft Azure MACC conversation in parallel. The competitive narrative does not need to be fully implemented. The competitive narrative needs to be credibly framed at the PPA negotiation. Read the related AWS EDP negotiation, the Microsoft EA renewal playbook, the multi cloud competitive framework, and the Microsoft Azure negotiation.
The buyer side Google Cloud PPA negotiation framework therefore runs against five structural realities. First, the PPA aggregate commitment does not replace the underlying CUD portfolio and the two layers need to be coordinated as a single commitment architecture. Second, the Vertex AI commitment overlay has become the highest leverage commercial dimension on the Google Cloud account at the upper customer scale. Third, the BigQuery edition mapping is a parallel commitment conversation that requires explicit governance feature mapping against the lowest viable edition. Fourth, the marketplace pull through credit is the structural mechanism that converts third party software spend into PPA commitment burn at one hundred percent credit rate. Fifth, the timing of the PPA preparation needs to start at least two hundred forty days before the contract term end to preserve the leverage across the nine commercial moves.
The first commercial move is the aggregate commitment sizing against the customer's eighteen to twenty four month consumption forecast. The aggregate commitment is the contracted minimum spend that the customer commits to across the contracted three year PPA term and is the structural base from which the PPA discount band is calculated.
The Google Cloud PPA discount band scales with the contracted aggregate commitment across documented tier breakpoints. Google typically opens the PPA discount band at the contracted twenty to thirty million dollar three year threshold with a middle of band discount, lifts the discount band at the seventy five to one hundred million dollar three year threshold, and reaches the upper end of the band at the contracted commitment above two hundred million dollars across the contracted three year term. The discount band differences across the breakpoints typically translate into five to twelve percentage points of incremental discount on the aggregate commitment.
The buyer side response sizes the contracted aggregate commitment against the customer's eighteen to twenty four month consumption forecast rather than against the current consumption baseline. The sizing approach reaches the next tier breakpoint where the consumption forecast supports the tier and captures the incremental discount band. The sizing approach also includes a shortfall recovery clause that allows the customer to convert a defined percentage of the unused commitment into the next contracted term at no recovery penalty, which protects the customer against the forecasting risk inherent in the tier breakpoint stretch.
The buyer side response also negotiates a ramped commitment structure inside the contracted three year PPA term rather than a flat annual commitment across the three years. The ramped structure typically lands at sixty percent of the aggregate commitment in year one, ninety percent in year two, and one hundred fifty percent in year three. The ramped structure aligns the contracted commitment with the customer's consumption growth curve and protects the customer against the forecasting risk in the early term of the contract while preserving the contracted aggregate commitment tier at the back of the contracted term.
The second commercial move is the underlying Committed Use Discount portfolio structured against the steady state workload baseline. The PPA aggregate commitment does not replace the underlying CUD portfolio. The CUD portfolio sits underneath the PPA and captures the resource specific, flexible, and Spend CUD discount bands on the underlying workload categories.
The resource specific CUD layer commits to a defined virtual machine family and region for a one or three year term in exchange for the highest published discount band. The published resource specific CUD discount band sits at thirty seven percent for the one year term and fifty five to seventy percent for the three year term, depending on the virtual machine family and the region. The resource specific CUD layer sits underneath the PPA aggregate commitment and captures the upper end of the discount band on the steady state virtual machine baseline.
The flexible CUD layer commits to a dollar per hour amount across compatible compute usage for a one or three year term. The published flexible CUD discount band sits at twenty eight percent for the one year term and forty six percent for the three year term across the broader compute catalog including Compute Engine, Cloud Run, Cloud Functions, and Google Kubernetes Engine. The flexible CUD layer captures the middle band on the variable compute baseline.
The Spend CUD layer commits to an aggregate dollar amount across the Google Cloud catalog and captures the residual workload catalog that does not fit the resource specific or flexible CUD structures. The Spend CUD discount band sits at the lower end of the CUD catalog but applies across the broadest set of services. The Spend CUD layer therefore captures the long tail of the Google Cloud catalog inside the underlying CUD portfolio.
The buyer side response coordinates the PPA aggregate commitment with the underlying CUD portfolio as a single commitment architecture rather than treating the PPA and the CUD portfolio as alternative commitment vehicles. The coordination runs the resource specific CUD portfolio on the steady state workloads, the flexible CUD on the variable compute, and the Spend CUD on the residual catalog, with the PPA wrapping the underlying CUD portfolio inside the aggregate commitment and the broader enterprise discount band. The coordinated approach captures both the upper CUD discount band on the steady state baseline and the aggregate PPA discount band on the broader commitment. Read the Google Cloud CUD negotiation.
The third commercial move is the Vertex AI commitment overlay. The Vertex AI commitment is the dimension where the Google Cloud account team has the most pricing latitude in 2026 and where the coordinated framework typically recovers the most measurable spend against the account team's opening framing inside the PPA.
Vertex AI inference, provisioned throughput, customization, and managed service spend rolls into the aggregate PPA by default. The Vertex AI catalog includes the Google Gemini family with the Gemini 2 Pro, Gemini 2 Flash, and Gemini 2.5 model variants, the Anthropic Claude family with the Claude Opus, Claude Sonnet, and Claude Haiku model variants through Google Cloud, the Meta Llama family, and the Mistral family. The Vertex AI commitment carries a token consumption metric, a provisioned throughput unit metric, and a customization compute metric. The Vertex AI specific discount layer sits at four to nine percent above the aggregate PPA discount band on the Vertex AI rolled up spend at the higher Vertex AI spend tier.
The Vertex AI specific discount layer is typically not surfaced unless the buyer raises Vertex AI spend as a distinct conversation. The buyer side response runs the Vertex AI commitment as a distinct line item at the PPA negotiation, with explicit provisions for model version conversion, managed service caps, data retention clauses, and Vertex AI token pricing benchmarked against the customer's actual measured model consumption. The practice has documented engagements where the Vertex AI commitment recovered an additional eleven to twenty one percent against the Google Cloud account team's opening Vertex AI proposal when the buyer credibly opened the AWS Bedrock or Microsoft Azure OpenAI alternative.
The practice has documented engagements where Vertex AI spend grew from less than four percent of the underlying PPA aggregate commitment to eighteen to thirty two percent of the aggregate commitment across a single twelve month period. The AI commitment overlay therefore needs to be sized at the PPA negotiation against the customer's eighteen to twenty four month forecast rather than the customer's current consumption baseline. The buyer side response inserts a Vertex AI commitment expansion clause that allows the customer to grow the Vertex AI commitment inside the underlying PPA without renegotiating the underlying commitment structure.
The fourth commercial move is the BigQuery edition mapping inside the PPA. The Google Cloud account team typically anchors the BigQuery commitment against Enterprise Plus on the assumption that the customer requires every governance feature in the upper edition. The buyer side response maps the customer's required governance features against the lowest viable edition.
BigQuery in 2026 runs three editions: Standard, Enterprise, and Enterprise Plus. The editions carry distinct compute slot pricing, distinct governance feature catalogs, and distinct commitment discount bands. BigQuery Standard is the entry edition with limited governance, limited concurrency, and limited workload management. BigQuery Enterprise sits at the middle tier with workload management, fine grained governance, integrated machine learning, materialized views, and the higher concurrency caps. BigQuery Enterprise Plus sits at the upper tier with customer managed encryption keys, VPC service controls, data residency at the regional level, advanced cataloging through Dataplex, the higher data retention windows, and the dedicated technical account manager.
The buyer side response maps the customer's required governance features against the lowest viable BigQuery edition. The map typically reveals that fifty to seventy percent of the customer's BigQuery workload can run on Standard or Enterprise with the remaining thirty to fifty percent of the workload running on Enterprise Plus. The mixed edition deployment is supported by Google Cloud at the project and reservation level and is one of the highest leverage commercial moves at the BigQuery commitment. The practice has documented engagements where the mixed edition deployment recovered an additional twelve to twenty four percent against the Google Cloud account team's opening Enterprise Plus proposal. Read the BigQuery cost governance negotiation download.
The fifth commercial move is the Google Cloud Marketplace pull through credit against the customer's documented third party software register. The marketplace pull through is the structural mechanism that converts third party software spend into PPA commitment burn at one hundred percent credit rate.
The Google Cloud Marketplace pull through is the structural arrangement where third party software spend transacted through the Google Cloud Marketplace counts against the PPA aggregate commitment at a defined credit rate. The Google Cloud Marketplace pull through credit sits at one hundred percent for defined software vendors, which is the highest pull through credit rate across the three hyperscaler marketplaces. The AWS Marketplace pull through credit sits at fifty percent against the AWS EDP and the Microsoft Azure Marketplace pull through sits at one hundred percent against the MACC but with a narrower vendor catalog.
The buyer side response maintains a documented third party software register that catalogs every third party software vendor running on the Google Cloud estate. The register includes the contract value, the contract anniversary date, the marketplace availability flag, and the customer's negotiation cadence with each vendor. The register typically includes Datadog, Snowflake, MongoDB, Confluent, HashiCorp, Wiz, Splunk, Palo Alto Networks, CrowdStrike, GitLab, JFrog, Sumo Logic, Couchbase, and the broader SaaS catalog. The buyer side response then converts the eligible third party software spend through the Google Cloud Marketplace at the contracted anniversary date of each vendor, which converts the third party software spend into PPA commitment burn at the one hundred percent credit rate.
The practice has documented engagements where the Google Cloud Marketplace pull through converted fifty to ninety percent of the in scope third party software spend into PPA commitment burn. The conversion typically scales between five and twenty five percent of the customer's aggregate PPA commitment value depending on the third party software footprint and the customer's marketplace migration discipline. Read the related Datadog negotiation download, the Snowflake negotiation download, the MongoDB Atlas negotiation download, the HashiCorp negotiation download, and the Splunk Cloud negotiation download.
The sixth and seventh commercial moves are the egress credit clause and the price protection clause across the contracted PPA term. These two clauses carry asymmetric commercial leverage because they touch the workload portability narrative and the contracted commitment economics directly.
Google Cloud, AWS, and Microsoft Azure all carry per gigabyte data egress fees from the cloud region to the public internet and to other cloud regions. The published Google Cloud egress fee rate sits at twelve cents per gigabyte for the first one terabyte per month, dropping to seven cents per gigabyte above ten terabytes per month. In 2024 Google Cloud announced free egress for customers migrating off Google Cloud. The migration egress waiver mechanism remains available in 2026. The buyer side response inserts an egress credit clause at the PPA negotiation that obligates Google Cloud to provide a defined egress credit, typically two to four percent of the contracted commitment value, against actual egress fees across the contracted term. Google Cloud account teams have agreed to the egress credit clause at the upper customer scale when the buyer credibly raised the workload portability narrative.
The buyer side response also negotiates a price protection clause inside the PPA that locks the contracted per service rates across the contracted three year PPA term against any subsequent Google Cloud list price catalog change. Google has implemented documented list price increases on the BigQuery slot rate, the Vertex AI token rate, and selected compute family rates across 2023, 2024, and 2025. The price protection clause is the structural mechanism that prevents the contracted PPA footprint from inflating across the contracted term when Google lifts the list price catalog mid term.
A customer that falls below the contracted PPA aggregate commitment burn rate faces two distinct shortfall mechanics. First, the customer typically pays the contracted shortfall at the end of the contracted term. Second, the shortfall becomes the anchor for the next PPA commitment proposal. The buyer side response inserts a shortfall recovery clause at the original PPA negotiation that allows the customer to convert a defined percentage of the unused commitment into the next contracted term at no recovery penalty. Google Cloud account teams have agreed to the shortfall recovery clause at the upper customer scale when the buyer credibly raised the commitment risk narrative at the original negotiation.
The eighth and ninth commercial moves are the staged renewal posture that anchors the Google Cloud PPA against the AWS EDP and Microsoft Azure MACC alternatives, and the contracted exit and conversion right.
The staged renewal posture coordinates the Google Cloud PPA renewal against the AWS EDP and the Microsoft Azure MACC commitments. The optimal posture stages the three renewals across a twelve to eighteen month window so that at any time at least one of the three commitments is in active negotiation. The active negotiation provides the credible alternative conversation that the other two account teams cannot ignore. The practice has documented engagements where the customer deliberately accelerated or deferred the Google Cloud PPA renewal by three to six months to create the staged renewal posture and recovered an additional eight to seventeen percent across the broader hyperscaler commitment cycle. Read the related multi cloud competitive framework and the GCP negotiation leverage framework.
The buyer side response negotiates an explicit exit and conversion right at the original PPA negotiation that defines the customer's ability to migrate the contracted commitment to AWS or Microsoft Azure at a defined notice window without forfeiting the prepaid contracted balance. The exit and conversion right is the structural protection against the contractual lock that the multi year PPA otherwise carries. The clause typically includes the explicit treatment of the contracted prepaid balance at the conversion point, the explicit treatment of the unused contracted aggregate commitment, and the explicit migration assistance provisions that Google Cloud commits to provide at the conversion notice.
The buyer side response also negotiates a contracted volume commitment ramp clause at the PPA negotiation that defines the customer's ability to grow the contracted aggregate commitment across the contracted term at the contracted per service rates. The volume commitment ramp is the structural mechanism that allows the customer to expand the PPA footprint mid term without renegotiating the underlying agreement at a higher rate.
A Google Cloud Private Pricing Agreement is the upper customer scale commitment vehicle that wraps the customer's aggregate Google Cloud spend in a single multi year agreement, typically with a contracted minimum commitment, a discount band against the published list price catalog, the Vertex AI overlay, the BigQuery edition mapping, the marketplace pull through credit, and the egress credit clause.
The Committed Use Discount Program operates on a per service basis with resource specific, flexible, and Spend CUD structures sized against the customer's measured consumption. The Private Pricing Agreement operates as the aggregate enterprise commitment layered on top of the CUD portfolio, with a contracted minimum spend, an enterprise discount band, the Vertex AI overlay, the BigQuery edition mapping, and the enterprise commercial provisions across the contracted term.
The practice has documented engagements where the coordinated PPA negotiation delivered twenty four to forty one percent recovery against the Google Cloud account team's opening commitment proposal. The upper end is available when the buyer credibly stages the AWS EDP and the Microsoft Azure MACC alternatives, runs the Vertex AI overlay as a distinct conversation, and structures the marketplace pull through against the documented third party software register.
Google Cloud typically opens the PPA conversation at the contracted three year commitment around twenty to thirty million dollars and runs the PPA mechanic across the upper customer scale including the customer running a contracted commitment above one hundred million dollars across the contracted term. The PPA discount band scales with the contracted commitment tier.
The Vertex AI commitment overlay sits inside the PPA aggregate commitment by default. The buyer side response runs the Vertex AI overlay as a distinct conversation at the PPA negotiation rather than allowing the overlay to be absorbed into the aggregate commitment. The distinct Vertex AI conversation typically surfaces an additional four to nine percent discount layer above the aggregate PPA discount band on the Vertex AI rolled up spend.
The egress credit clause is the contractual provision that obligates Google Cloud to provide a defined egress credit, typically two to four percent of the contracted commitment value, against actual egress fees across the contracted term. The clause is one of the structural buyer side moves at the PPA negotiation because it directly addresses the workload portability narrative against AWS and Microsoft Azure.
The Google Cloud Marketplace pull through is the structural arrangement where third party software spend transacted through the Google Cloud Marketplace counts against the PPA aggregate commitment at a defined credit rate. The pull through credit sits at one hundred percent for defined software vendors, which is the highest pull through credit rate across the three hyperscaler marketplaces.
The most common mistake is committing to a single multi year aggregate spend commitment without structuring the underlying CUD portfolio against the steady state workload baseline. The aggregate PPA without the underlying resource specific CUD portfolio settles at the middle of the discount band rather than capturing the upper end of the band on the steady state baseline.
The Google Cloud PPA negotiation sits inside the broader Redress Compliance Google Cloud advisory practice. Engage with the practice on a single PPA cycle, on the coordinated CUD and PPA framework, or on the long running always on advisory subscription.
Google Cloud services practice · GCP Negotiation Framework · Google Cloud CUD Negotiation · Vertex AI and Gemini Negotiation
The practice runs four engagement models against the Google Cloud PPA commitment cycle. The Vendor Shield always on advisory subscription covers the Google Cloud account alongside the broader hyperscaler estate. The Renewal Program runs a structured twelve month managed sequence around the PPA commitment cycle. The Benchmark Program sizes the Google Cloud commitment against more than five hundred documented engagements. The software spend assessment sizes the Google Cloud account alongside the broader AWS, Microsoft, Oracle, SAP, and ServiceNow footprint. Read the related Google Cloud services practice, the Google Cloud CUD negotiation download, the Vertex AI and Gemini negotiation download, the BigQuery cost governance negotiation download, the multi cloud competitive framework, the AWS EDP negotiation download, the Microsoft EA renewal playbook, the Microsoft Azure negotiation, the GCP negotiation leverage framework, the multi vendor negotiation scorecard, and the software spend health check.
The Google Cloud negotiation leverage framework covering the staged commitment posture, the workload portability narrative, the Vertex AI commitment overlay, and the marketplace pull through that sits underneath the PPA.
Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for CIOs running the coordinated PPA and Vertex AI commitment cycle.
Google had structured our PPA as a single aggregate spend with the Vertex AI overlay embedded inside the commitment. Redress restructured the underlying CUD portfolio, raised Vertex AI as its own line item, converted the third party software register through the marketplace pull through, and staged the renewal against the AWS EDP. Thirty seven percent recovery on the three year contracted commitment.
We work for the buyer. Always. There is no other side of our table.
Google Cloud PPA signals, CUD portfolio signals, Vertex AI commitment signals, BigQuery edition signals, and the broader hyperscaler commitment signals from the Redress Compliance Google Cloud practice.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
