Connect Azure SQL Database to Infograph
What it brings in: Every table and view the user can read.
What you need
- An Azure SQL Database, and permission to change its server's networking in the Azure portal.
- A user with a password (SQL authentication). A server that allows only Microsoft Entra authentication cannot be used.
- Infograph's sync servers connect from 51.222.152.247.
Your connection string
Each part is one thing you fill in, and each can fail on its own.
Server=tcp:[server].database.windows.nethost: fix for "We couldn't find that host. Check the host name, then try again.",1433port: fix for "The host refused the connection. Check the port, and that your database accepts connections from Infograph's address.";Initial Catalog=[database]database: fix for "That database does not exist on this server.";User ID=[user]user: fix for "The username or password was not accepted.";Password=[password]password: fix for "The username or password was not accepted.";Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;Steps
Copy the server name
Open your database's Overview page and copy the Server name, which ends in .database.windows.net. Azure routes each login by that name, so use it rather than an IP address.
Allow Infograph through the firewall
Open the server, then Networking under Security. On the Public access tab, set Public network access to Selected networks: it is off by default. Under Firewall rules, add a rule for each address below, with it as both the start and the end IP address, then select Save. A new rule can take up to five minutes to apply.
51.222.152.247Create a read-only user
Infograph only reads. Give it its own user so you can see and revoke its access in one place. Connect to your database, not master, as the server admin, for example in the portal's query editor, and run this with your own password. It creates a contained user, which signs in to this one database.
CREATE USER infograph WITH PASSWORD = '[strong-password]'; ALTER ROLE db_datareader ADD MEMBER infograph;Copy your connection string
Open the database's Connection strings page under Settings and copy the ADO.NET string. Put the user you created in User ID and its password in place of the placeholder. The JDBC and ODBC strings work too.
Server=tcp:[server].database.windows.net,1433;Initial Catalog=[database];User ID=[user];Password=[password];Encrypt=True;TrustServerCertificate=False;Connection Timeout=30;Paste it in Infograph and choose your tables
Open Azure SQL Database in Infograph, paste the string under Connection string and press Connect. Pick the tables you want and Infograph starts loading them. A serverless database that has paused takes about a minute to resume, so if the first Connect fails, press it again.
Allow 51.222.152.247 through your firewall so Infograph can connect.
Connect
Troubleshooting
Each entry is the message Infograph shows when a connection fails. Open it for the fix.
This host is not reachable from Infograph. Use your database's public address.
The address is private. Host names containing privatelink, and private IP addresses, belong to a private endpoint that only your virtual network can reach. Use the Server name from Overview with public access on, or connect through an SSH server under Advanced.
We couldn't find that host. Check the host name, then try again.
Copy the Server name again from the database's Overview page. It ends in .database.windows.net.
The host refused the connection. Check the port, and that your database accepts connections from Infograph's address.
Azure turned the connection away. Either Public network access is set to Disable (error 47073), or 51.222.152.247 is missing from the server's firewall rules (error 40615). Open Networking under Security, set Public network access to Selected networks on the Public access tab, and add a rule for each address. A new rule can take up to five minutes to apply.
The server closed the connection. Check that it allows Infograph's address, and whether it requires an encrypted connection.
The server answered, then hung up before Infograph could sign in. Check its firewall allows 51.222.152.247, and that the host and port are the database's own rather than a proxy in front of it.
The host did not answer in time. Check the host and port, and that your firewall allows Infograph's address.
Check the host is the Server name from Overview and the port is 1433. If the server is reachable only through a private endpoint, connect through an SSH server under Advanced, and keep the Server name as the host.
The username or password was not accepted.
Azure refused the login. Use a SQL authentication user and its password, not a Microsoft Entra account or an access token. Enter the user name alone: Infograph adds the server name itself. A contained user signs in only to the database it was created in, so check the database name too. In a Server=...; string, put a password containing ; in double quotes.
Those credentials were not accepted.
Check the user, the password and the database name. If the server allows only Microsoft Entra authentication, Infograph cannot sign in. Turn that off on the server's Microsoft Entra ID page, under Settings, and connect as a user with a password.
That database does not exist on this server.
SQL Server signed you in but could not open the database. Check its spelling and case against the list from SELECT name FROM sys.databases. If the name is right, the login has no user in that database: run the CREATE USER and ALTER ROLE lines from the steps in it.
Through an SSH server
Infograph could not reach your SSH server. Check its address and port, and that it allows connections from Infograph's address.
Check the SSH server's public address and port, and that its firewall allows 51.222.152.247 on that port, usually 22.
Your SSH server only offers old encryption settings. Infograph needs a current OpenSSH with an Ed25519, ECDSA or RSA (SHA-2) host key.
Your SSH server only offers old encryption settings. Update OpenSSH on it. It needs an Ed25519, ECDSA or RSA (SHA-2) host key.
Your SSH server refused Infograph's key. Check the key is in authorized_keys for that user.
Add Infograph's public key, shown in the form when you turn on SSH, to ~/.ssh/authorized_keys for the SSH user you entered. Check that user exists and that the file is readable only by them.
Your SSH server's identity changed. If you expected this, trust the new server on the connection.
Infograph remembers your SSH server's key from the first connect, and the server now shows a different one. If you rebuilt or replaced the server, open the connection and press Trust the new server. If you did not, ask whoever runs the server before you trust it.
This connection has not trusted an SSH server yet. Open the connection and use Re-discover streams to trust it.
The connection has not checked your SSH server yet. Open the connection and press Re-discover streams. Infograph then remembers the server's key.
Your SSH server would not forward to the database host. Check the permitopen rule and the database host and port.
The SSH server would not pass the connection on to the database. In authorized_keys, the permitopen rule must name the database host and port exactly as you entered them. In sshd_config, AllowTcpForwarding must not be no. The database must also accept connections from the SSH server, for example in its firewall or security group.