Azure SQL IntegrationConnect Azure SQL Database to KPI Tree. Two authentication methods, no ODBC driver required.
KPI Tree connects directly to Azure SQL Database using SQL authentication or Azure AD service principal. No ODBC driver to install or manage. The connection is always encrypted and requires a valid server certificate. Define metrics with T-SQL, map how they drive each other, assign ownership, and build the accountability layer your data is missing.
Connected in under an hour
Provide your server hostname, choose your authentication method, and KPI Tree validates the connection in real time.
Choose your authentication method
KPI Tree supports two ways to authenticate with Azure SQL Database. SQL authentication uses a standard username and password. Azure AD service principal uses a client ID, client secret, and tenant ID for passwordless, identity-managed access. Both methods encrypt the connection and require a valid server certificate.
Provide your connection details
Enter your server hostname, port (default 1433), and database name. KPI Tree validates the connection in real time, confirming it can authenticate and reach your database.
Define metrics and start building
Write T-SQL against your tables and views to define each metric. One query per metric on a configurable schedule, all downstream analytics off-database. Map how metrics drive each other, assign RACI ownership, and start closing the loop between data and action.
Built for the Azure ecosystem
KPI Tree connects to Azure SQL Database natively, with no additional drivers or middleware. Your existing Azure security and governance model stays intact.
Azure AD service principal authentication
Authenticate with a service principal using client ID, client secret, and tenant ID. No passwords to rotate, no user accounts to manage. Integrates with your existing Azure AD governance and conditional access policies.
No ODBC driver required
KPI Tree connects without an ODBC driver. No driver installation, no version management, no compatibility issues. The connection is always encrypted with TLS and requires a valid server certificate.
Off-database analytics
One query per metric on a configurable schedule. Comparisons, correlations, and analysis run in KPI Tree's compute engine without pushing additional queries to your database. Your DTU or vCore consumption stays predictable.
Two authentication methods. Pick the one that fits your security model.
SQL authentication uses a standard username and password for teams that prefer simplicity. Azure AD service principal uses client credentials for teams that want identity-managed, passwordless access integrated with their existing Azure AD policies. Both methods always encrypt the connection and require a valid server certificate. No ODBC driver is needed for either method.
- SQL authentication: username and password
- Azure AD service principal: client ID, client secret, tenant ID
- Always encrypted, requires valid server certificate
- No ODBC driver required for either method
Cause-and-effect trees built from your Azure SQL data.
Define metrics with T-SQL against your tables and views. Arrange them into cause-and-effect trees that model how your business actually works. When a number moves, trace the tree to understand which drivers changed. Assign RACI ownership so every metric has a named person accountable for it. Statistical correlation analysis surfaces relationships between metrics. Impact tracking verifies whether actions moved the needle.
- Metric trees map causal relationships between business measures
- RACI ownership assigns accountability to real people
- Statistical correlation analysis surfaces hidden drivers
- Impact tracking proves whether actions worked
One query per metric. No additional queries for comparisons or aggregations.
KPI Tree runs one query per metric on a configurable schedule. Comparison periods, correlations, regressions, and outlier detection all run in KPI Tree's compute engine without pushing additional queries to your database. Your DTU or vCore consumption stays predictable regardless of how many people use KPI Tree.
- No additional database queries for comparisons or aggregations
- DTU and vCore consumption stays predictable
- Configurable sync schedule per metric
- All downstream analytics run off-database
Your Azure infrastructure stays exactly as configured.
KPI Tree does not require changes to your Azure infrastructure. It connects to Azure SQL Database through your existing network configuration, authenticates through your chosen method, and reads data with a read-only user or service principal. Your existing firewalls, virtual network rules, and Azure AD policies stay in place.
- No changes to firewalls or virtual network rules
- Existing Azure AD policies remain enforced
- Read-only access only
- All credentials encrypted at rest
What KPI Tree adds on top of Azure SQL
Your database stores the data. KPI Tree adds the layer that turns it into understanding, ownership, action, and proof.
Cause and effect, not just queries
Metric trees map how every KPI drives the ones above it. When revenue drops, trace the tree to find whether it was traffic, conversion, or average order value - and who owns each driver.
Ownership that creates accountability
Every metric has a named owner with full RACI. Actions are tracked against the metric they were meant to move. Personalised action plans tell each team member what to focus on.
Off-database analytics that keep costs flat
One query per metric syncs data into KPI Tree's engine. Comparisons, correlations, and outlier detection all run off-database. Your Azure SQL costs stay predictable as your team grows.
Related integrations
Other data sources that work with KPI Tree.
Common questions
- SQL authentication (username and password) and Azure AD service principal (client ID, client secret, tenant ID). Both methods encrypt the connection and require a valid server certificate.
- No. KPI Tree connects to Azure SQL Database without an ODBC driver. No driver installation, version management, or compatibility issues.
- Server hostname, port (default 1433), database name, and your chosen authentication credentials (username/password for SQL auth, or client ID/secret/tenant ID for Azure AD).
- KPI Tree connects to Azure SQL Database. If your metrics are in Synapse dedicated SQL pools that are accessible via the same connection interface, they may work, but the integration is designed and tested for Azure SQL Database.
- One query per metric on a configurable schedule. All comparisons, correlations, and analysis run off-database. Your DTU or vCore consumption stays predictable regardless of how many people use KPI Tree.
- If you use dbt, see our dedicated dbt Cloud and dbt Core integration pages. They connect through the dbt semantic layer rather than directly to Azure SQL.
- Read-only access to the tables and views you want to define metrics against. No write access, no admin privileges.
- KPI Tree queries your database and processes aggregated results in its own engine. Raw row-level data is not persisted outside your environment. Your existing Azure security policies remain enforced.
Related guides
Deep dives into the frameworks and metrics that work with Azure SQL.
Connect Azure SQL in under an hour.
SQL or Azure AD authentication, no ODBC driver, always encrypted. Your Azure data stays where it is.
