Read first:
../conectores.md(status map) andfichas.md(index of sheets).
What it is#
Reads CSV, JSON and XLSX files from a OneDrive folder or a SharePoint library (Microsoft Graph, application credentials) and loads them into the Bronze layer; Parquet is recognized and loaded directly.
Supported ingestion modes:
- Nós buscamos — We fetch the data from your source.
What it's for#
Bring data from OneDrive / SharePoint into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and 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.
Remember that the first run with a real credential is followed by our team before the connector is fully released.
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, the run is blocked.
- Downtime: ingestion runs can be temporarily disabled (maintenance or incident). When that happens, the UI indicates the feature is unavailable at the moment.
Prerequisites#
- A OneDrive / SharePoint account with access to the data you want to ingest.
- In Microsoft Entra, register an application with the application permission Files.Read.All (or Sites.Selected on the desired site) in Microsoft Graph, grant admin consent and generate a client secret. Provide the Tenant ID, the drive ID (document library) and the folder; the secret is encrypted and never shown again.
Credentials#
Authentication method: Application credentials (client id/secret) exchanged for an access token.
Sensitive fields. They are encrypted (AES-256-GCM) and never remain in the connection config, in the pipeline definition, in the export or in the DAG. By default the encrypted value is stored in the database; moving this connection's credential to the external credential vault is an explicit choice made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.
- Client Secret (
clientSecret)
Secrets are never re-displayed and are redacted in any error/log (raw token, URL-encoded and in JSON).
Form fields#
| Campo | Rótulo | Tipo | Obrigatório | Observação |
|---|---|---|---|---|
tenantId | Tenant ID | text | yes | Microsoft Entra directory (tenant). |
driveId | Drive ID | text | yes | SharePoint document library or OneDrive (GET /sites/{site}/drives in Graph Explorer). |
pasta | Folder | text | no | Path within the drive. Only the specified level is read; files are grouped by name. |
clientId | Client ID | text | yes | Application credential generated in the Microsoft Entra portal. |
clientSecret 🔒 | Client Secret | password/secret | yes | secret (encrypted; external vault optional) |
Step-by-step#
- In the menu Dados → Conexões, use Nova conexão.
- Choose OneDrive / SharePoint in the catalog.
- Fill in the form fields (see the table above).
- Use Testar conexão. The result is returned in three capabilities, each with OK, Failed, Not applicable or Not tested. In this sheet they mean: Network — the storage service endpoint is reachable from the application server; Authentication — the credential from 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 given prefix (the displayed count is of visible objects, not tables).
- Use Salvar conexão. Saving does NOT start any ingestion.
- 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.
- On review, Publicar (agenda desligada) creates version 1 without executing anything. Then, Ativar agenda and Executar agora are separate actions.
Example — connection test#
Example configuration (all values are fictitious; secrets appear masked):
# Exemplo sintético (valores fictícios — não são credenciais reais)
tenantId = <tenantId>
driveId = <driveId>
pasta = <pasta>
clientId = exemplo-client-id-ficticio
clientSecret = •••••• (cifrado — nunca exibido)Expected result#
The Testar conexão returns the number of visible objects under the specified prefix. After the first load, the content of those files appears 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.
- SaaS load: default
batchSize5,000,maxRows200,000 per resource. - Estimated volume: ~1 GB/month (catalog estimate, not measured).
- Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).
Security#
- Workspace scope: each customer reads and writes only to their own datalake (
<prefix>_bronze/_silver/_gold); there is never leakage between workspaces. - Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credential vault is optional and enabled per connection; without it, the encrypted value is kept in the database. Changing the value here DOES NOT revoke the credential at the source.
- Redaction: all errors/logs pass through secret redaction (raw, URL-encoded and in JSON).
- No production mocking: a path that would fall into mock triggers production guard (explicit failure instead of simulated success).
Common errors#
- Authentication failed — this connector credential is NOT a user/password: it is an access key (or service account). Check the pair entered in the form and whether it is still active in the provider.
- Listing denied — the credential authenticates but cannot list the bucket. Grant bucket listing and read of objects under the prefix; read permission without listing is not enough because the pipeline needs to discover which files exist.
- Bucket/prefix nonexistent 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 on load, depending on pipeline policy.
Troubleshooting#
- Use Testar conexão to isolate credential/network problems before scheduling.
- Monitor 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 change = attention).
Related#
../conectores.md— connectors catalog by status../ingestao-incremental-backfill.md— full, incremental by watermark, backfill and checkpoint../pipeline-medalhao.md— Bronze/Silver/Gold layers and quality../agendamento-retry-dlq.md— scheduling, retry/backoff and DLQ../custo-limites-seguranca.md— cost, limits and security per workspace
Last reviewed: 2026-10-04. Sheet automatically generated from the product's connectors catalog.