FAQs

Common questions about data access, permissions, and revocation for a Serverless e6data deployment on Azure.

Why does e6data need access to my Azure storage? To read and analyze the data in your ADLS Gen2 account. e6data requires only the Storage Blob Data Reader role - it cannot modify or delete your data.

Can e6data modify or delete my data? No. The role grants read-only access. Access is also keyless - it uses Workload Identity federation, so no credentials are stored.

Can I limit access to specific containers or paths? Yes. Azure RBAC lets you scope the role assignment at the storage-account, container, or blob-path level.

How do I revoke access? Remove the Storage Blob Data Reader role assignment from the Managed Identity - in the Portal (Storage Account → IAM → Remove) or with the CLI:

az role assignment delete --role "Storage Blob Data Reader" --assignee <CLIENT_ID> --scope <STORAGE_SCOPE>

See also