Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

Azure Blob Storage — connector

Reads files (CSV/JSON/XLSX) from an Azure Blob Storage container and loads them into the Bronze layer. Parquet is recognized and loaded directly into Bronze/warehouse.

On this page (15)

Read first: ../conectores.md (state map) and fichas.md (index of cards).


What it is#

Reads files (CSV/JSON/XLSX) from a container of Azure Blob Storage and loads them into the Bronze layer. Parquet is recognized and loaded directly into Bronze/warehouse.

Supported ingestion modes:

  • Nós buscamos — We pull the data from your source.

Purpose#

Bring data from Azure Blob Storage into your datalake and make it available to the Bronze/Silver/Gold layers, to BI models and to the natural language question wizard.

When to use / when not to use#

Use when you need to consolidate this source into the datalake on a scheduled basis, with isolation per workspace.

Avoid sending files with an unstable schema without first checking profiling and schema drift.

Plan and permissions#

  • Plan: core product (connectors are part of all plans; the limit is the number of sources allowed by the plan).
  • Access: requires an active workspace — if the subscription is overdue, suspended or cancelled, runs are blocked.
  • Disablement: ingestion runs can be temporarily turned off (maintenance or incident). When this happens, the screen informs that the resource is currently unavailable.

Prerequisites#

  • The source bucket/container, and the prefix (folder) from which objects will be read.
  • A credential with permission to list the bucket and read the objects under that prefix — nothing more. It is not necessary (nor desirable) to grant write, delete or admin permissions on the bucket.
  • The files under the prefix must be in a format the pipeline can read (CSV, JSON or Parquet). Object storage is transport, not format: the schema comes from the file.

Credentials#

Sensitive fields. They are encrypted (AES-256-GCM) and never stored in the config of the connection, in the pipeline definition, in exports or in the DAG. By default the encrypted value is kept in the database; moving this connection's credential to an external secrets vault is an explicit choice made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • SAS token (or SAS URL) (sasToken) — Paste the SAS token (starting at sv=) or the full SAS URL. It is encrypted (AES-256-GCM) and never shown again.
  • Client secret (clientSecret) — Secret of the app registration with the Storage Blob Data Reader role. Encrypted and never shown again.

Secrets are never re-displayed and are redacted in every error/log (raw token, URL-encoded and in JSON).

Form fields#

FieldLabelTypeRequiredNotes
accountStorage accounttextyesName of the storage account (the address is minhaconta.blob.core.windows.net).
containerContainertextyes—
prefixPrefix / foldertextno—
authModeAuthenticationselectnodefault: sas; options: sas / oauth; SAS is the simplest path: generate a read + list SAS URL/token (sp=rl) on the container.
sasToken 🔒SAS token (or SAS URL)password/secretnosecret (encrypted; external vault optional); appears when authMode = sas; Paste the SAS token (starting at sv=) or the full SAS URL. It is encrypted (AES-256-GCM) and never shown again.
tenantIdDirectory (tenant) IDtextnoappears when authMode = oauth
clientIdApplication (client) IDtextnoappears when authMode = oauth
clientSecret 🔒Client secretpassword/secretnosecret (encrypted; external vault optional); appears when authMode = oauth; Secret of the app registration with the Storage Blob Data Reader role. Encrypted and never shown again.

Step-by-step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Azure Blob Storage from the catalog.
  3. Fill in the form fields (see the table above).
  4. Use Testar conexão. The result is returned separately in three capabilities, each with OK, Failed, Not applicable or Not tested. In this card they mean: Network — the storage service endpoint is reachable from the application server; Authentication — the credential in the form (access key or service account, not user/password) was accepted; Reading — it was possible to list the objects of the bucket/container under the provided prefix (the displayed count is of visible objects, not tables).
  5. Use Salvar conexão. Saving does NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In the review, Publicar (agenda desligada) creates version 1 without running anything. Afterwards, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Example configuration (all values fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
account = minhacontaexemplo
container = meu-container-exemplo
prefix = dados/2026/
authMode = sas

Expected result#

Testar conexão returns the number of visible objects under the provided prefix. After the first load, the contents of those files appear in the Bronze layer of your workspace, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • Estimated volume: ~3 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Scoped per workspace: each customer reads and writes only to their own datalake (<prefixo>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credentials vault is optional and attached per connection; without it the encrypted value remains in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: every error/log goes through secret redaction (raw, URL-encoded and in JSON).
  • Production does not mock: a path that would hit a mock triggers the production guard (explicit failure instead of simulating success).

Common errors#

  • Authentication failed — the credential for this connector is NOT username/password: it is an access key (or service account). Check the pair entered in the form and whether it is still active at the provider.
  • Listing denied — the credential authenticates but cannot list the bucket. Grant bucket listing and object read under the prefix; read permission without listing is not enough because the pipeline needs to discover which files exist.
  • Bucket/prefix not found or empty — check the exact bucket name and the prefix (folder). A prefix with no objects returns zero visible objects, not an error.
  • File in unsupported format — object storage transports files; the pipeline needs to be able to read the content (CSV, JSON or Parquet). An object in another format is ignored or fails the load, depending on the pipeline policy.

Troubleshooting#

  • Use Testar conexão to isolate credential/network problems before scheduling.
  • Track runs in connector observability (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed column/type changed = attention).

Related#


Last review: 2026-10-04. Card automatically generated from the product connector catalog.

Related links