Import files from Azure Blob Storage into Mammoth
The Azure Blob Storage connector imports files from a Microsoft Azure Storage account into Mammoth as datasets. It signs in with Azure app credentials (Tenant ID, Client ID, Client Secret) tied to a storage account, not a per-user sign-in. Open it from Data Library > New dataset > Connectors and search for Azure Blob Storage. Project Admins create the connection; Project Editors can start datasets from a connection the project already has. Which connectors you can add depends on your plan.
What you can bring in from Azure Blob Storage
Files in the storage account's containers, of these types: .txt, .csv, .tsv, .psv, .xls, .xlsx, .xlsm, .xml, .json, .jsonl, .ndjson, .zip, .bz2, .gz, .tar, .7z.
Unlike most file sources, an Azure Blob Storage dataset can be refreshed afterwards. For Parquet files in Azure Data Lake Storage, use the Parquet (Azure) connector.
Before you connect Azure Blob Storage
You need an Azure Active Directory app with access to the storage account. An Azure admin usually does this once. You also need the Storage account name Mammoth should read from.
Register the Azure AD app for Blob Storage
- Go to Azure Portal → Azure Active Directory → App registrations.
- Click New registration, name it (for example
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 at once; 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).
Connect Azure Blob Storage to Mammoth
- Go to the Data Library, click New dataset, and choose Connectors.
- Search for Azure Blob Storage and click its tile. The connector workspace opens with the Chat connecting Azure Blob Storage.
- Fill in all four fields below in the chat's card and connect. There's no sign-in step, because the connector uses the app credentials.
If you already have an Azure Blob Storage connection, pick it under Your connections in the launcher instead. See Connect a database or app for the shared steps.
| Field | What to enter | 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 |
Open a file from an Azure container
- In the left panel, open a container and browse to the file you want. A spreadsheet opens to its tabs.
- Tick the columns you want. They gather in Your table.
- If a file can't open in the panel yet, ask the agent in the Chat to import it.
Save an Azure Blob Storage file as a dataset
- Click Save as dataset.
- Enter a Dataset name and pick the folder under Save in.
- Click Save.
Refresh an Azure Blob Storage dataset
The workspace saves a file once and shows Saved once. Scheduled refresh for files is coming. Unlike most file sources, you can afterwards add an Azure Blob Storage dataset to a Dataset Refresh automation. It re-reads the file manually or on a schedule.
Troubleshoot Azure Blob Storage connections
| Symptom | Likely cause | Fix |
|---|---|---|
| Authentication fails | A value is copied wrong | Check Storage Account Name, Tenant ID, Client ID and Client Secret |
| Authentication fails right after setup | The role assignment hasn't spread yet | Wait a few minutes after granting access, then try again |
| Authentication stops working later | The client secret expired | Generate a new secret in Azure Portal, then update the connection in Data → Connections with Edit connection |
| No containers or files appear | The role is on one container only, or the file type isn't supported | Give the app at least Storage Blob Data Reader on the storage account, and check the file types above |
Related
- Parquet (Azure): import Parquet files from Azure Data Lake Storage.
- Connect a database or app: the shared connector workspace steps.
- Refresh a dataset: re-read the file on a schedule.
- Manage saved connections: update the connection when a secret expires.
- Connector reference: every source Mammoth connects to.
Something wrong? support@mammoth.io