Azure Blob Storage

azure blob storage is microsoft’s object storage solution for the cloud users can create data lakes with azure blob storage to support their analytics needs, and it also offers storage so you can design robust mobile and cloud native applications pre requisites access to your azure portal services ability to create a blob storage ability to update your azure network firewall ability to test with private or public secured containers setup instructions datalakehouse io securely connects to your azure blob storage using the form in the datalakehouse io portal please complete the following basic steps enter a name or alias for this connection, in the 'name/alias' field, that is unique from other connectors enter a target schema prefix , a name which will be the prefix for the schema at the target destination to where your data will sync enter in the connection string (sas) url field the shared access signature (sas) url connection string you retrieved from the azure pre requisite steps based in the azure storage account where your files are stored the url typically starts with the storage account and other information related to the container, for example https //\<your storage account> blob core windows net/\<container name>?sp= enter any other optional details in the available fields (see the setup video if you need help or contact support) folder path, is a path on the root bucket from where desired files will be retrieved file pattern, is a regular expression (regex) used to isolated only certain files to be retrieved file type, allows for a pre determined type of file extension to be retreived click the save & test button once your credentials are accepted you should be able to see a successful connection public vs private containers dlh io works with both private and public security on the containers if for some reason during testing you have an issue connecting to a private configured container, please test with a public access configured container this will ensure that you have confirmed that security is not a problem or if there is some other issue with how you have configured your access credential or container when provided it for your dlh io blob storage connector setup if there any questions please contact customer support docid\ pbtuxndqrdogoroejbgsv sas token security permission levels your azure blob storage access policy and your permissions shouls be set for the least permissive access however, dlh io requires the following permissions on the container when creating the sas token(s), in order to validate (test) a connection each time read, list and, when used as a target destination connection it requires the permissions read, add, create, write, delete, list, and move if you are unclear on how to create a shared access token, or what it is, please review the microsoft blob storage container documentation on sas token creation