Connector
If it has an ODBC driver, it's a source.
Every stack has systems nobody builds connectors for. The ODBC connector turns them into governed, live sources — same identity model, same virtual layer, no special case.
- Live at the source
- No replication
- Existing permissions
How Virtual Data Platform reaches ODBC
Outbound only
A Gateway inside the source's network connects outbound to your tenant — no inbound firewall rules, TLS on every connection.
Queried at the source
The Gateway queries the source directly through its connector, under the requesting user's own permissions — Microsoft Entra ID in, translated to the source's authentication.
Nothing persisted
Results stream back end-to-end encrypted and combine with your other sources in memory — no warehouse to fill, no copy to govern.
What teams do with ODBC
Bring legacy databases into the same governed layer as your strategic systems.
Reach niche and departmental systems without waiting for a dedicated connector.
Retire point-to-point export scripts — queries run against the source live instead.
What this connector covers
- Tables & views
- Free SQL queries
- Function calls
New connectors ship regularly — missing a source you need? Just ask.
Consume it in the tools you already use
Model once, then query from anywhere — every request under the user's own identity.
See your own data live in 30 minutes.
Start with a live demo — we'll show your use case in Excel, Power BI, R, or through an AI assistant. Then take it further with a free trial in your own isolated tenant.