Using Azure Storage with Import Definitions

Import definitions include the capability to source files from multiple storage providers. This includes Local storage, AWS, or Azure. 

If your client or service is configured to utilize Azure storage, the option will be available when creating an import definition. 

Connection String

The storage connection string must be the Primary Connection String of the storage account with an included SAS Token. This can be generated in one of two ways.

Microsoft Azure Storage Explorer: 

1. Find the correct storage account in the list of available storage accounts. You must be signed in to a valid account that has access to the storage account in question.
2. Right click the storage account and select Get Shared Access Signature. Set expiry time, all required permissions and services. You may even whitelist specific IP addresses if required. NOTE: You must allow the Create permission as LemonEdge will create a container / base-path, if one does not exist.
   
3. Copy the connection string and paste this into the Storage Connection String field of the import definition.
   

Azure Resource Portal

1. Search for Storage Accounts and navigate to the resource
   
2. Find the correct storage account and click on the link
   
3. Click on Shared Access Signature from the left-hand menu
   
4. Set all parameters as listed in the previous steps and click Generate SAS and connection string
   
   
5. Copy the connection string and paste this into the Storage Connection String field of the import definition.
   

Storage Base Path

The storage base path is simply the container name where we have stored our file. If the container has not been created and we included the create permission as part of our SAS Token, LemonEdge will automatically create the container for us. However, if one already exists, we simply need to pass in the container name (case-sensitive) to the storage base path field.

Import Definition Step

The import definition step will be set up as usual, however we will ensure that the Import Storage Relative File points to the correct location in our blob container. For instance, if our file is named Currencies.csv and is stored in our blob container, in a directory named Currencies - our relative file path would be Currencies/Currencies.csv.