The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Data 360 connects to Snowflake through Zero Copy without moving data (opens in a new tab)

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.

  1. Connect enterprise data
  2. Give it shared meaning
  3. Turn it into trusted context
  4. 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.

Read the original at Salesforce Blog (opens in a new tab)

Worth reading?

Recommended

How Data 360 compiles governed context for artificial intelligence agents at production scale (opens in a new tab)

Readers will understand how the Agent Context Engine retrieves, reconciles, and packages authorized evidence into token-efficient Context Packs for AI agents.

Why read this

The piece also explains how Data 360 separates runtime state from durable memory to maintain governance across models and channels.

Salesforce Engineering describes how Data 360 assembles governed, authorized context for AI agents without loading an entire enterprise data estate into every prompt. The core challenge is identifying the requester, purpose, authority and freshness needs, retrieving evidence from structured and unstructured sources, reconciling conflicts, and applying access, masking, residency, consent and purpose controls, all within token, latency, freshness and cost budgets. Data 360 serves as a shared runtime foundation across Salesforce, platforms such as Databricks and Snowflake, operational systems and knowledge bases, with data kept authoritative where it lives through ingestion and Zero Copy. The article cites Q2 FY27 production usage of 104.3 trillion connected records, including 81.5 trillion Zero Copy rows.

The Agent Context Engine works in two directions. On the outbound path it moves through six runtime stages: Resolve (identify requester, agent, purpose, authority, entities and freshness), Plan (choose access paths such as relational, search, graph, RAG, streaming and federated), Reconcile (rank evidence while keeping conflicts visible), Govern (apply controls before retrieval or action), Compile (fit evidence, working state, memory and citations into a token-fit Context Pack and action contract), and Learn selectively (return typed interaction traces and decide what to promote, update or expire). On the inbound path, conversations, tool calls, decisions and outcomes return as traces for audit and evaluation. Only approved facts move into durable memory, and only validated outcomes become learnings.

Data 360 separates runtime state into four forms: working context for the current reasoning step, short-term memory for the active trace across turns, long-term memory for approved facts and commitments that belong to the enterprise, and learnings distilled from validated outcomes and corrections. The article stresses that a transcript is not automatically enterprise memory. Trusted Context sits within Salesforce’s Enterprise AI Harness, alongside Trusted Models, Agency, Actions, Governance and Security, and the same governed context reaches Agentforce, custom and partner agents, and SaaS assistants through SDKs, API adapters, MCP and APIs. The authors also report performance results across production retrieval, high-concurrency queries, analytical SQL, ClickBench, TPC-derived and LDBC graph workloads, while noting these are not directly comparable. They propose an Agentic Context Benchmark, which would count a result only when the resulting action is both authorized and completed. New capabilities are planned to begin rolling out in early FY28, with availability varying by product, region and agreement.

Read the original at Salesforce Engineering (opens in a new tab)

Worth reading?