Azure Protectors

• 1: Azure Databricks Protector
• 1.1: Installing the Azure Databricks Protector
• 1.2: Uninstalling the Azure Databricks Protector

1 - Azure Databricks Protector

The Protegrity Big Data Protector for Azure Databricks delivers end‑to‑end data protection. Organizations deploying the Big Data Protector rely on modern, supported storage options. These include Workspace storage, Unity Catalog Volumes, and cloud object storage like ADLS Gen2 or Azure Blob Storage.

Designed to secure sensitive data across analytics pipelines, the Big Data Protector applies advanced tokenization and encryption during Spark execution and enforces centralized, policy‑driven controls. Whether installed via Unity Catalog Volumes for init script and .tgz delivery, the Protector ensures resilient execution across Azure Databricks clusters.

By embracing cloud‑native storage paths, this approach ensures long‑term compatibility with Databricks platform changes while maintaining Protegrity’s standard of seamless and transparent protection. Organizations can continue to process high‑value datasets on Azure Databricks with confidence knowing that sensitive information is secured across its lifecycle, even as the underlying platform evolves.

The Protegrity Big Data Protector for Azure Databricks empowers organizations to secure sensitive data across their analytics pipelines. This can be achieved by combining high‑performance protection mechanisms with flexible deployment models tailored for modern cloud architectures. Central to this capability are two approaches: Application Protector REST (AP REST) and Cloud Protector approach. Each approach is designed to address different customer requirements around scalability, infrastructure usage, and cost optimization.

1.1 - Installing the Azure Databricks Protector

Prerequisites

For more information about the prerequisites, refer to the sections listed below.

Register the jumpbox

To register and prepare the jumpbox, refer to Registering and preparing the jumpbox.

For the Application Protector REST Approach

For more information about the prerequisites, refer to For the Application Protector REST Approach.

For the Cloud Protector Approach

For more information about the prerequisites, refer to For the Cloud Protector Approach

Preparing the Environment

For more information about the preparing the environment, refer to Preparing the Environment.

Installing the Protector

For more information about installing the protector, refer to Installing the Protector.

Integrating the Azure Databricks Protector with Protegrity Provisioned Cluster (PPC)

To integrate the Azure Databricks Protector with PPC, perform the following steps:

When prompted for the ESA IP address, enter the PPC FQDN as configured in Automated script-based installation or Manual component-based installation. Ensure the FQDN does not exceed 50 characters. For the ESA listening port, enter 25400. These specific values are required to integrate the protector with the PPC.

Configuring the Protector

For more information about protector configuration, refer to Configuring the Protector.

1.2 - Uninstalling the Azure Databricks Protector

For more information about uninstalling the Azure Databricks Protector, refer to Uninstalling the Protector.