Skip to content
Last updated

Integrate Microsoft Azure with Databox


Availability

userUsers, Editors, and Admins
accountAll accounts
planExclusive to select subscription plans

Azure SQL Database is a fully managed relational database service built on the SQL Server engine. It handles provisioning, patching, backups, and scaling automatically, and runs on the same engine as on-premises SQL Server instances while removing the need to manage underlying infrastructure. Connecting Azure SQL Database to Databox lets you pull data directly from your managed database, build datasets using SQL queries, and visualize business-critical figures alongside data from your other connected tools.

Connection

If you've already established a connection, you can reuse it to add new data sources to your Databox account.

Step 1: Create a read-only SQL Server login for Databox

Databox only reads data from your database — it never writes to it. Create a dedicated SQL Server login with SELECT-only permissions on the database you want to connect. You can run these commands using the Query editor in the Azure portal, or via a SQL Server client (such as SSMS or Azure Data Studio) connected to your instance.

CREATE LOGIN databox WITH PASSWORD = 'your_secure_password';
GO
USE your_database;
GO
CREATE USER databox FOR LOGIN databox;
GO
GRANT SELECT ON SCHEMA::dbo TO databox;
GO

Replace your_database with the name of the database you want to connect, and your_secure_password with a strong password. If you need to grant access to additional schemas, repeat the GRANT SELECT ON SCHEMA statement for each one.

NoteNote: The CREATE LOGIN statement must be run in the context of the master database, while CREATE USER and GRANT must be run against your_database. If using the Azure portal Query editor, switch between databases using the database selector at the top of the editor.

NoteNote: Avoid the following special characters in your password, as they can cause encoding issues when establishing the connection: `, ', ", /, \, and spaces.

Step 2: Enable public access on your Azure SQL server

Databox connects to Azure SQL Database over a public endpoint. Verify that the public endpoint is enabled on your logical SQL server.

  1. In the Azure portal, go to your SQL server resource (not the individual database).
  2. Under Security, click Networking.
  3. Under Public access, select Selected networks.
  4. Click Save to apply the change.

NoteNote: The server's fully qualified hostname is shown on the Overview page of your SQL server resource (e.g., myserver.database.windows.net). Copy this value — you will need it in Step 4.

Step 3: Add the Databox IP to your firewall rules

Azure SQL Database uses server-level firewall rules to control inbound network access. Add a rule that permits connections from the Databox IP address.

  1. In the Azure portal, go to your SQL server resource.
  2. Under Security, click Networking.
  3. Under Firewall rules, click Add a firewall rule and enter:
    • Rule name: Databox
    • Start IPv4 address: 52.4.198.118
    • End IPv4 address: 52.4.198.118
  4. Click Save.

Step 4: Enter your Azure SQL connection details in Databox

  1. In Databox, go to Data Sources > + New connection.
  2. Search for Microsoft Azure and click Connect.
  3. Fill in the connection form:
    • Data source name — a label for this connection in Databox.
    • Server Name — the fully qualified server name of your Azure SQL server, found on the Overview page in the Azure portal (e.g., myserver.database.windows.net).
    • Username — the SQL Server login name created in Step 1.
    • Password — the password for that login.
    • Database name (optional) — the specific database to connect to. Leave blank to connect at the server level.
    • Timezone — the time zone used to interpret date values in query results. Defaults to Etc/UTC.
  4. Click Connect.
connect

Datasets

The Microsoft Azure integration supports the creation of datasets, which allow you to define and shape the specific data you want to use for reporting in Databox. Datasets make it easier to focus on the most relevant information, enabling you to filter, visualize, and analyze metrics across projects, teams, and clients without writing complex queries each time.

Steps to create a dataset

  1. Select a table: Pick the appropriate schema within that database.
  2. Select columns: Browse and select the specific columns (fields) from your tables or views to include in your dataset. These columns define the structure and content of your dataset.

Optional: Write SQL

For more advanced use cases, you can write a custom SQL query instead of selecting columns manually. This allows you to:

  • Join multiple tables
  • Apply filters and aggregations
  • Format or transform data before importing it into Databox

Your query must return a valid tabular result to be used as a dataset.

Additional resources

Resources

For comprehensive details on metrics, data availability, templates, specifications, usage guidelines, and other key information, refer to the resources listed below.

FAQ

Do I configure firewall rules on the SQL server resource or the database resource?

Firewall rules are set at the SQL server (logical server) level, not on the individual database. A rule added to the logical server applies to all databases hosted on that server. In the Azure portal, navigate to the SQL server resource — not the SQL database — and open Security > Networking to manage firewall rules.

Does Databox support Azure Active Directory (Entra ID) authentication?

No. Databox connects to Azure SQL Database using SQL Server authentication (username and password only). Azure Active Directory (Microsoft Entra ID) authentication is not supported. Make sure the login you create in Step 1 uses SQL Server authentication, not Azure AD authentication.

What should I do if Databox cannot connect to my Azure SQL instance?

Check the following in order:

  1. Public access is set to Selected networks on the SQL server (under Security > Networking).
  2. A firewall rule exists with both start and end IP set to 52.4.198.118.
  3. The SQL Server login was created in the master database and a corresponding user with SELECT permissions exists in the target database.