A working framework for CIOs, analytics leaders, automation leaders, and procurement teams negotiating the 2026 Microsoft Power Platform renewal. Recover eighteen to thirty six percent against the opening proposal.
A working framework for CIOs, analytics leaders, automation leaders, citizen developer program owners, and procurement teams negotiating the 2026 Microsoft Power Platform renewal. Recover eighteen to thirty six percent against the opening proposal through user pool reconciliation, capacity right sizing, and a documented competitive exit path.
Microsoft Power Platform sits at the center of the enterprise low code and citizen developer movement. The platform spans Power BI analytics, Power Apps low code applications, Power Automate workflow automation, Power Pages external sites, Copilot Studio conversational agents, and the underlying Dataverse data backbone.
The 2026 commercial discussion sits at a difficult fork. Microsoft pushes customers from individual product subscriptions toward broader Power Platform suite commitments. Copilot Studio expansion adds new line items inside the renewal proposal. The Microsoft Fabric capacity model overlaps with Power BI Premium per capacity.
The 2026 Power Platform renewal cycle uses six commercial vectors against the buyer.
This paper sets out the Redress Compliance 2026 Power Platform renewal negotiation framework. Refined across more than five hundred enterprise software engagements at Industry recognized scale, with over two billion dollars under advisory.
The framework stages the renewal response across user pool reconciliation, Power BI Premium per capacity right sizing, Power Apps per user versus per app decision, Power Automate flow accounting, Copilot Studio adoption tracking, Dataverse capacity right sizing, MACC drawdown evaluation, and a documented competitive exit path.
The exit path covers Salesforce Flow and Lightning Platform, ServiceNow Now Platform, OutSystems, Mendix, Appian, Tableau, Qlik Sense, and selected UiPath automation workflows.
The single most valuable 2026 move is documenting the active analyst, app maker, and flow owner baseline alongside the Power BI Premium per capacity workload profile inside the procurement file before the opening commercial discussion.
Default 2026 Power Platform posture inflates the contracted commitment across every metric. The Microsoft EA framework creates additional levers through MACC drawdown that customers without buyer side advisory rarely capture on the consumption tier.
Read the related Microsoft EA Renewal Playbook, the Microsoft Azure ELA Negotiation, the Microsoft Fabric Negotiation, the Microsoft Services, and the Microsoft Knowledge Hub.
Microsoft Power Platform started as a unifying brand around Microsoft Power BI, Microsoft Flow, and Microsoft PowerApps in 2018. The brand consolidation pulled the three separate analytics and low code products into a single platform identity.
The 2019 to 2021 cycle expanded the platform across analytics, applications, automation, and the data backbone. Power Virtual Agents added conversational AI capability. Dataverse (formerly Common Data Service) became the underlying data layer. AI Builder added prepackaged machine learning models.
The 2022 to 2024 cycle introduced Copilot Studio as the next generation conversational AI agent builder. The rebrand from Power Virtual Agents acknowledged the broader generative AI integration. The 2025 launch of agent skills expanded Copilot Studio into autonomous agent territory.
The 2024 to 2026 portfolio compression aligned Power Platform with the broader Microsoft Copilot strategy. Microsoft 365 Copilot, Copilot for Dynamics 365, and Copilot Studio together form the customer facing Copilot suite. GitHub Copilot covers the developer Copilot surface. The Power Platform Copilot integration deepens across Power BI, Power Apps, and Power Automate.
The 2026 commercial discussion folds four structural pressures. List price increases took effect across the Power Platform catalog with selected double digit moves. Power BI Premium per capacity migration toward Microsoft Fabric F SKUs reshapes the commercial framework. Copilot Studio expansion drives new line items. Dataverse capacity growth compounds across applications.
The 2026 renewal wave hits the consolidated Power Platform installed base. Documented commercial uplift compounds across list price increases, Copilot Studio upsell, Power BI Premium capacity growth, Dataverse capacity growth, and the multi year commitment.
| Customer profile | Typical 2026 Power Platform scope | Annual 2026 commitment |
|---|---|---|
| Mid market | 500 to 2,500 Power BI Pro, selective Power Apps, light Power Automate | USD 0.15m to 0.85m |
| Large enterprise | 4,000 to 12,000 Power BI Pro, Power Apps and Automate per user, Premium P2 | USD 1.2m to 4.8m |
| Upper enterprise | 18,000 plus Power BI Pro, full Power Apps and Automate, Premium P3 or F64+, Copilot Studio | USD 5m to 22m |
| Three year commitment value band | Aggregate term value at upper enterprise scale | USD 15m to 66m |
| Product or capacity unit | List rate | Negotiated band at upper enterprise scale |
|---|---|---|
| Power BI Pro (per user per month) | USD 10 | USD 6 to USD 8 |
| Power BI Premium per user (per user per month) | USD 20 | USD 12 to USD 16 |
| Power BI Premium P1 capacity (per month) | USD 5,000 | USD 3,500 to USD 4,200 |
| Power BI Premium P3 capacity (per month) | USD 20,000 | USD 13,500 to USD 16,500 |
| Microsoft Fabric F64 capacity (per month) | USD 8,400 | USD 5,800 to USD 7,000 |
| Power Apps per app (per user per app per month) | USD 20 | USD 12 to USD 16 |
| Power Apps per user (per user per month) | USD 40 | USD 25 to USD 32 |
| Power Automate per user (per user per month) | USD 15 | USD 9 to USD 12 |
| Power Automate Process (per flow per month) | USD 150 | USD 95 to USD 120 |
| Copilot Studio (per tenant per month base) | USD 200 | USD 130 to USD 165 |
| Copilot Studio messages (per 25k pack) | USD 200 | USD 130 to USD 165 |
| AI Builder credits (per million per month) | USD 500 | USD 325 to USD 415 |
Each industry vertical carries a documented 2026 Power Platform renewal pattern. Read the Microsoft Fabric Negotiation, the Microsoft Dynamics 365 Negotiation, and the Microsoft Teams Enterprise Negotiation.
The single largest commercial recovery vector on a 2026 Power Platform renewal sits inside the user inventory. Every Power Platform user account produces documented session and activity telemetry inside the Microsoft 365 admin portal and the Power Platform admin center.
Default 2026 Microsoft posture rolls the prior user pool forward without reconciliation against current active user requirements. The pool includes leavers, role changes that moved users out of analytics or app development workflows, and shared workstation accounts.
The reconciliation lives across the Power BI tenant admin, the Power Platform admin center, the Microsoft 365 admin portal, the Entra ID source of truth, and the Workday or HR active employment record.
Pull the Power BI tenant admin user list filtered to documented active sign in and active workspace usage within ninety days. Compare against the Entra ID provisioning source. Reconcile against the Workday or HR active employment status.
That count is the active Power BI Pro baseline. Compare the active baseline against the contracted Power BI Pro pool.
Power BI Premium per user at USD 20 per user per month covers individual premium features. Power BI Premium per capacity (P SKUs) starting at USD 5,000 per month covers shared capacity with free user read access.
The break even runs roughly five hundred Pro users with documented premium feature need versus the P1 capacity. Above that scale, capacity usually compresses cost. Below that scale, Premium per user usually wins.
The 2026 Microsoft Fabric F SKU launch overlaps with Premium per capacity. The F64 SKU at USD 8,400 per month roughly matches P1 capacity with broader Fabric capability. Read the Microsoft Fabric Negotiation.
Every 2026 Power Platform renewal should land at the vendor with this evidence pack already filed inside the procurement record.
Power BI Premium per capacity sits at the high end of the Power BI commercial framework. P1 capacity starts at USD 5,000 per month. P3 capacity runs USD 20,000 per month. P4 capacity runs USD 40,000 per month. The 2026 Microsoft Fabric F SKU overlap added F2 through F2048 as alternative capacity tiers.
Default 2026 posture sizes Premium per capacity ahead of documented refresh, concurrency, and workload requirements. Most environments find the contracted capacity exceeds actual workload by twenty five to forty five percent.
Pull ninety days of capacity metrics from the Power BI Premium Utilization and Metrics app. Document peak refresh CPU, peak query CPU, and peak memory usage across business hours.
Right size the capacity tier against documented peak utilization. Most environments find P3 customers can run on P2. P2 customers can run on P1. P1 customers may move to Premium per user or to Fabric F SKUs.
The 2026 Microsoft Fabric F SKU framework introduces capacity pause capability. Customers can pause F capacity during off hours to compress consumption cost. The pause capability is not available on Premium per capacity P SKUs.
The Microsoft Fabric F SKUs replace Premium per capacity at most upper enterprise customers in 2026. The F64 SKU provides the equivalent compute capacity to P1 at lower cost when paused during off hours. The broader F SKU range provides finer grained capacity tier selection.
The procurement file should evaluate migration from Premium per capacity to Fabric F SKUs at every renewal. The migration unlocks the pause capability and aligns Power BI with the broader Fabric data platform.
Power Apps sells in two distinct licensing models. Per user at USD 40 per user per month covers unlimited apps. Per app at USD 20 per user per app per month covers a single app per user.
Default 2026 posture pushes the per user license broadly across the app maker and end user pool. Most environments find a meaningful percentage of users only access one or two apps. The per app license compresses cost at customers with concentrated app usage patterns.
The break even runs at two apps per user. Users accessing one app run cheaper on per app. Users accessing two apps run roughly equivalent. Users accessing three or more apps run cheaper on per user.
Pull the Power Apps maker portal app usage telemetry per user across the trailing ninety days. Map users to their app access pattern. Assign per app to single app users and per user to multi app users.
The compression typically cuts the aggregate Power Apps cost by twenty to thirty percent against the default per user assignment across all users.
Power Pages provides external facing portal capability at separate per page view pricing. The 2026 commercial framework prices Power Pages at documented per page view rates against authenticated and anonymous users.
The procurement file should evaluate Power Pages against the embedded Power Apps Portal capability. Customers without external facing portal requirements should avoid the Power Pages line entirely.
Power Automate provides workflow automation across cloud and desktop. The 2026 commercial framework prices the platform at per user, per flow, and Process Mining variants with consumption based add ons.
Per user at USD 15 per user per month covers unlimited cloud flows per user. Per flow at USD 150 per flow per month covers a single flow with unlimited executions. Process Mining at USD 5,000 per tenant per month covers the process mining capability.
Pull the Power Automate cloud flows inventory per user. Document flow owner, trigger frequency, and last run timestamp.
Users with documented active flows justify the per user license. Users with dormant flows or no flow ownership should rotate off the per user license. The compression typically cuts the per user pool by twenty five to forty percent.
Power Automate Desktop covers attended desktop automation. Unattended desktop automation requires the Power Automate Unattended add on at USD 150 per bot per month. The procurement file should map every unattended bot against documented automation workflows and active business value.
Default 2026 posture funds unattended bots across documented and undocumented use cases. Right sizing the unattended bot pool against active automation workflows typically compresses the line by thirty to fifty percent.
Copilot Studio replaced Power Virtual Agents as the next generation conversational AI agent builder. The 2026 commercial framework prices Copilot Studio at USD 200 per tenant per month for the base plus consumption based message packs at USD 200 per 25,000 messages.
Default 2026 posture funds Copilot Studio capacity ahead of documented agent count and message volume. The 2024 to 2026 Copilot Studio rollout introduced significant capacity inflation across early adopter accounts.
Pull the Copilot Studio agent inventory per tenant. Document monthly message volume per agent across the trailing twelve months. Map agents against documented business use cases.
Inactive agents with no documented business use case should rotate off the platform. Active agents with documented message volume justify the capacity tier matching that volume.
The compression typically cuts the Copilot Studio line by twenty five to forty percent against the default capacity tier funded ahead of usage.
Microsoft 365 Copilot at USD 30 per user per month covers Word, Excel, PowerPoint, Outlook, and Teams. Copilot Studio at USD 200 per tenant per month covers custom conversational agents.
The 2024 to 2026 rollout introduced documented capability overlap. M365 Copilot covers selected conversational workflows that previously required Copilot Studio. The procurement file should map M365 Copilot capability against each Copilot Studio agent before renewal commitment. Read the GitHub Enterprise Copilot Negotiation for the related developer Copilot framework.
Dataverse provides the data backbone across Power Platform and Dynamics 365 applications. Each application includes base Dataverse capacity. Additional capacity ships as separate add ons across database, file, and log.
The 2026 framework folds documented Dataverse capacity growth across all three storage tiers into the renewal uplift. Default 2026 posture funds capacity ahead of documented consumption rates.
Pull documented Dataverse consumption across database, file, and log capacity per environment from the Power Platform admin center. Compare against the contracted capacity per environment.
Most environments find the included capacity per application user exceeds active consumption. The contracted capacity add ons often size above documented growth rates.
Right sizing the Dataverse capacity tier against documented consumption growth typically saves fifteen to twenty five percent against the contracted Dataverse add on line.
The Power Platform admin center allows multiple environments per tenant. Default 2026 posture creates new environments without consolidating dormant ones.
The procurement file should map every Dataverse environment against active application and active user counts. Dormant environments with no active applications should be removed entirely.
Selected Power Platform consumption can route through the Azure Microsoft Azure Consumption Commitment (MACC) vehicle in 2026. The drawdown applies to Power BI Premium per capacity, Microsoft Fabric F SKU capacity, Dataverse capacity, Copilot Studio messages, AI Builder credits, and embedded Azure infrastructure.
The core Power Apps and Power Automate per user subscriptions remain on the standard Microsoft Customer Agreement enterprise pricing track. The MACC drawdown applies to the consumption tier.
Default 2026 posture leaves Power Platform consumption outside the MACC drawdown vehicle. Customers with multi year MACC commitments should evaluate routing the consumption tier through the MACC.
The MACC drawdown break even test asks three questions. Does the customer have an active multi year MACC commitment? Does the customer face MACC drawdown shortfall risk in the current term? Does the MACC discount profile beat the standalone Power Platform consumption profile?
Positive answers across all three justify MACC drawdown evaluation. The procurement file models the MACC drawdown scenario against the standalone Power Platform commercial scenario across the consumption tier.
The MACC drawdown often beats the standalone Power Platform commercial framework at upper enterprise scale on the consumption tier. The drawdown provides flexibility on commitment timing. Read the Microsoft Azure ELA Negotiation.
The MACC sits inside the broader Microsoft Enterprise Agreement framework. The MACC drawdown decision should coordinate with the broader Microsoft EA renewal cycle including Microsoft 365, Azure, GitHub, Dynamics 365, and the broader portfolio.
Customers with simultaneous Microsoft EA and Power Platform renewals should structure both inside a single coordinated commercial discussion. The combined leverage typically compresses both lines by additional five to ten percent beyond the standalone optimization.
The procurement file should align Power Platform term dates with the Microsoft EA term dates. The aligned dates simplify MACC drawdown management. Read the Microsoft EA Renewal Playbook.
The 2026 Power Platform commercial discussion carries a documented exit path against the alternative low code, automation, and analytics platforms. OutSystems, Mendix, Appian, Salesforce Flow and Lightning Platform, ServiceNow Now Platform, Tableau, Qlik Sense, and UiPath each cover documented commercial pressure on the Power Platform installed base.
The exit path does not require complete migration. The procurement file files the documented capability to migrate selective workloads against the Power Platform commercial position.
OutSystems provides the high control enterprise low code platform with documented enterprise scale. Mendix provides the equivalent footprint inside the Siemens portfolio.
Both platforms compete with Power Apps at the high control low code tier. The procurement file should evaluate these alternatives against the Power Apps commitment at customers with complex application requirements.
Salesforce Flow and the broader Lightning Platform cover the citizen developer workflow at customers with established Salesforce footprints. ServiceNow Now Platform covers the equivalent footprint at customers with established ServiceNow footprints.
Both platforms compete with Power Apps and Power Automate at the citizen developer tier. The procurement file should evaluate these alternatives at customers consolidating around Salesforce or ServiceNow. Read the Salesforce Sales Cloud Negotiation and the ServiceNow Now Platform Negotiation.
Tableau covers the analytics workflow with documented enterprise scale. Qlik Sense covers the equivalent footprint with documented enterprise scale across the QlikView and Qlik Sense product lines.
Both platforms compete with Power BI at the analytics tier. The procurement file should evaluate these alternatives against the Power BI Pro and Premium commitment. Read the Tableau Cloud Enterprise Negotiation.
Across more than five hundred enterprise software engagements, six traps recur in 2026 Power Platform renewals. Each carries a documented commercial cost. Each has a known corrective move inside the procurement file.
Pull the Power BI tenant admin user list filtered to active workspace usage in the trailing ninety days. Reconcile against the Entra ID provisioning source. Compare against the Workday or HR active employment status.
The team that walks into the commercial discussion with reconciliation filed walks out with eighteen to thirty six percent recovery. The team that walks in without reconciliation walks out with ten to twenty two percent uplift. The active analyst baseline before the meeting is the single biggest discriminator across five hundred engagements.
Pull the Power Apps maker portal app usage telemetry per user across the trailing ninety days. Map users to their app access pattern. Assign per app to single app users at USD 20 per user per app per month.
Reserve the per user license at USD 40 per user per month for users accessing three or more apps. The compression typically cuts the aggregate Power Apps cost by twenty to thirty percent against the default per user assignment. Combine with the Power Automate per user inventory reconciliation for additional compression.
Pull ninety days of capacity metrics from the Power BI Premium Utilization and Metrics app. Document peak refresh CPU, peak query CPU, and peak memory usage. Right size the capacity tier to documented peak utilization.
Evaluate migration from Premium per capacity P SKUs to Fabric F SKUs at every renewal. The F SKU framework introduces capacity pause capability that compresses consumption cost during off hours. The migration aligns Power BI with the broader Fabric data platform and unlocks the pause capability not available on P SKUs.
Pull the Copilot Studio agent inventory per tenant with monthly message volume per agent across the trailing twelve months. Rotate inactive agents off the platform. Size capacity to active message volume plus documented headroom.
Pull Dataverse consumption per environment across database, file, and log storage. Compare against the contracted capacity. Right size the capacity tier against documented consumption growth. Consolidate dormant environments. The combined compression often saves twenty to thirty five percent across Copilot Studio and Dataverse capacity lines.
Run the MACC drawdown break even test. Customers with active multi year MACC commitments and MACC drawdown shortfall risk should route the consumption tier through the MACC vehicle. Align Power Platform term dates with the Microsoft EA term dates.
Map every contracted Power Platform line against the documented competitive equivalent. OutSystems and Mendix map to high control Power Apps. Salesforce Flow and ServiceNow Now Platform map to citizen developer Power Apps and Power Automate. Tableau and Qlik Sense map to Power BI. UiPath maps to Power Automate Desktop unattended automation.
File the exit path in the first commercial meeting. Reference it at every escalation point. Cap annual uplift at three to four percent with documented downgrade rights.
Microsoft Power Platform is the low code business application platform from Microsoft. The 2026 portfolio spans Power BI for analytics, Power Apps for low code application development, Power Automate for workflow automation, Power Pages for external facing websites, Copilot Studio for conversational AI agents, and Dataverse for the underlying data backbone.
The platform integrates deeply with Microsoft 365, Dynamics 365, Azure, and the broader Microsoft Copilot suite. AI Builder ships prepackaged machine learning models for use across Power Apps and Power Automate.
The 2026 Power Platform list pricing runs from USD 10 per user per month on Power BI Pro to USD 20 per user per month on Power BI Premium per user. Power Apps per app sits at USD 20 per user per app per month.
Power Apps per user sits at USD 40 per user per month. Power Automate per user sits at USD 15 per user per month. Copilot Studio base sits at USD 200 per tenant per month.
Negotiated bands compress these by twenty to forty percent at upper enterprise scale with documented user pool reconciliation and capacity right sizing.
Documented opening commercial uplift bands of ten to twenty two percent against the prior contracted Power Platform run rate at upper enterprise scale.
The 2026 framework folds list price increases, Copilot Studio upsell, Power BI Premium per capacity to per user migration, Dataverse capacity growth, and the multi year commitment uplift.
Power BI Premium ships in two distinct models. Power BI Premium per user lists at USD 20 per user per month for individual premium features. Power BI Premium per capacity (P SKUs) lists from USD 5,000 per month for the P1 tier.
The Microsoft Fabric capacity model with F SKUs is replacing selected Premium per capacity workloads in 2026. The F64 SKU at USD 8,400 per month roughly matches P1 capacity with the broader Fabric capability and the capacity pause feature not available on P SKUs.
Eighteen to thirty six percent against the Power Platform opening proposal across the contracted user pool.
Recovery requires documented user pool reconciliation against active analysts and app makers, Copilot Studio agent adoption tracking, Power BI Premium per capacity right sizing, Dataverse capacity right sizing, MACC drawdown evaluation, and a documented Salesforce, ServiceNow, OutSystems, Mendix, Appian, and Tableau exit path.
Selected Power Platform consumption can route through the Azure Microsoft Azure Consumption Commitment vehicle in 2026. The drawdown applies to Power BI Premium per capacity, Microsoft Fabric F SKU capacity, Dataverse capacity, Copilot Studio messages, AI Builder credits, and embedded Azure infrastructure.
The core Power Apps and Power Automate per user subscriptions remain on the standard enterprise agreement. Customers with multi year MACC commitments should evaluate routing the consumption tier through the MACC vehicle.
Copilot Studio is the conversational AI agent builder inside Power Platform. The 2026 line replaces the legacy Power Virtual Agents brand. Copilot Studio sells at USD 200 per tenant per month for the base capacity plus consumption based message packs at USD 200 per 25,000 messages.
The 2026 framework sizes Copilot Studio against documented agent count, message volume, and active end user adoption. Default 2026 posture funds capacity ahead of documented usage.
The contracted exit path covers documented migration to Salesforce Flow and Lightning Platform, ServiceNow Now Platform, OutSystems, Mendix, Appian, UiPath, Tableau, and Qlik Sense.
The documented exit path is a meaningful commercial leverage vector inside the 2026 Power Platform commercial discussion alongside the MACC drawdown evaluation and the product by product right sizing levers.
The 2026 Power Platform renewal framework sits inside the broader Redress Compliance Microsoft advisory practice. Engage on a single 2026 Power Platform renewal cycle, the coordinated Microsoft EA plus MACC plus Power Platform portfolio renewal, or the always on Vendor Shield advisory subscription.
Microsoft Knowledge Hub · Microsoft Services · Microsoft EA Renewal Playbook · Microsoft Azure ELA Negotiation · Microsoft Fabric Negotiation · Microsoft Dynamics 365 Negotiation · Microsoft Teams Enterprise Negotiation · Multi Vendor Negotiation Scorecard · Software Spend Assessment · Vendor Shield
The practice runs four engagement models against the 2026 Power Platform renewal cycle.
Continue with the Microsoft EA Renewal Playbook, the Microsoft Azure ELA Negotiation, the Microsoft Fabric Negotiation, the Microsoft Dynamics 365 Negotiation, the multi vendor negotiation scorecard, and the complete white paper library.
Read the GitHub Enterprise Negotiation, the Microsoft Teams Enterprise Negotiation, the Salesforce Sales Cloud Negotiation, the ServiceNow Now Platform Negotiation, and the Tableau Cloud Enterprise Negotiation.
The Microsoft EA Renewal Playbook covers the full enterprise Microsoft Agreement framework including the MACC drawdown vehicle that selected Power Platform consumption can route through at upper enterprise scale.
Used across more than five hundred enterprise engagements. Independent. Buyer side.
Microsoft had opened the 2026 Power Platform renewal at a USD 4.8m three year commit across 14,000 Power BI Pro users, broad Power Apps per user attach, P3 capacity at two nodes, and aggressive Copilot Studio capacity assumptions.
Redress separated the contracted user pool from the active analyst baseline. Two thousand four hundred users had no documented workspace usage in ninety days. The active Power BI Pro baseline was 11,600 after reconciliation.
The Power Apps per user versus per app analysis identified 3,200 users active on a single app who should sit on the per app license at USD 20 per user per app per month rather than per user at USD 40. The aggregate Power Apps cost compressed by twenty eight percent.
The Power BI Premium per capacity right sizing dropped P3 capacity from two nodes to one node based on documented refresh and concurrency utilization. The Microsoft Fabric F SKU migration evaluation showed F64 plus pause capability beat the standalone P1 capacity on aggregate cost.
The 2026 renewal closed at USD 3.1m against the USD 4.8m opening proposal. Thirty five percent recovery on the contracted opening commercial proposal across the consolidated Power Platform footprint. The MACC drawdown vehicle absorbed the consumption tier alongside the Microsoft EA renewal.
We work for the buyer. Always. There is no other side of our table.
Power Platform, Microsoft Fabric, Power BI, Azure, GitHub, Dynamics 365, and the broader Microsoft commercial signals from the Redress Compliance advisory 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.
