Six weeks after closing the $32 billion all-cash acquisition1 that stands as the largest in Google’s history, Wiz arrived at Google Cloud Next ‘262 with security coverage for AWS AgentCore, Microsoft Azure Copilot Studio, Salesforce Agentforce, and Databricks, alongside Google’s own Gemini Enterprise Agent Platform. The close happened on March 11. The announcements followed on April 22. The multi-cloud commitment made at acquisition time is now visible in shipping integrations.
The Acquisition Close and the Six-Week Sprint to Next ‘26
Google completed the Wiz acquisition on March 11, 20263, at $32 billion all-cash. Six weeks is not enough time to reorganize a security company of Wiz’s scale, which means the Next ‘26 product announcements were not improvised post-close. They were in development before the deal signed, which says something about how seriously Google was treating the multi-cloud positioning from the start.
Google explicitly committed to keeping Wiz multi-cloud at the time of acquisition close4, with products continuing to work across AWS, Microsoft Azure, and Oracle Cloud Platform. Google Cloud Next ‘26 was the first major public demonstration that the commitment was being honored in product, not in press statements alone. Whether the organizational incentives remain aligned over the next three to five years is a separate analysis.
What Wiz Shipped: Agent Studio Coverage Breakdown
The announced coverage spans four platforms: AWS AgentCore, Microsoft Azure Copilot Studio, Salesforce Agentforce, and Databricks, each representing a different vendor’s bet on where agent infrastructure lives.
The Databricks integration came with the most technical specificity. On April 20, 2026 (two days before the conference), Wiz published a detailed breakdown5 covering agentless discovery of Databricks workspaces, clusters, and Unity Catalog assets, extending the Wiz security graph across the Databricks Data & AI Platform. Unity Catalog is Databricks’ governance layer for data and AI assets; its inclusion in the discovery scope means Wiz’s graph now sees permission boundaries and asset relationships at the level where most enterprise Databricks security failures originate. The pre-conference timing suggests staged release coordination rather than conference-day stacking.
Committing to maintain coverage across four non-Google agent platforms simultaneously is a significant ongoing surface area. Each integration requires engineering investment in platforms controlled by competitors, and agent platform APIs are changing faster than traditional cloud APIs. The announcement functions as both a product statement and a signal to enterprise buyers that Wiz is not narrowing its coverage to match its new owner’s cloud preferences.
The broader coverage pattern reflects where agent-era attack surface is moving: away from IaaS compute primitives and toward managed orchestration layers that sit between cloud infrastructure and application code. A credential compromise inside a Copilot Studio agent or a misconfigured AgentCore execution role has a different blast radius than a misconfigured S3 bucket, primarily because agent frameworks often carry elevated permissions by design and their actions are harder to audit in real time. Wiz extending its graph here is a response to where the exposure is shifting.
Why Google Is Paying to Stay Cloud-Agnostic
Wiz’s platform is used by more than half of Fortune 100 companies6. At that scale, the install base is not predominantly GCP. It spans AWS, Azure, on-premises infrastructure, and multi-cloud environments assembled over years of vendor relationships and migration half-measures. Forcing a cloud-lock at acquisition time would not have converted any meaningful fraction of that base to GCP; it would have opened an uncontested replacement window for CrowdStrike, Palo Alto, and Orca Security.
Less obvious is how expensive maintaining genuine multi-cloud support actually is as an ongoing commitment. Platform-specific integrations with AWS AgentCore and Azure Copilot Studio require engineering investment in platforms controlled by competitors, active partnership maintenance with vendors who would prefer Wiz’s capabilities to be GCP-exclusive, and sustained organizational resistance to the natural pressure to prioritize GCP-specific features on the roadmap. None of that is a one-time cost. It compounds over each product cycle.
The argument for staying neutral holds until the customer base itself starts migrating. Enterprise cloud migrations take years, and companies running the bulk of their workloads on AWS are not moving because their CSPM vendor changed owners. In the short term, Google benefits more from retaining the existing install base intact than from converting any fraction of it to GCP. The medium-term calculus, past 2027, is where the analysis gets less settled.
The Tradeoff: Attach Revenue vs. Competitive Cloud Lift
By extending Wiz coverage to AWS AgentCore and Azure Copilot Studio, Google is actively deepening integration between a Google-owned security product and Amazon’s and Microsoft’s agent platforms. Analytically, managed agent orchestration and studio access rank among the higher-margin product lines at both companies, though vendor margin data for these specific platforms is not publicly confirmed. Google is, in effect, making competitors’ high-value platforms more credible for security-conscious enterprise buyers.
Google’s implicit bet is that the attach revenue from Wiz subscriptions across the full Fortune 1006 install base, regardless of which cloud the workload runs on, exceeds whatever competitive advantage Google would gain from forcing customers to choose between Wiz and their existing infrastructure. Given current enterprise switching costs, that bet is likely sound through 2027. The structural exposure appears in the years after: as AWS and Microsoft build native security graph capabilities of their own (a question of when, not whether), the value of Wiz’s cross-cloud attach erodes from both ends simultaneously.
At that point, Google’s options narrow: compete on Wiz product merit across all clouds, deepen GCP-specific advantages compelling enough to justify migration, or accept that $32 billion3 was priced for a window that does not stay open indefinitely.
What AWS and Microsoft Customers Should Watch
No AWS or Microsoft public response to the Next ‘26 agent-coverage announcements was available at research time. Neither hyperscaler is eager to amplify the message that a Google-owned security product is shipping deeper integration with their agent platforms. Neither appears to have moved to restrict it.
For security teams at enterprises running Wiz on non-GCP infrastructure, three questions have different answers today than they did on March 10:
- Does the Wiz contract include language on multi-cloud continuity or integration parity? The acquisition changes who is on the other side of that agreement, and vendor-level commitments do not automatically translate to contractual guarantees.
- What are the data residency implications if Wiz’s telemetry and graph infrastructure gradually migrates toward GCP primitives? Backend consolidation is common post-acquisition and rarely announced as a discrete event.
- How does your organization’s vendor risk policy handle security tooling now owned by a direct hyperscaler competitor?
None of these are active problems. They are questions worth asking while the public commitment is recent.
Implications for Future Cybersecurity M&A
What makes Google’s multi-cloud commitment notable is that it came under no obvious regulatory pressure to maintain neutrality. The Wiz acquisition did not trigger the market-dominance arguments that would force behavioral remedies as a closing condition. Google chose multi-cloud as strategy, not as concession. That distinction matters for how future deals price: an acquirer who commits to neutrality under regulatory pressure is different from one who commits because the economics demand it. The latter is a more durable signal for what the model actually is.
If Google demonstrates over the next two to three years that this approach generates better returns than a cloud-lock alternative, it narrows the playbook for future acquirers in the category. The cloud-lock strategy in security M&A was always theoretically expensive on a long enough horizon: acquire the asset at multi-cloud valuation, then destroy value by narrowing distribution to a single cloud’s customer base. Google’s approach inverts this. Extend distribution to competitors’ platforms, capture attach revenue across all clouds, avoid forcing the migration decision that accelerates churn. Whether this generates better five-year returns than the alternative is the empirical question the industry will now have data on.
The secondary effect is on seller expectations. If multi-cloud neutrality demonstrably preserves acquisition valuations, sellers will price it in. Acquirers planning to cloud-lock after close will find the valuation gap between a neutral asset and a captive one disappears into the negotiation. Wiz set a floor at $32 billion3 for a neutral, Fortune 1006-penetrated security graph in March 2026. The cost of narrowing that footprint, going forward, belongs on the buyer’s side of the ledger.
Frequently Asked Questions
Does the Oracle Cloud Platform commitment include agent-platform coverage?
Not yet. The Next ‘26 announcements added agent-platform integrations for AWS, Azure, Salesforce, and Databricks only. Oracle Cloud Platform was included in the broader multi-cloud continuity commitment made at acquisition close, but no agent-specific security graph extension for Oracle was announced — organizations running agent workloads on Oracle Infrastructure retain Wiz’s existing CNAPP capabilities without the newer agent-era extensions.
How does the Databricks security graph differ from Unity Catalog’s native controls?
Unity Catalog governs access policies and audit trails within Databricks. Wiz’s integration maps those permission boundaries into a cross-cloud graph that correlates Databricks asset relationships with infrastructure outside Databricks. A misconfigured Databricks service principal with excessive permissions reaching into an AWS account would only surface in Wiz’s graph because it spans both environments — Unity Catalog has no visibility beyond Databricks’ boundary.
Could AWS or Microsoft restrict Wiz’s API access to AgentCore or Copilot Studio?
Technically yes. Both platforms control their agent APIs and could impose rate limits, scope restrictions, or partnership requirements that limit a Google-owned product’s access depth. Neither company publicly responded to the Next ‘26 announcements, but the structural dependency is real: Wiz’s coverage for non-Google agent platforms relies on API access that competitors have no contractual obligation to maintain at current levels. This is the specific risk that differentiates multi-cloud security tools from cloud-native ones.
What prior hyperscaler security acquisition is the closest precedent for this multi-cloud approach?
Cisco kept Duo Security platform-neutral after its 2018 acquisition, but at $2.35B the strategic stakes were far lower. The closer structural analogy is Broadcom’s post-close handling of VMware — a multi-cloud asset maintained broadly across competing hypervisors — though VMware targets infrastructure, not security. No cybersecurity acquisition near this $32B scale has been operated with explicit multi-cloud neutrality, meaning Google is working without a tested template.
What should change in vendor risk assessments for enterprises running Wiz on AWS or Azure?
Add a review cadence tied to Wiz backend infrastructure changes, not just product roadmap updates. Post-acquisition backend consolidation toward GCP primitives is common and rarely announced as a discrete event, which means telemetry routing, graph storage, and data residency can shift without triggering contractual change-of-control clauses. Teams should also confirm whether their Wiz agreement includes integration-parity guarantees across clouds — vendor-level commitments made at acquisition close do not automatically carry contractually.