> ## Documentation Index
> Fetch the complete documentation index at: https://docs.merops.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Azure

> Create Azure Storage credentials and connect the provider in Merops

Merops connects to Azure Blob Storage using a storage connection string, a storage account name and key, or a Microsoft Entra service principal. The service principal format uses the account name, tenant ID, client ID, and client secret.

## Choose and prepare a credential

### Storage account connection string or key

1. In the Azure portal, open the Storage Account that contains the containers Merops should access.
2. Under **Security + networking**, open **Access keys**. You need permission to list the account keys.
3. Use **Show keys** to copy either the full connection string or the account key. The connection string includes the account name and key.
4. Create a local plain-text file such as `azure-credentials.txt` in one of these formats:

```text theme={null}
AZURE_STORAGE_CONNECTION_STRING=YOUR_CONNECTION_STRING
```

Or use the account name and key:

```text theme={null}
AZURE_STORAGE_ACCOUNT=YOUR_STORAGE_ACCOUNT
AZURE_STORAGE_KEY=YOUR_ACCOUNT_KEY
```

### Microsoft Entra service principal

If you use a service principal, register an application in Microsoft Entra ID and create a client secret. Assign it the **Storage Blob Data Contributor** role on the storage account (or a narrower supported scope) so it can manage blob data, including listing containers.

Create a local text file with the service principal values:

```text theme={null}
AZURE_STORAGE_ACCOUNT=YOUR_STORAGE_ACCOUNT
AZURE_TENANT_ID=YOUR_TENANT_ID
AZURE_CLIENT_ID=YOUR_CLIENT_ID
AZURE_CLIENT_SECRET=YOUR_CLIENT_SECRET
```

## Import the credentials in Merops

1. In Merops, open **Providers** and choose **Add provider**.
2. Select **Azure**, import the text file, and enter a display name if requested.
3. Open the new connection and check that its Blob Storage containers load.

Credential upload accepts a non-empty file up to 10 MiB. A successful import confirms that Merops parsed the file; it does not prove that the identity can perform every operation. Check [permissions guidance](/security-privacy/security/credentials-and-permissions.md).

For the current portal steps, see Microsoft's guides to [viewing storage account keys and connection strings](https://learn.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage), [registering an Entra application and creating a service principal](https://learn.microsoft.com/en-us/entra/identity-platform/howto-create-service-principal-portal), and [authorizing access to blob data with Entra ID](https://learn.microsoft.com/en-us/azure/storage/blobs/authorize-access-azure-active-directory).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.