Skip to main content

​
Prerequisites

  • An Azure account with an Azure Database for PostgreSQL, MySQL (Flexible Server), or Azure SQL Database
  • A VexiData account

​
Connect Azure Database to VexiData

1

Get your connection details

  1. Log in to the Azure Portal
  2. Navigate to your database server
  3. On the Overview page, copy the Server name (FQDN)
ParameterPostgreSQL ExampleMySQL ExampleSQL Server Example
Hostmyserver.postgres.database.azure.commyserver.mysql.database.azure.commyserver.database.windows.net
Port543233061433
DatabaseYour database nameYour database nameYour database name
UsernameYour admin usernameYour admin usernameYour admin username
PasswordYour admin passwordYour admin passwordYour admin password
On Flexible Server, use your plain username (e.g., myadmin). The @servername suffix is not required.
2

Add VexiData to firewall rules

Azure blocks all external connections by default. You must add VexiData’s IP addresses.
  1. Go to your database server’s Networking page
  2. Under Firewall rules, click Add a firewall rule
  3. Add each of VexiData’s IPs:
Rule nameStart IPEnd IP
VexiData 1139.59.53.167139.59.53.167
VexiData 2165.22.217.42165.22.217.42
  1. Click Save
Firewall changes can take up to 5 minutes to apply. If your connection fails immediately after saving, wait and try again.
3

Add the connection in VexiData

  1. Go to Data Sources in VexiData
  2. Click PostgreSQL, MySQL, or SQL Server depending on your server type
  3. Fill in the details:
FieldValue
Display NameA name to identify this connection (e.g., “Azure Production”)
HostYour server FQDN (e.g., myserver.postgres.database.azure.com or myserver.database.windows.net)
Port5432 (PostgreSQL), 3306 (MySQL), or 1433 (SQL Server)
DatabaseYour database name
Schemapublic (PostgreSQL) or dbo (SQL Server)
UsernameYour admin username
PasswordYour admin password
4

Test and save

Click Test & Save Connection. VexiData will verify it can reach your database. Once connected, your schema will be analyzed automatically.

​
Troubleshooting

  • Verify VexiData’s IPs are in your Firewall rules. Changes take up to 5 minutes to apply
  • Make sure you’re using the Server name (FQDN), not an IP address
  • Check that your server is running in the Azure Portal
  • Azure enforces SSL (TLS 1.2+) by default. VexiData handles this automatically
  • If you see SSL errors, verify the host and port are correct
  • For PostgreSQL and MySQL (Flexible Server), use your plain username without the @servername suffix
  • For Azure SQL Database, use your admin login configured during creation
  • Reset your password from the Azure Portal if needed
  • For PostgreSQL, confirm your tables are in the public schema. For SQL Server, confirm they’re in the dbo schema. Update the Schema field in VexiData if they’re in a custom schema
  • Check that your database user has SELECT permissions on the tables