Configure OneLake Identity for Cloud subvolumes

This article describes an alternate configuration for OneLake lakehouses to be used for a subvolume configuration. This applies to either Cloud Ingest subvolumes or Cloud Mirror subvolumes.

Configure OneLake for Extension Identity

Add Extension Identity to OneLake workspace

1. Navigate to your OneLake portal; for example, https://youraccount.powerbi.com.
2. Create or navigate to your workspace.
3. Select Manage Access.
4. Select Add people or groups.
5. Enter your extension name from your Azure Container Storage enabled by Azure Arc installation. The extension is called microsoft.arc.containerstorage in the Azure portal. This name must be unique within your tenant.
6. Change the drop-down for permissions from Viewer to Contributor.
7. Select Add.

Attach subvolume to Edge Volume

When creating a subvolume for Cloud Ingest or Cloud Mirror, during the CRD creation process, there are two parameters that need to be set specifically for OneLake:

• spec.storageaccountendpoint in ingestSubvolume.yaml or spec.blobAccount.accountendpoint in mirrorSubvolume.yaml:

  Your storage account endpoint is the prefix of your Power BI web link. For example, if your OneLake page is https://contoso-motors.powerbi.com/, then your endpoint is "https://contoso-motors.dfs.fabric.microsoft.com".

• spec.containerName in ingestSubvolume.yaml or spec.blobAccount.containerName in mirrorSubvolume.yaml:

  Details of your OneLake lakehouse, for example, "<WORKSPACE>/<DATA_LAKE>.Datalake/Files".

Next Step

Continue the steps in either Attach Ingest subvolume to Edge Volume or Attach Mirror subvolume to the Edge Volume to complete the configuration.