Integrations · SaaS applications · Coming next
Microsoft Dynamics 365: coming next connector
Dynamics 365 (Dataverse) connector: table discovery from Dataverse metadata (primary id as key, single-target lookups as relationships), Web API reads with a pinned version and @odata.nextLink paging.
Coming next SaaS applications
Active implementation; not yet available for production use.
Not available yet. Active implementation; not yet available for production use. The console does not offer it, and asking an agent for a connector it does not ship fails with the error code CONNECTOR_NOT_AVAILABLE; the product never fakes a connection.
What you can do today
Export Dynamics 365 tables to CSV or Parquet with your existing tooling inside your network and read them with the Local files or object-store connectors.
Whatever route you choose, the export and every row-level step stay inside your network. You can evaluate the whole workflow now with the synthetic demo.
Known limitations
- Exercised only against a local mock of the Dataverse Web API v9.2; not yet run against a real Dynamics 365 environment.
- The application user needs organization-wide Read on every configured table and Read on security roles, users and teams, so the agent can prove it read-only.
- Customer and Owner lookups (several target tables) are not turned into relationships; columns with several choices, images, files and column-security-protected columns are not read.
- Counts above 5,000 come from Dataverse's snapshot count (RetrieveTotalRecordCount).
Capability matrix
Microsoft Dynamics 365 does not ship yet, so no capability is verified. The column shows what the design plans; plans are not commitments.
| Capability | Design intent |
|---|---|
| Discovery | Planned |
| Classification | Planned |
| Profiling | Not planned yet |
| Masking | Planned |
| Deterministic masking | Planned |
| Entity-aware subsetting | Not planned yet |
| Relationship preservation | Planned |
| Synthetic workflows | Not planned yet |
| Certification | Planned |
| Provisioning | Not planned yet |
| CI/CD | Not planned yet |
| Evidence generation | Planned |
How the connector is designed to prove read-only access
Proven before reading from the application user's security roles (direct and through teams) and privileges: no System Administrator or System Customizer role and no privilege other than Read (no Create, Write, Delete, Assign, Share, Append or AppendTo on any table), and organization-wide Read on every configured table, because Dataverse silently filters rows outside a user's read scope. A role, team or privilege the user may not see refuses the source.
A Microsoft Entra ID app registration signs in with OAuth 2.0 client credentials (secret reference) as a Dataverse application user. Columns protected by column-level security are not read. Optional incremental extraction by modifiedon. Records are processed inside your environment and never sent to DataNivra Cloud.
Planned authentication: Microsoft Entra ID application, OAuth 2.0 client credentials (secret reference); access token (secret reference).
What crosses the boundary
Connectors run inside the agent in your network. Only metadata, aggregates and evidence reach DataNivra Cloud:
- Schema, table and column names and data types (for file sets, operator-declared or opaque table names — never data-derived file names).
- Aggregates such as row-count estimates, null and distinct ratios; counts from 1 to 10 are reported as 10 (small-cell protection).
- Classification findings (which column looks like which kind of sensitive data) and relationship metadata.
- Evidence metadata: checksums, gate outcomes, engine and policy versions, and templated error codes.
Never sent:
- Any cell value, row, sample, minimum/maximum or top-k value — masked or not.
- Credentials, connection strings or resolved secret values: DataNivra stores only the secret reference.
- Free text copied from your data, or exception messages that contain values.
See the customer-resident architecture and how to verify these claims yourself.
Request this connector
We prioritise connectors by demand, engineering effort and strategic fit. Telling us that Microsoft Dynamics 365 matters to you is counted; it does not commit a delivery date.
Need something specific from the Microsoft Dynamics 365 connector? Request a feature (please describe it without real data).
All integrations · SaaS application test data management · Guides · Start free