Skip to main content

Export Results to Azure Blob Storage

You can set up an export of analytics and list results to Azure Blob Storage from Hybrid, Confidential Computing, and LinkedIn clean rooms.

Note

  • Partners invited to a clean room must have their export destination connections (grouped under "Destinations") approved by clean room owners. Contact your Customer Success representative to facilitate the approval.

  • For Azure exports originating from Confidential Computing clean rooms, notify your LiveRamp contact as LiveRamp needs to add your Azure Blob Storage to the firewall allowlist. If you joined the project mid-configuration and are unsure if your clean room is Confidential Computing and needs this step, contact your LiveRamp Clean Room account team.

  • Configuring exports outside of a clean room (i.e., at the organization level) is still supported, but will be deprecated. Setting up clean room question exports within a clean room is recommended.

Overall Steps

Perform the following overall steps in Microsoft Azure to set up an export of analytics and list results to Azure Blob Storage:

  1. Configure access for the Service Principal

Once the above steps have been performed in Microsoft Azure, perform the overall steps in the sections below in LiveRamp Clean Room.

  1. Enable the clean room for exports

  2. Add your Azure AD Service Principal credential to your Clean Room Organization

  3. Add an Azure Export destination connection 

  4. Set up a data export within the clean room

  5. Create a new export

For information on performing these steps and for export details, see the sections below.

Configure Access for the Service Principal

The AD Service Principal needs to have read, write, and delete access to the target Azure Blob Storage location.

Note

For information on creating Azure AD Service Principals, see Microsoft's Learn site.

To configure access for the Service Principal, perform the following steps in the Microsoft Azure UI:

  1. Create Microsoft Extra ID App.

    LCR-Export_Results_to_Azure_Blob_Storage_-Configure_Access_step_1.png

  2. Generate a secret for the created app.

    LCR-Export_Results_to_Azure_Blob_Storage_-Configure_Access_step_2.png

  3. Add required roles to the Extra ID app:

    1. Navigate to the storage account which will be used for exports and select Access Control (IAM).

      LCR-Export_Results_to_Azure_Blob_Storage_-Configure_Access_step_3a.png

    2. Create a Role assignment and add the role "Storage Blob Data Contributor" to it.

      LCR-Export_Results_to_Azure_Blob_Storage_-Configure_Access_step_3b.png

  4. During role assignment, in the members section add the Microsoft Extra ID app created earlier.

    LCR-Export_Results_to_Azure_Blob_Storage_-Configure_Access_step_4.png

Use the Tenant ID, Client ID, and Client Secret during the procedure in the "Add the Credentials" section below .

Perform Steps in LiveRamp Clean Room

Once the above steps have been performed in Microsoft Azure, perform the overall steps in the sections below in LiveRamp Clean Room.

Enable the Clean Room for Exports

Before setting up an export, the clean room owner must enable export for the selected source clean room:

  1. From the LiveRamp Clean Room navigation pane, select Clean Rooms → Clean Rooms (or click Go to Clean Rooms from the Clean Rooms tile).

  2. In the row for the clean room you would like to export from, click the More Options menu (the three dots), and then select Edit.

    CR-Export_to_GCS-edit_button.png

  3. From the Configuration step, click Next Step.

    LCR-Export_Analytical_Results_to_BigQuery-Next_Step_button.png

  4. From the Parameters step, adjust any data control parameters as needed and then slide the Enable Export toggle to the right.

    CR-Export_to_GCS-edit_clean_room_screen.png

  5. Click Next Step.

  6. Verify that your data control parameters are correct and then click Save.

    CR-Export_to_GCS-edit_clean_room_screen_2.png

Add the Credentials

To set up an export to a cloud location, you must configure your Azure AD Service Principal credentials for your Organization:

  1. From the LiveRamp Clean Room navigation pane, select Data Management → Credentials.

  2. Click Add Credential.

    add_credential.png

  3. Enter a descriptive name for the credential.

  4. For the Credentials Type, select Azure AD Service Principal.

  5. Enter the following information for your AD Service Principal:

    LCR-Export_Results_to_Azure_Blob_Storage_-Credential_Parameters.png

    • Tenant ID

    • Client ID

    • Client Secret

  6. Click Save Credential.

  7. Verify that your credentials have been added to LiveRamp Clean Room:

