# ABS - Azure Blob Storage

The ABS data source in SCA provides access to contacts exported from any application (including on-premises) via **CSV or JSON files** using the **SCA Blob Storage connector (ABScon)**. Contacts are queried via the **Azure Blob Storage API** and remain **managed in the source system**.

The **ABS connector (ABScon)** is a command-line tool that reads, encrypts, and transfers contact data to an Azure Blob Storage container in your tenant, which can then be read and decrypted by SCA.

#### App Configuration Parameters

**Defaults (**[**`SecContacts.Defaults`**](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults)**):**

* [**ABS\_Enabled**](https://docs.secure-contacts.com/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults#enable-or-disable-features) → Enables or disables the ABS data source.
* [**ABS\_InitValue**](https://docs.secure-contacts.com/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.defaults#initial-value-set-by-default) → Defines the default state of the user’s switch in the app (on/off). This controls whether the data source is visible or hidden when the user first launches SCA.

**Azure Blob Storage (**[**`SecContacts.AzureBlobStorage`**](https://docs.secure-contacts.com/app-configuration-policy-name-values-for-sca/sca-configuration-connect-additional-datasource#seccontacts.azureblobstorage)**):**

* [**SecContacts.AzureBlobStorage**](https://docs.secure-contacts.com/app-configuration-policy-name-values-for-sca/sca-configuration-connect-additional-datasource#seccontacts.azureblobstorage) → Configure the connection to your Azure Blob Storage container.
* Administrators can also:
  * Split contacts into multiple separate SCA data sources using multiple CSV/JSON files in the same container (e.g., by business unit, department, or origin system)

**Additional Steps:**

* Download and install the **ABS connector (ABScon)** (contact us for details).
* Set up ABScon by following the provided **howto.txt** instructions.
* Ensure the tenant has a **license with Azure Active Directory Premium P1 (or higher)** to use Azure Blob Storage with SCA.

**Customization:**

* [**SecContacts.CustomDatasourceNames**](https://docs.secure-contacts.com/documentation/app-configuration-policy-name-values-for-sca/sca-configuration-seccontacts.customdatasourcenames) → Assign friendly display names for the ABS source.

#### Requirements to Access ABS Contacts

To access ABS contacts in SCA, a user must have:

* **Azure Active Directory Premium P1 (or higher)** license
* **Authorized access to the Azure Blob Storage container**

#### Requirements for ABS Contacts

Any **ABS contact** to be shown in SCA must have the following fields populated:

1. **First name**
2. **Last name**
3. **Valid phone number**

**Note:** All eligible ABS contacts that meet these requirements will appear in SCA

{% hint style="success" %}

* Each data source, including ABS, can be **hidden by the user** if they do not want to see or use it.
* Hiding the ABS data source does **not affect Caller Identification** — contacts from hidden sources will still resolve incoming calls.
* The ABS data source is only available with the **Enterprise Edition** of SCA.
  {% endhint %}