The setup uses a Databricks-managed central environment that runs independently of both parties to prevent administrative overreach. Leveraging OpenSharing, the clean room gains read-only access to live data tables without making unnecessary copies. LiveRamp also supplies its proprietary identity code and private models directly to this secure workspace without revealing intellectual property. Once the job completes, resolved RampIDs are shared back via OpenSharing for immediate downstream analytical use.
Key points
Enterprises can generate RampIDs locally to eliminate the security risks of exporting cus…: Enterprises can generate RampIDs locally to eliminate the security risks of exporting customer records externally.
Proprietary vendor code and sensitive customer datasets remain isolated and confidential…: Proprietary vendor code and sensitive customer datasets remain isolated and confidential throughout the entire matching process.
Resolved identifier outputs flow directly back to native environments to immediately supp…: Resolved identifier outputs flow directly back to native environments to immediately support artificial intelligence and analytics workloads.
Sources checked by our analysis pipeline: 1
A look at how LiveRamp Embedded Identity runs inside Databricks Clean Rooms: the central clean room, how OpenSharing connects each party's data, who can see what, and where the results land.
by Ryan Werth and Johanna Hughes
Historically on Databricks, to resolve customer records to a person-based ID such as RampID, a data team had to export PII to an outside service, wait for a match file, and load it back in. Each step added a pipeline to maintain, a copy of sensitive data to govern, and a delay before the results were usable. Packaged clean rooms disrupt this traditional pattern by removing the need for that round-trip.
LiveRamp Embedded Identity on Databricks brings the identity service to the data. Anyone can take advantage of LiveRamp's identity resolution solution without having their precious customer data leave their owned-storage. With minimal set-up, customers can receive a resolved list of RampIDs back in their environment where their analytics and AI workloads already run, all while maintaining Unity Catalog governance. These appended RampIDs to the customers’ data become the match key for high…
Enterprise users can now seamlessly query and govern shared datasets without duplicating assets between Databricks and Google Cloud environments. This partnership leverages Lakehouse Federation and open standards to eliminate costly data redundancy while preserving essential governance tags across both platforms. As a result, organizations can deploy cross-cloud analytics and artificial intelligence agents more efficiently and securely.
Public sector organizations can now access advanced data and artificial intelligence tools within a dedicated, compliance-focused cloud environment. Built identically to its commercial counterpart, the offering allows government teams to prepare their architectures using existing Microsoft commitments before handling mission-critical defense workloads. This step lays the groundwork for agencies to eventually run sensitive operations under upcoming federal security authorizations.
Tailscale devices typically depend on reaching a central coordination server upon reboot to fetch critical network details and establish secure connections. By preserving this network map directly to local storage, machines can immediately connect to existing peer nodes even through complete coordination server outages or poor internet links. This client-side change significantly hardens connection reliability for users operating across unstable environments.