Before you connect
Network access — Supaboard connects from a fixed set of egress IPs. Add them to your SQL Server firewall allow-list before attempting a connection. The current IP list is shown inside the connector form under Whitelist IPs. Database user permissions — The user you provide needs at minimum:CONNECTon the databaseSELECTon the target schema(s) and tables
Connection fields
Port note — The standard on-premises SQL Server port is1433. Azure SQL Database and many managed SQL Server instances use1433as well. Supaboard’s default shows3342— update it to1433for Azure SQL or most RDS/Cloud SQL instances.
SSH Tunnel fields
Shown when the SSH Tunnel toggle is enabled.Finding your connection details
Azure SQL
- Open your SQL server in the Azure Portal.
- On the Overview page, copy Server name — this is your Host (format:
servername.database.windows.net). - The default Port is
1433. - Under Security → Networking, add a firewall rule for each Supaboard egress IP.
- Ensure Allow Azure services and resources to access this server is set if needed.
Amazon RDS for SQL Server
- Open the RDS Console and select your instance.
- Under Connectivity & security, copy the Endpoint — this is your Host.
- The default Port is
1433. - Add Supaboard egress IPs to the instance’s VPC security group (inbound TCP on port 1433).
Google Cloud SQL for SQL Server
- Open the Cloud SQL Console and select your instance.
- Under Connect to this instance, copy the Public IP address — this is your Host.
- Default Port is
1433. - Under Connections → Authorized networks, add each Supaboard egress IP.
SSL
Enable the SSL toggle when your database requires encrypted connections (recommended for Azure SQL and all cloud-hosted instances — Azure SQL enforces SSL by default).- SSL Certificate — paste the server’s CA certificate in PEM format if your instance uses a self-signed or private CA. For Azure SQL and AWS RDS, the certificates are publicly trusted and no upload is needed.
SSH Tunnel
Use an SSH tunnel when your SQL Server instance is in a private network with no public IP. When to use it:- Instance is not publicly accessible
- On-premises SQL Server behind a corporate firewall
- Security policy requires all external traffic to pass through a bastion host
- The bastion server can reach the SQL Server host on port 1433
- Supaboard’s egress IPs are allowed on the bastion server’s SSH port (default 22)
- The SSH user has permission to forward connections
- If using a private key, it is in PEM format
Recommended database user permissions
GRANT SELECT ON SCHEMA line for each schema you want to expose. For finer-grained control, grant SELECT on individual tables:

