Your own applications in every report
Projects, orders, or usage recorded in Azure SQL show up on the same dashboards as the rest of the business, not in a separate report someone has to request.
Bring the records your own applications keep in Azure SQL into Go Fig's dashboards, reports, and answers, read where they sit and never changed.
Azure SQL is often where a company's own applications keep their records, like projects, orders, or usage. Your data team connects it once with a solutions engineer. The records stay in your Azure SQL database, and Go Fig reads them there rather than copying them into its own storage. The connection is read only, and we recommend a read-only user so nothing in the database can change. Those records then sit next to your CRM and every other system you connect, on dashboards and in scheduled reports. Celeste, Go Fig's AI analyst, can answer questions from them too.
Projects, orders, or usage recorded in Azure SQL show up on the same dashboards as the rest of the business, not in a separate report someone has to request.
Follow a newly closed customer's first weeks from the records in your database, so onboarding doesn't stall quietly.
Check how a customer has been using what they bought before anyone reaches out about a renewal.
In Azure SQL, your data team creates a user for Go Fig and grants it permission to read only the tables and views it should see (it can look but never change anything).
Add Go Fig's server IP to the Azure SQL firewall. The connect form shows the address to allow. Without it, the connection cannot reach the database.
Add the server host (your-server.database.windows.net), database name, username, password, and port. Confirm the IP allowlist in the form.
Open Go Fig and look for the tables you granted. Each time a report or an answer needs them, Go Fig reads them fresh from Azure SQL.
You need someone who can create a database user and add a firewall rule in Azure, usually on your data or IT team. A solutions engineer works through the rest of the connection with them.
No. The records stay in your Azure SQL database and Go Fig reads them there. So it can find the right table, Go Fig's search index keeps field names, descriptions, and a few sample rows, as our security page explains.
Go Fig reads the database each time the data is used, so a report or an answer is as current as the records in Azure SQL.
No. The connection is read only. We recommend giving Go Fig a read-only user too, so the database itself makes sure nothing can change.
The server host, database name, a username and password, the port (1433 by default), and a firewall rule that allowlists Go Fig's IP.
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.