You will learn what the Zero Copy v2 connector exposes in Snowflake, which pieces are generally available versus in preview, and how governance and private connectivity are handled across the two platforms.
Connect enterprise data
Give it shared meaning
Turn it into trusted context
Act on it in agents
Data moves from enterprise data to action in four stages, as the article frames Data 360's role
Salesforce describes Data 360 as a context layer for AI agents, and presents its Zero Copy partnership with Snowflake as the way to reach governed data where it already lives rather than copying it through ETL pipelines. The article reports more than 1,000 joint customers running workloads with native Zero Copy, and presents this as the basis for Agent Context Engine, which combines structured data, unstructured content, knowledge graphs and agent memory.
The technical changes are the substance here. The v2 Zero Copy connector presents Data 360 objects as native Apache Iceberg tables inside a customer’s Snowflake account, queryable with SQL and usable with Streams and Dynamic Tables for near real-time change capture. OpenID Connect authentication secures access. Expanded Zero Copy with Horizon Catalog adds direct file federation with Snowflake-managed Iceberg tables, and Data 360 Private Connect Multicloud allows Data 360 on AWS to reach Snowflake on Azure without public internet traffic.
Availability is staged. The v2 connector and Private Connect for Snowflake on Azure are generally available, Expanded Zero Copy with Horizon Catalog and Snowflake Cortex Agents are in public preview, and the Salesforce and Informatica MCP servers in Cortex are in private preview. Tableau support for Snowflake semantic views is planned for general availability in early 2027.
You will learn the setup steps for the Zero-Copy V2 connector, including the enrollment code handoff, consumer grants and legacy schema aliases.
Why read this
You will also see where change tracking via streams failed in one test.
Create connector and get Enrollment ID
Create Snowflake V2 target in Salesforce
Link Data Share to the target
Mount shared data and grant access
The V2 setup runs between the Snowflake admin and the Salesforce admin in four steps
The author revisits connecting Salesforce data to Snowflake and reports that the V2 connector simplifies setup. The enrollment code replaces manual credential configuration, authentication uses OpenID Connect, and friendly names reduce SQL cleanup. Legacy schema aliases and grant comparisons before and after migration help keep existing access intact.
The walkthrough covers creating the connector and retrieving the Enrollment ID, then the Salesforce-side steps: creating a Snowflake V2 Data Share target, linking a Data Share to it, and mounting the shares in Snowflake as a linked database. It also covers granting usage and select privileges on existing and future views to the consuming role, and the choice between legacy and friendly naming.
The author’s incremental test did not work. A stream on an exposed view failed with a change tracking error involving unmanaged Iceberg tables, so current-state queries worked but change feeds did not through that path. The author recommends confirming the supported source object and stream setup, then testing inserts, updates and deletes end to end before relying on downstream history.