Azure Blob Storage data point is used to configure connectivity to Azure Blob Storage. For each instance of Azure Blob Storage, a separate data point will have to be created. Any container within the bucket can be accessed using the Data point as long as the user has necessary privileges. The Azure Blob Storage data point can be associated to any file object created like, delimited, fixed width, xml, json, etc.

To work with Azure Blob Storage Data Point, follow below steps:

Step I: Create a New Data Point

Step II: Provide connection details

1. To connect to Azure Blob Storage database, following details need to be provided in the Properties tab.

  • Storage Account Name: Azure Storage has an address that includes our unique account name which is a combination of the account name and the Azure Storage blob endpoint forms the base address for the objects in your storage account.

  • Authentication Method: This supports two types of authentication methods,
    1. Azure account key: Choose to authenticate based on access keys and other parameters to produce an encrypted signature string that is passed on the request in the Authorization header.
    2. Shared access signatures (SAS): Choose to grant fine-grained access to resources in your storage account with specified permissions and over a specified time interval.
  • Key: The 512-bit access key generated while creating storage account. To use the project parameter for the Key, check the Use Project Parameters option, and you can view and select the required Project Parameter from the Key drop-down.
  • Container: Give container details that organizes a set of blobs, like a directory in a file system.


  • Mandatory field names are suffixed with *. To establish the connection, provide all the mandatory property field values.
  • All the fields in the Properties tab can be parameterized using project parameters. To parameterize the fields, refer Working with Project Parameters.

2. Assign Agent: To assign or change the associated agent click Change. The Change Agent window appears and displays the list of available Agents. From the list, select the required Agent Name.

Note: To search for a specific agent, enter the keyword in the search bar, and the window displays the search result list. Select the required agent and click Ok.
  • If Default agent is assigned to the Project then automatically, the Default agent will be associated with the new Data point created.
  • If Default agent is not assigned to the Project then, no agent will be assigned automatically and appropriate agent needs to be assigned to the data point.
  • When connecting to the Agent server then, the agent installation user should have appropriate privilege to access the path where file will be placed.
  • When connecting to the remote server then, the firewall needs to be opened from the Agent server to it and user specified to connect should have appropriate privilege to access the path where file will be placed.

Step III: Test the data point connection

  • To validate that the data point is able to connect to the Azure Blob Storage data point database using the details provided, refer Test Data Point Connection. 

Step IV: Save the data point 


Step VI: Modify the configured Load properties

When moving data from one system to another the data is extracted from the source system, moved over the network and loaded into the target system. The SQLs and commands generated during execution of the jobs to extract and load data are generated based on the properties defined for these. The properties associated with the extraction and load of data should depend on the format, performance and variety of the data being moved. These properties vary based on the environment and the type of the system. Diyotta comes with default properties that covers most of the known scenarios.

To modify these properties, refer Editing Extract Properties in Azure Blob Storage Data Point and Editing Load Properties in Azure Blob Storage Data Point.

  • The default values for extract and load properties can be configured in the Admin module and these properties reflect in the Studio module.
  • The extract and load properties set in data point are by default used in the source and target instance of the data flow and the job flows.
  • It is a good practice to set the extract and load properties as per the company standards in the data point.
  • However, if needed any specific property can be overridden in the data flow or job flow.