# Azure Blob Notifier

- Published on Sep 24, 2025
- 1 minute(s) read

The Azure Blob Notifier output connection will send submission data and state-change notifications to the Azure Blob Storage URI you specify.

If you would like to use the Azure Blob Notifier connection in a SaaS instance and your service is not public, you should create a firewall pinhole for the connection. Contact your Hyperscience representative for more information.

## Sample use cases

- Send extracted information and submission metadata to an Azure Blob Storage container for downstream processing.
- Configure monitoring of the output container and alert other systems to take action on submissions, if needed.

## Block settings table

In addition to the settings outlined below, you can also configure the settings described in [Universal Integration Block Settings](https://help.hyperscience.ai/v42/docs/universal-integration-block-settings).

| **Name** | **Required?** | **Description** |
| -------- | -------------- | ---------------- |
| **Azure Blob Storage URI** | Yes | The URI of the location where the data should be stored.<br>Example formats:<br>- _https://<account_name>.blob.core.windows.net/<container_name>/<prefix>/_<br>- _https://<account_name>.blob.core.windows.net/<container_name>_ |
| **Authentication Type** | Yes | Can be one of the following: <br>- **Service Principal**<br>- **Storage Account Key**<br>**Service Principal** should be selected if you want to use M2M Azure Entra ID authentication. It is an Application Service Principle type.<br>**Storage Account Key** requires an account name and access key. |
| **Client ID** | Yes, if **Service Principal** is selected for **Authentication Type** | Azure Entra ID Application Service Principal Client ID.<br>This setting is only available if **Service Principal** is selected for **Authentication Type**. |
| **Client Secret** | Yes, if **Service Principal** is selected for **Authentication Type** | Azure Entra ID Application Service Principal Client Secret. <br>To edit the secret, click **Edit value**, modify the secret, and then click **Done**.<br>This setting is only available if **Service Principal** is selected for **Authentication Type**. |
| **Tenant ID** | Yes, if **Service Principal** is selected for **Authentication Type** | Azure Entra ID Application Service Principal Tenant ID.​​ <br>Unique identifier of the Tenant in which the corresponding application is registered with.<br>This setting is only available if **Service Principal** is selected for **Authentication Type**. |
| **Storage Account Name** | Yes, if **Storage Account Key** is selected for **Authentication Type** | Azure Storage Account name.<br>This setting is only available if **Storage Account Key** is selected for **Authentication Type**. |
| **Storage Account Key** | Yes, if **Storage Account Key** is selected for **Authentication Type** | Azure Storage Account key. <br>To edit the key, click **Edit value**, modify the key, and then click **Done**.<br>This setting is only available if **Storage Account Key** is selected for **Authentication Type**. |

## Setting up the Azure Blob Notifier

To set up the Azure Blob Notifier, enter the settings as described in the [Block settings table](https://help.hyperscience.ai/v42/docs/azure-blob-notifier#block-settings-table) above.

Before deploying a flow with the Azure Blob Notifier enabled, ensure that the credentials you’ve specified in the block settings have the _write_ permission for the specified container.