Azure Blob Storage connector
The Azure Blob Storage connector imports files from a Microsoft Azure Storage account into Mammoth as datasets. Authentication uses Azure app credentials (Tenant ID, Client ID, Client Secret) tied to a storage account—not a per-user OAuth sign-in.
Before you start
You need an Azure Active Directory app registered with access to the target storage account. This is a one-time setup, typically done by an Azure admin.
Register the Azure AD app
- Go to Azure Portal → Azure Active Directory → App registrations
- Click New registration—name it (e.g.,
Mammoth Blob Storage) and click Register - Copy the Application (client) ID—this is your Client ID
- Copy the Directory (tenant) ID—this is your Tenant ID
- Go to Certificates & secrets → New client secret, add a description, set an expiry, and click Add
- Copy the secret Value immediately (it won't be shown again)—this is your Client Secret
- On your storage account, go to Access Control (IAM) → Add role assignment and grant the app the Storage Blob Data Reader role (or higher, if you also need export)
You'll also need the Storage account name you want Mammoth to read from.
Step 1: Select the Azure Blob Storage connector
- In Mammoth, go to Data Library and click + New Dataset
- Select Connectors
- Search for Azure Blob Storage or find it in the Cloud Storage category
- Click the Azure Blob Storage tile
Step 2: Create a connection
Click New Connection to open the credential form.
| Field | Description | Example |
|---|---|---|
| Storage Account Name | The Azure Storage account to connect to | mycompanystorage |
| Tenant ID | Azure AD Directory (tenant) ID | xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx |
| Client ID | Azure AD Application (client) ID | yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy |
| Client Secret | The app secret value you created | — |
All four fields are required. Click Connect once they're filled in—there's no OAuth sign-in step, since the connector authenticates directly with the app credentials above. If validation fails, the error message appears at the bottom of the form.
Step 3: Find and select your Azure Blob Storage file
After connecting, select the connection under Existing Connections. Mammoth shows the containers and blobs in the storage account as a file tree.
- Click a container to expand it and browse its contents
- Check the box next to a file to select it, or check a folder/prefix to include everything inside it
- You can select more than one file in a single connection
Supported Azure Blob Storage file types
.txt · .csv · .tsv · .psv · .xls · .xlsx · .xml · .zip · .bz2 · .gz · .tar · .7z
Step 4: Create the Azure Blob Storage dataset
Click Create new dataset. Mammoth does not ask you to choose an update method for this connector.
To keep the dataset in sync as the source file changes, set up a Dataset Refresh automation.
Troubleshoot Azure Blob Storage connections
Authentication fails
- Check all four values (Storage Account Name, Tenant ID, Client ID, Client Secret) are copied correctly
- Confirm the app's role assignment on the storage account has propagated (this can take a few minutes after granting access)
Client secret expired
- Client secrets expire based on the duration you set during creation—generate a new secret in Azure Portal and update the connection in Mammoth
No containers or files appear
- Confirm the app has at least the Storage Blob Data Reader role on the storage account, not just on a single container
- Confirm the file is one of the supported formats listed above