Adeptia Connect enables you to use Azure Blob as an Application Source or Target in a Process Flow. You can also create an Event that uses Azure Blob, and bind that Event with the Process Flow. Refer to the following sections that guide you on how to use Azure Blob in a Process Flow.

In the event of Adeptia Connect users not willing to whitelist the connect.adeptia.com server to exchange data with Azure Blob, they need to follow the steps given on the page Supporting OAuth without whitelisting connect.adeptia.com.

Azure Blob as an application source

This section helps you creating Azure Blob as an Application Source that can be used in a Process Flow as an activity.

Follow the steps given below to create Azure Blob type of application source.

Click Configure > SOURCES > Application Source.
Click Create Application Source.
In the Name field, enter a name for the Azure Blob application source.
In the Description field, enter a description for the Azure Blob application source.
In the Application field, select Azure Blob as the type of application source.

In the Account field, select the Azure Blob account that you want to use as the source.
You can also create an Azure Blob account and use it as the source by clicking the icon, and then providing the following information on the Create New Account screen.

Field Name	Description
Provide a name for this account. e.g. "MyAccount"	A short, descriptive name that helps you re-use this account in future.
Access Type	This field governs the type of authentication you choose to connect to your Azure Blob. Note: You can select Azure AD, Shared Key, or Shared Access Signatures as the Access Type. Based on your selection, the next field will ask you for the required input (Id, Key, or Signature) to proceed. For example, if you select Azure AD as the Access Type, the next field in the form will be Tenant Id where you’d need to enter the Tenant Id of your Azure Blob account. You can also use HashiCorp Vault to fetch the Shared Key and Shared Access Signatures secrets. Before you use HashiCorp Vault, ensure that you have cleared the browser cache. If you ever change the secrets for this activity in HashiCorp Vault, ensure that you have cleared the cached secrets to bring the change into effect. Each secret is maintained as a key-value pair in Hashicorp Vault. Enter the variable in the following format in the field for which you want to fetch the secret from Vault: ${Vault:<Key1>} Where, <Key1> is the key in Hashicorp Vault that is defined for the field for which you want to fetch the secrets. For example, you need to enter ${Vault:SharedAccess.Signatures} in the Shared Access Signatures field, if you have defined SharedAccess.Signatures as the key for this field in the Vault. For more details refer to this page. You can also enter the values manually. You can select one of the following Access Types: Azure AD – This option facilitates OAuth based authentication and the user experience will be the same as the other OAuth apps. Once you select Azure AD as Access Type, you’ll require the Tenant Id to enter in the next field. To know how to get the Tenant Id refer to this page in the Microsoft Azure documentation. After clicking Continue, the user would need to enter the Azure credentials in a new window. Shared Key – Facilitates non-OAuth based authentication. To know how to get the Shared Key, refer to this page in the Microsoft Azure documentation. As you complete all the fields and click Continue, your account will be created and saved. You may want to test if you’d be able to connect this account with Azure Blob by clicking Test. Shared Access Signatures – Facilitates non-OAuth based authentication. To know how to get the Shared Access Signature, refer to this page in the Microsoft Azure documentation. As you complete all the fields and click Continue, your account will be created and saved. You may want to test if you’d be able to connect this account with Azure Blob by clicking Test.
Storage Account Name	Name of your storage account in Azure.
Container Name	Name of the container in the selected Storage Account.
Select Project	Name of your Project in which you want to create a Template/Transaction.

Once you have provided the information, click to use the account as a source.

In the Trigger field, select either of the following triggers based on your requirement.

Sl. no.	Trigger	Description
1	Get Blob	The Get Blob operation downloads a blob, including its metadata and properties.
2	Get Blob Snapshot	The Get Blob Snapshot operation returns a read-only snapshot of a blob.
3	Get Blob Metadata	The `Get Blob Metadata` operation returns all user-defined metadata for the specified blob or snapshot.
4	Get Blob Properties	The `Get Blob Properties` operation returns all user-defined metadata, standard HTTP properties, and system properties for the blob. It does not return the content of the blob.
5	Get Blob Tags	The `Get Blob Tags` operation returns all user-defined tags for the specified blob, version, or snapshot.

In the Folder field, specify the path of the folder where the source file/blob is located.
In the File Name field, enter the source file/blob name.
Expand Advanced Properties.
Select Delete File on Success check box, if you want to delete the downloaded source file after it is used in the process flow execution.
In the Select Project field, select the project.
Click Save.