Add an Export Destination Connection

To add an export destination connection:

  1. From the LiveRamp Clean Room navigation pane, select Destinations & Integrations → Destinations.

  2. Click Create Destination Account.

    CR-Export_to_GCS-_create_partner_account_button.png

  3. Select Azure Export.

    LCR-Export_Results_to_Azure_Blob_Storage_-Azure_Export_tile.png

  4. Enter a name and select the Azure AD Service Principal credential created in the "Add the Credentials" section above.

    LCR-Export_Results_to_Azure_Blob_Storage_-select_credentials.png

  5. Click Add new account.

  6. Confirm that the new destination connection has been added to your list of Azure Export destination connections.

    LCR-Export_Results_to_Azure_Blob_Storage_-new_destinatinon_connection.png

Note

The status of the destination connection will be "Pending" initially, but you can continue to export data. Once the first successful export has been processed the status changes to "Complete".

Set Up a Data Export Within the Clean Room

To set up a data export within the clean room:

  1. From the LiveRamp Clean Room navigation pane, select Clean Rooms → Clean Rooms.

  2. From the tile for the desired clean room, click Enter.

  3. From the Clean Room navigation pane, select Destinations. The Destinations screen shows all destination connections provisioned to the clean room.

  4. Check the check box for the desired destination connection and then click Provision (AWS S3 example shown).

    CR-Export_to_AWS-_provision_Activation_Channels.png

  5. Verify that your destination connection has been added (S3 IAM example shown).

    CR-Export_to_AWS-_verify_Activation_Channels.png

Create a New Export

To create a new export:

  1. From the LiveRamp Clean Room navigation pane, select Clean Rooms → Clean Rooms.

  2. From the tile for the desired clean room, click Enter.

  3. From the Clean Room navigation pane, select Exports.

  4. Click + New to open the wizard to create a new export.

    CR-Export_to_GCS-__Exports_page.png

  5. Select the question that you want to export outputs for and then click Next.

    Note

    Unless paused, all run outputs will be exported to the configured export destination connection.

    CR-Export_to_GCS-_choose_clean_room_question.png

  6. Check the radio button for the specific Azure destination connection you want to send run outputs to.

    LCR-Export_Results_to_Azure_Blob_Storage_-Select_Azure_Export.png

  7. Enter the following information on where you would like the outputs to be exported to and then click Finish.

    LCR-Export_Results_to_Azure_Blob_Storage_-Required_Parameters.png

    • Storage Account

    • Storage Container

    • Azure Export Path

    Note

    In the Azure Export Path field, “/” values are appended before and after the value entered into this field. That is, you do not have to add “/” before or after your folder path.

    The values shown in the screenshot above result in a final file path structured as "abfss://storage-container@storage-account.dfs.core.windows.net/azure-export-path/*".

  8. Verify that the job has been created. Exports are added to the page. You may view the details of an export by clicking on the name.

    LCR-Export_Results_to_Azure_Blob_Storage_-Verify_job_creation_1.png
    LCR-Export_Results_to_Azure_Blob_Storage_-Verify_job_creation_2.png

Note

  • Exports can be paused, which will stop them from sending data upon the completion of each run.

  • Exports cannot be edited or deleted. Changes should be made by pausing the export and creating a new export.

Export Details

When a question runs, the results will be written to the defined bucket. Each row will have an associated "Run ID" column. There will be a second metadata table created. Users can join on Run ID to get run metadata (Run Name, Runtime Parameters, etc.).

Azure Export File Structure

  • abfss://<container>@<account>.dfs.core.windows.net/<export-path>/

    • /date=<yyyy-mm-dd>

      • /cleanroom=<clean-room-id>

        • /question=<clean-room-question-id>

          • /run=<run-id>

            • /data ← For analytical questions, this contains 1 .csv file. For user list questions, this contains 1+ .parquet files with list data.

              Note

              List files do not contain column headers

            • metadata.json ← This contains each column header name, data type, and whether it is encrypted. If encryption is used, the dek and kek are also provided.

In this section: