Universal Connector & Client Integrations

No new front end. We come to yours.

The Universal Connector reaches every tool we've never heard of — and we built dedicated native clients for the ones people live in.

Universal Connector

Start here: one branded umbrella over two generic endpoints — so any SQL- or REST-speaking tool connects with zero plugins, no driver and nothing on anyone's roadmap.

Universal Connector

unique to Virtual Data Platform

The tool you need to connect was never on anyone's roadmap.

If your tool can talk to SQL Server, it can talk to every system Virtual Data Platform reaches. Read that again.

The virtual SQL Server (TDS) endpoint means any client built for Microsoft SQL Server or Azure SQL connects unchanged — no driver, no plugin. Power BI is the flagship example; DBeaver, Tableau and custom apps connect the same way.

Power Query (Power BI)

Sql.Database("yourtenant.eu01.virtualdataplatform.com", "MyCompany",
    [Query = "SELECT * FROM Logistics.OrdersBacklog WHERE Plant = 'Graz'"])

OData endpoint

Your tool speaks REST, not SQL.

The other half of the umbrella — a REST/OData endpoint for everything that isn't SQL.

From low-code platforms to legacy middleware, anything that can call a REST service reads your Virtual Datasets the same governed way, under the user's own identity — the long tail the SQL endpoint doesn't reach.

Dedicated clients

On top of the Universal Connector, dedicated native clients for the tools people live in — the same governed, live data, queried natively in each.

Excel Add-in

end-to-end encrypted

Your controllers will not leave Excel — and they shouldn't have to.

Live enterprise data in the world's most popular BI tool. Refresh, don't re-export.

Two access modes in one add-in: formulas for power users, a visual sidebar wizard for everyone else.

The formula

Address a dataset by its Category and name, then pass parameters straight from the worksheet: change B2, hit refresh, done.

Excel

=VDP.GetData("Finance", "SalesByRegion", "region=" & B2)

R & Python packages

end-to-end encrypted

Your notebook runs on a stale CSV someone exported last week.

Governed, live data in R and Python — under your own identity.

Native packages bring Virtual Datasets straight into data-science workflows: authenticate with Entra ID, query a dataset by its Category and name, and get a data frame back — live, and run under your own permissions. The example below is R; the Python package follows the same pattern.

library(VDP)

token    <- Token$new()
vdp_data <- VDP$new(token)

vdp_data$param$add_parameter_body(
  vec_parameter_name  = c("Plant"),
  vec_parameter_value = c("Graz")
)

df <- vdp_data$get("Logistics", "OrdersBacklog")

MCP Server

AI-ready

Your AI assistant is guessing because it cannot see real data.

Your AI assistants, on real data, with real permissions.

The MCP server exposes Virtual Datasets as tools to any MCP-capable assistant — same per-user identity, auth translation and sandboxing as human access. The AI & MCP use case has the full picture.

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.

Book a live demo Request free trial