The exact Azure roles a user needs to edit Delta tables with Eddytor — and how to grant them.
To use this tool, users must have at least Reader or equivalent permissions for the storage accounts to view the resources. In addition, the app requires more granular access through the Storage Blob Data Owner or Storage Blob Data Contributor roles, as it interacts directly with the Azure Storage Blob API.
Having just the general Owner or Contributor role at the storage account level is not sufficient, because those roles do not cover the more specific blob-related permissions required for the app to function. Therefore, users need both Reader-level permissions on the storage account and Storage Blob Data Owner / Contributor roles to interact with blobs as intended.
This is the minimum access the user needs of the storage account. It is important that the user gets both the Reader (or better) role AND the Storage Blob Data Contributor (or Storage Blob Data Owner) role.
You can grant the user access by clicking the + Add icon in the top.
If you know your way around storage account ACL, you can grant the user even more container/folder-granular access. Test your settings when doing this — it's easy to get wrong if you're not familiar with ACL.
Read more here: Link to Microsoft documentation.
What Eddytor is, the problem it solves, and how it plugs into your Azure infrastructure.
GuideWhy spreadsheets and SharePoint lists break down for master data — and where Eddytor fits in.
TutorialA short walkthrough of Eddytor's core features — connecting, editing, bulk upload, creating tables, and constraints.
Can't find it? Ask support and a human will answer, usually within a few hours.