Use this task to create an Azure Blob Storage cloud file connector. Azure connectors support two authentication methods: key-based authentication using storage account access keys, or managed identity-based authentication using Azure managed identities.

Prerequisites

  • You have an Azure storage account with a container holding files you want to mask or discover.

  • For key-based authentication (AZURE_SECRET): You have a storage account access key.

  • For managed identity authentication (AZURE_MANAGED_IDENTITY): Your compliance node is running on an Azure VM with a managed identity that has access to the storage container.

Steps

  1. In the left navigation pane, click Compliance > Connectors.

  2. Click + Connector.

  3. In the Details step:

    1. Enter the connector name.

    2. (Optional) Add tags using Tag Key and Tag Value, then click + Tag.

  4. Click Next.

  5. In the Configuration step:

    1. Select the Job Orchestrator that will run masking and discovery jobs using this connector.

    2. Select the Source Type: File - Delimited, File - Fixed Width, File - JSON, File - XML, or File - Parquet. Note: PARQUET file type is not supported with managed identity authentication. File type cannot be changed after creation.

    3. Select the Connection Method: Azure Blob Storage.

    4. Enter the following cloud storage details:

      1. Prefix (Optional): A key prefix to scope file discovery within the container (e.g., "raw/pii/"). If omitted, the entire container is accessible.

      2. Delimiter (Optional): The character used to split the storage path into folder-like segments (default: /).

      3. Account Name: The Azure storage account name.

      4. Container Name: The container name within the storage account.

    5. Select the Authentication Method: Access Key for key-based authentication or Managed Identity for managed identity-based authentication. The credentials required depend on your selection:

      1. Access Key: Enter your storage account access key.

      2. Managed Identity: No credentials needed if the compliance node is running on an Azure VM with a managed identity that has access to the container.

  6. Click Next.

  7. In the Summary step, review the connector details.

  8. If you need to make changes, click Back to update the previous steps. Otherwise, click Submit.

Test your connection

(Optional) Before submitting the connector, click Test Connection to verify connectivity to your container.

Last updated
Oct 8, 2026