Overview
What is Azure SQL Database: Azure SQL Database is Microsoft's fully managed relational database service, built on the SQL Server engine. Microsoft handles patching, backups, availability, and monitoring. The vCore purchasing model offers three tiers: General Purpose, Business Critical, and Hyperscale.
How to integrate Azure SQL Database with Datagrid
Project teams use Azure SQL Database as the operational store for orders, customers, transactions, and application records. Through its standard SQL endpoint at <servername>.database.windows.net, Datagrid imports configured tables, views, and stored procedure outputs on a schedule you set. Data flows one way on import, from Azure SQL Database into Datagrid; the import does not write back to the source, and from there Datagrid's AI agents read, classify, and enrich records before routing finished work to the systems where project teams act on it, including automated row-level exports to MS SQL, MySQL, RDS, and BigQuery. Follow this setup order: configure Azure SQL Database access, authenticate the Datagrid integration, then schedule the data sync.
Configure Azure SQL Database access
Configure access on the Azure side first, then add the connection in Datagrid.
Add Datagrid's egress IP addresses to your server-level IP firewall rules in Azure. Obtain the current addresses from the connection information provided for the Datagrid integration. Firewall changes take up to 5 minutes to propagate, per the firewall rules docs.
Create a database user for Datagrid and grant it read permissions, such as the
db_datareaderrole.In Datagrid, add a new integration and select Azure SQL Database.
Enter the Server name as
<servername>.database.windows.net, then the Database, Username, and Password.Confirm that outbound access to Azure SQL Database is open on port
1433.
Use the following configuration as a field-level reference. Replace each placeholder with the values for your Azure SQL Database environment.
server: <servername>.database.windows.net
port: 1433
database: <database-name>
username: <sql-username>
password: <sql-password>
encryption: TLS 1.2 or later
sync: scheduled intervalAuthenticate the Datagrid integration
Give the integration an SQL authentication login with a username and password. Azure stores logins in the master or as contained users in individual databases and enforces password complexity for these credentials. Keep SQL authentication active for the integration's database user because Entra-only authentication disables SQL authentication at the server level.
Azure SQL Database encrypts all connections and requires TLS 1.2 at minimum.
Schedule the data sync
Configure the scheduled pull after the credentials pass the connection check. The sync has the following operating details:
Objects synced: Datagrid imports the database objects configured for the integration.
Direction: The scheduled sync is a one-way import from Azure SQL Database into Datagrid.
Frequency: Datagrid runs scheduled pulls at the interval configured by the project team.
Why use Azure SQL Database with Datagrid
The integration provides teams with a direct execution layer to turn operational relational data into answers and actions.
Direct relational read access: Operations leaders query configured database objects directly, bypassing a separate report request.
Agentic enrichment of raw records: Project teams classify text columns, extract structured values, and enrich each record before routing it.
Cross-platform routing: Project teams route enriched records to HubSpot CRM and Jira for follow-through, with Intercom as an additional downstream system.
Natural-language answers from operational data: Project leaders query synced schema and records with plain-language questions.
Cross-source context: Account and project teams complete the workflow by cross-checking Azure SQL rows against other connected Datagrid sources in one pass.
What you can build with Azure SQL Database Datagrid integration
Project teams can turn operational database records into repeatable workflows for analysis, enrichment, routing, and reporting. The following workflows connect specific records to the decisions and systems that depend on them:
Operational Q&A agents: Operations leaders sync order, customer, commitment, and transaction tables so project teams can ask questions directly. A project manager can ask which purchase orders have been open for more than 90 days, which invoices have gone overdue this week, or which RFI commitments remain unresolved. A data analysis agent answers from the synced tables without a report request.
Structured extraction from text columns: Project teams process support tickets, invoices, proposal notes, and client requests that carry free-text fields. An agent reads each synced record, classifies it, extracts structured values, and routes the output downstream. This mirrors the pattern Microsoft documents for AI-enriched Azure SQL.
Change-driven cross-platform sync: Operations and account teams use changed records to keep CRM commitments and project tickets current. Change Data Capture and change tracking mark new and changed rows in Azure SQL Database, according to Microsoft's CDC overview. Project teams expose those records through an imported table or view, and agents then create CRM records or update tickets in connected systems.
Warehouse and reporting pipelines: Project leaders pull operational tables from Azure SQL Database for portfolio reporting. Row-level exports write to BigQuery, MS SQL, MySQL, or RDS for analytics and BI. Microsoft Fabric is also available as a Datagrid integration for teams whose reporting lives there. Azure SQL Database is a standard operational source in Microsoft's analytics architecture, completing the reporting workflow.
Resources and documentation
Connect and query guide: Azure SQL Database connection and query options.
IP firewall rules documentation: Server-level network access requirements.
Entra authentication overview: Identity options for Azure SQL Database.
Change data capture overview: Setup reference for tier requirements and CDC behavior.
Frequently asked questions
How do I fix connection error 40615?
Error 40615 means Datagrid's egress IPs are missing from the Azure SQL Database server's allow list. Add the current Datagrid egress IPs to the Azure IP firewall rules, then wait for propagation, which takes up to 5 minutes. Microsoft's documentation warns that NAT can cause a tool's outgoing IP address to differ from its configured IP address.
Which port does Datagrid use?
Datagrid connects to Azure SQL Database over TCP port 1433. Because Datagrid connects from outside Azure, the connection uses the Proxy connection policy by default. That policy routes traffic through the Azure gateway, according to Microsoft's connectivity architecture.
Which authentication method should I use?
Use SQL authentication for this Datagrid integration. Azure SQL Database accepts both authentication methods, and Microsoft recommends Entra-based identities where possible. However, Microsoft's security best practices note that Entra authentication is not supported for every tool or third-party application, and Entra-only mode prevents the SQL login from connecting.
How do I resolve serverless error 40613?
Retry the Datagrid scheduled import after Azure SQL Database resumes. Microsoft's serverless tier docs state that the first connection to a paused database resumes it and returns error 40613. The database resumes in about a minute. If Datagrid exposes a connection-timeout setting for this integration, set it to at least 60 seconds. Otherwise, retry the Datagrid import after Azure SQL Database resumes.
Can Datagrid sync only changed rows?
Yes, when the project team exposes changed rows through an imported table or view. CDC and Azure SQL change tracking are separate mechanisms, and both can identify changes for the Datagrid scheduled import. CDC runs on all vCore-based tiers. On the DTU model, CDC requires S3 or higher; Basic, S0, S1, and S2 require a watermark-based query or full-object imports for CDC-based workflows. Serverless databases do not run CDC while paused. Without either mechanism, the Datagrid scheduled import pulls full objects.
Similar integrations
Amazon RDS: Common alternative managed relational service for migration comparisons and cross-cloud ETL alongside Azure SQL Database.
JDBC MySQL: JDBC-based direct database connectivity for MySQL, useful for migrations, cross-database ETL, or hybrid architectures with Azure SQL Database.
Google Cloud SQL - PostgreSQL: GCP's managed PostgreSQL service, paired with Azure SQL Database for multi-cloud architectures, migrations, and cross-database analytics.
Azure PostgreSQL Database: Azure's managed PostgreSQL service, co-deployed with Azure SQL Database as an OLTP/OLAP companion in hybrid data architectures.
Snowflake: Cloud data warehouse destination for analytics and BI pipelines ingesting operational data from Azure SQL Database.
Azure Data Lake Storage: Enterprise data lake destination for Fabric mirroring, staged ETL, and file-based ingestion originating from Azure SQL Database.