Skip to content

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

Updated on 2026-10-04

Dynamics 365 — connector

Reads accounts, contacts, opportunities and leads via the Dataverse (Dynamics 365) Web API and loads them into the Bronze layer.

On this page (15)

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


What it is#

Reads accounts, contacts, opportunities and leads via the Dataverse (Dynamics 365) Web API and loads them into the Bronze layer.

Supported ingestion modes:

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

What it's for#

Bring Dynamics 365 data 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, isolated by 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 in the plan).
  • Access: requires an active workspace — with overdue, suspended or cancelled subscription, runs are blocked.
  • Shutdown: ingestion runs can be temporarily disabled (maintenance or incident). When that happens, the UI indicates the feature is currently unavailable.

Prerequisites#

  • A Dynamics 365 account with access to the data you want to ingest.
  • In Microsoft Entra ID, register an application (Client ID + Client Secret) and, in the Power Platform admin center, add it as an application user for the environment with a read security profile. Provide the environment URL (https://org.crm.dynamics.com) and the tenant ID.

Credentials#

Authentication method: application credentials (client id/secret) exchanged for an access token.

Sensitive fields. They are encrypted (AES-256-GCM) and are never stored in the connection config, pipeline definition, export or DAG. By default the encrypted value is kept 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#

FieldLabelTypeRequiredNotes
urlAmbienteURL do ambientetextyesDataverse/Dynamics 365 environment address, without a trailing slash.
tenantIdID do tenant (Entra ID)textyes—
clientIdClient IDtextyesApplication credential generated in the Microsoft Entra ID portal.
clientSecret 🔒Client Secretpassword/secretyessecret (encrypted; external vault optional)

Step by step#

  1. In the Dados → Conexões menu, use Nova conexão.
  2. Choose Dynamics 365 in the catalog.
  3. Fill in the form fields (see the table above).
  4. Use Testar conexão. The result is shown broken down into Conectividade, Autenticação and Listagem/leitura — each with OK, Failed, Not applicable or Not tested. A capability with no test of its own for this connector shows as Not applicable, and Not applicable never counts as success.
  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 are fictitious; secrets appear masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
urlAmbiente = <urlAmbiente>
tenantId = <tenantId>
clientId = exemplo-client-id-ficticio
clientSecret = •••••• (cifrado — nunca exibido)

Expected result#

Testar conexão returns the list of discovered tables/resources. After the first load, rows 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); includes anti-loop protection.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~1 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; Bronze load consumes datalake processing (billable).

Security#

  • Workspace scope: each customer reads and writes only in 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 persisted. The external credential vault is optional and enabled per connection; without it, the encrypted value stays in the database. Changing the value here DOES NOT revoke the credential at the origin.
  • Redaction: every error/log is passed through secret redaction (raw, URL-encoded and in JSON).
  • No mocking in production: a path that would fall into a mock triggers production guard (explicit failure instead of simulating success).

Common errors#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or lacking required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop protection). If it happens in consecutive runs, open a support ticket specifying the connector and the resource.
  • Empty records path — the response arrived without records in the expected location. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network issues before scheduling.
  • Monitor runs in the 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 revision: 2026-10-04. Sheet automatically generated from the product connector catalog.

Related links