A Microsoft SQL connection lets the Microsoft SQL · Query step run SQL against your own SQL Server or Azure SQL database. You give Bizomate the server, the database, and a SQL Server user and password of your own.

Who can do this

  • Workspace Admins and Editors.
  • Plan: Microsoft SQL is a premium connection. You can add it and test its steps on any plan; publishing a workflow that uses it needs Starter, Pro or Enterprise.

Before you start

  • A SQL Server user. Bizomate signs in with a SQL Server user name and password (SQL authentication). Windows sign-in and Microsoft Entra sign-in are not used. Make a user for Bizomate and give it only the tables your workflows need.
  • Encryption. Bizomate always connects encrypted, so the server must accept encrypted connections. Azure SQL does.
  • Reachable from the internet. The server must have a public address, and its firewall must let Bizomate in on its port (1433 unless you changed it). A server on a private network or behind a VPN cannot be reached. If the firewall allows only listed addresses, add Bizomate's (below).

The addresses Bizomate connects from

If your server's firewall only lets in addresses you list, add all of these. Bizomate connects from one of them, and which one can change without notice, so allow every one:

20.244.77.107, 98.70.233.34, 98.70.238.182, 4.187.192.56, 4.187.192.83, 4.187.202.192, 4.247.208.118, 4.188.89.53, 20.235.194.47, 135.13.177.151, 135.13.180.237, 4.224.138.26, 4.224.139.74, 4.188.89.72, 4.247.208.154, 4.224.71.1, 4.188.115.70, 4.187.190.117, 20.219.174.118, 20.204.214.217, 4.247.214.195, 4.247.236.85, 4.247.215.225, 4.224.71.224, 4.224.115.37, 4.224.115.87, 4.187.214.53, 4.187.204.15, 20.204.211.52, 20.204.214.68, 20.192.171.20

These are the outgoing addresses of Bizomate's servers in Azure Central India (as of 2 October 2026). If they change, this article is updated.

Steps

  1. Select Connections in the bar at the top, then + Add connection.
  2. Under Database, select Microsoft SQL. It reads "Stored credential", with the diamond for paid plans.
  3. In Connection name, type a name — for example Consulace finance.
  4. In Server, type the server's address. For Azure SQL, as the example shows: tcp:consulace-sql.database.windows.net,1433. SQL Server takes the port after a comma.
  5. In Database, type the database's name.
  6. In User, type the SQL Server user. "A SQL Server user of your own. Give it only the tables your workflows need."
  7. In Password, type that user's password. "Stored encrypted. It is never shown again after you save."
  8. Optional: choose a date in This password expires on · optional if the password must be changed by then.
  9. Leave Test the connection before saving ticked.
  10. Select Save connection. It reads Testing while Bizomate signs in.

The toast "Connection added" says "“Consulace finance” is ready. Every workflow in this workspace can use it."

What happens next

  • The connection appears under Database. Its panel shows Server — "tcp:consulace-sql.database.windows.net,1433 · finance" — and never the user or password.
  • The Microsoft SQL · Query step lists it under Connection.
  • Test signs in and runs select 1, answering "Signed in to Microsoft SQL."

Good to know

  • On the Free plan the window notes: "Microsoft SQL is on paid plans. You can add it and test the steps that use it now; publishing a workflow that uses it asks for a paid plan."
  • Bizomate allows 15 seconds to connect.
  • Fields are never shown again; to change any of them, Reconnect and fill all four in again.

If something goes wrong

What you see Why What to do
"Give the server's address.", "Give the database's name.", "Give the user it signs in as.", "Give the user's password." That field is empty. Fill it in.
Microsoft SQL refused it — "SQL Server refused: … Nothing was saved." The server turned the sign-in down, or its firewall did not let Bizomate in. Check the user and password; in the server's firewall, allow outside connections on its port.
"… is not on the public internet, so workflows cannot reach it." The address is a private one. Use the server's public address.
"Use a SQL Server user and password in the connection string — User ID=…;Password=… — and no Authentication or Integrated Security setting." The stored connection does not use a SQL Server user. Reconnect with a SQL Server user and password.
"The connection string has no User ID. Replace it on Connections with one that has a SQL Server user and password." No user is stored. Reconnect with a user.
"The connection string names a Failover Partner, which workflows cannot use. Replace it on Connections with the server's own address." The stored connection points at a mirrored pair. Reconnect with the server's own address.