Event for Azure Blob type of application source

The Application Event enables you to specify when and how frequently a Process Flow bound with it would be executed based on the polling frequency. It also overrides the parameters you have provided in the application source used in the Process Flow as an activity.

This section discusses the event for Azure Blob type of application source. Follow the steps given below to create the application event.

Click Configure > EVENTS > Application.
Click Create Application Event.
In the Name field, enter a name for the event.
In the Description field, enter a description for the event.
In the Application field, select Azure Blob as the type of application source.

In the Account field, select the Azure Blob account that you want to use as a source.
You can also create an Azure Blob account by clicking the icon, and then providing the following information on the Create New Account screen.

Field Name	Description
Provide a name for this account. e.g. "MyAccount"	A short, descriptive name that helps you re-use this account in future.
Access Type	This field governs the type of authentication you choose to connect to your Azure Blob. Note: You can select Azure AD, Shared Key, or Shared Access Signatures as the Access Type. Based on your selection, the next field will ask you for the required input (Id, Key, or Signature) to proceed. For example, if you select Azure AD as the Access Type, the next field in the form will be Tenant Id where you’d need to enter the Tenant Id of your Azure Blob account. You can also use HashiCorp Vault to fetch the Shared Key and Shared Access Signature secrets. Before you use HashiCorp Vault, ensure that you have cleared the browser cache. If you ever change the secrets for this activity in HashiCorp Vault, ensure that you have cleared the cached secrets to bring the change into effect. Each secret is maintained as a key-value pair in Hashicorp Vault. Enter the variable in the following format in the field for which you want to fetch the secret from Vault: ${Vault:<Key1>} Where, <Key1> is the key in Hashicorp Vault that is defined for the field for which you want to fetch the secrets. For example, you need to enter ${Vault:SharedAccess.Signatures} in the Shared Access Signatures field, if you have defined SharedAccess.Signatures as the key for this field in the Vault. For more details refer to this page. You can also enter the values manually. You can select one of the following Access Types: Azure AD – This option facilitates OAuth based authentication and the user experience will be the same as the other OAuth apps. Once you select Azure AD as Access Type, you’ll require the Tenant Id to enter in the next field. To know how to get the Tenant Id refer to this page in the Microsoft Azure documentation. After clicking Continue, the user would need to enter the Azure credentials in a new window. Shared Key – Facilitates non-OAuth based authentication. To know how to get the Shared Key, refer to this page in the Microsoft Azure documentation. As you complete all the fields and click Continue, your account will be created and saved. You may want to test if you’d be able to connect this account with Azure Blob by clicking Test. Shared Access Signatures – Facilitates non-OAuth based authentication. To know how to get the Shared Access Signature, refer to this page in the Microsoft Azure documentation. As you complete all the fields and click Continue, your account will be created and saved. You may want to test if you’d be able to connect this account with Azure Blob by clicking Test.
Storage Account Name	Name of your storage account in Azure.
Container Name	Name of the container in the selected Storage Account.
Select Project	Name of your Project in which you want to create a Template/Transaction.

Once you have provided the information, click to save the account.

In the Trigger field, select either of the following triggers based on your requirement.
Sl. no.
Trigger
Description
1
Get New Or Updated Blob
The New or Updated Blob operation downloads the newly created or updated blob.
2
Get All Blob
The Get All Blob operation downloads all blobs.
In the Folder field, specify the path of the folder where the source file/blob is located.
In the Search Criteria field, specify a file extension, in case you want to retrieve only the files/blobs matching this search criteria. For example, *.txt.
Select Run Initial Load check box, if you want to process all the files when the event gets triggered for the first time.
In the Polling Frequency field, provide the time interval at which the Process Flow bounded with it will get executed.
Expand Advanced properties.
In the Select Project field, select the project.
Click Save.

Sl. no.	Trigger	Description
1	Get New Or Updated Blob	The New or Updated Blob operation downloads the newly created or updated blob.
2	Get All Blob	The Get All Blob operation downloads all blobs.

Azure Blob as an application target

This section helps you creating Azure Blob as an Application Target that can be used in a Process Flow as an activity.

Follow the steps given below to create an Azure Blob type of application target.

Click Configure > TARGETS > Application Target.
Click Create Application Target.
In the Name field, enter a name for the Azure Blob application target.
In the Description field, enter a description for the Azure Blob application target.
In the Application field, select Azure Blob as the type of application target.

In the Account field, select the Azure Blob account that you want to use as the target.
You can also create an Azure Blob account and use it as the target by clicking the icon, and then providing the following information on the Create New Account screen.

Field Name	Description
Provide a name for this account. e.g. "MyAccount"	A short, descriptive name that helps you re-use this account in future.
Access Type	This field governs the type of authentication you choose to connect to your Azure Blob. Note: You can select Azure AD, Shared Key, or Shared Access Signatures as the Access Type. Based on your selection, the next field will ask you for the required input (Id, Key, or Signature) to proceed. For example, if you select Azure AD as the Access Type, the next field in the form will be Tenant Id where you’d need to enter the Tenant Id of your Azure Blob account. You can also use HashiCorp Vault to fetch the Shared Key and Shared Access Signatures secrets. Before you use HashiCorp Vault, ensure that you have cleared the browser cache. If you ever change the secrets for this activity in HashiCorp Vault, ensure that you have cleared the cached secrets to bring the change into effect. Each secret is maintained as a key-value pair in Hashicorp Vault. Enter the variable in the following format in the field for which you want to fetch the secret from Vault: ${Vault:<Key1>} Where, <Key1> is the key in Hashicorp Vault that is defined for the field for which you want to fetch the secrets. For example, you need to enter ${Vault:SharedAccess.Signatures} in the Shared Access Signatures field, if you have defined SharedAccess.Signatures as the key for this field in the Vault. For more details refer to this page. You can also enter the values manually. You can select one of the following Access Types: Azure AD – This option facilitates OAuth based authentication and the user experience will be the same as the other OAuth apps. Once you select Azure AD as Access Type, you’ll require the Tenant Id to enter in the next field. To know how to get the Tenant Id refer to this page in the Microsoft Azure documentation. After clicking Continue, the user would need to enter the Azure credentials in a new window. Shared Key – Facilitates non-OAuth based authentication. To know how to get the Shared Key, refer to this page in the Microsoft Azure documentation. As you complete all the fields and click Continue, your account will be created and saved. You may want to test if you’d be able to connect this account with Azure Blob by clicking Test. Shared Access Signatures – Facilitates non-OAuth based authentication. To know how to get the Shared Access Signature, refer to this page in the Microsoft Azure documentation. As you complete all the fields and click Continue, your account will be created and saved. You may want to test if you’d be able to connect this account with Azure Blob by clicking Test.
Storage Account Name	Name of your storage account in Azure.
Container Name	Name of the container in the selected Storage Account.
Select Project	Name of your Project in which you want to create a Template/Transaction.

Once you have provided the information, click to use the account as the target.

In the Action field, select either of the following actions based on your requirement.

Sl. no.	Action	Description
1	Create Block Blob	The `Create Block` operation creates a new Block blob.
2	Update Block Blob	The `Update Block` operation updates a new block to be committed as part of a blob.
3	Create Page Blob	The Create `Page Blob` operation creates a new Page blob.
4	Update Page Blob	The `Update Page Blob` operation writes a range of pages to an existing Page blob.
5	Put Append Blob	The `Put Append Blob` operation append a blob.
6	Set Blob Snapshot	The `Snapshot Blob` operation creates a read-only snapshot of a blob.
7	Delete Blob	The `Delete Blob` operation marks the specified blob or snapshot for deletion. The blob is later deleted during garbage collection.
8	Undelete Blob	The `Undelete Blob` operation restores the contents and metadata of a soft deleted blob and any associated soft deleted snapshots.
9	Set Blob Properties	The `Set Blob Properties` operation sets system properties on the blob.
10	Set Blob Metadata	The `Set Blob Metadata` operation sets user-defined metadata for the specified blob as one or more name-value pairs.
11	Set Blob Tags	The `Set Blob Tags` operation sets user-defined tags for the specified blob as one or more key-value pairs.

In the Folder field, specify the path of the target folder.
In the File Name field, enter the name of the target file as per your requirement.
In the Time Stamp field, select the format of date and time. The date and time gets appended to the target file name in the same format as selected by you in this field.
Expand Advanced Properties.
In the Select Project field, select the project.
Click Save.

Browser not supported