Azure SQL Query

LAST UPDATED: MAY 23, 2025

Overview

Azure SQL Database is a fully managed cloud-based relational database service built on Microsoft SQL Server technology hosted on Azure Cloud service. This integration enables organizations to query table content of the given Azure SQL server.

D3 SOAR is providing REST operations to function with Azure SQL Query.

Azure SQL Query is available for use in:

Connection

To connect to Azure SQL Query from D3 SOAR, follow this part to collect the required information below:

Configuring Azure SQL Query to Work with D3 SOAR

READER NOTE

D3 vSOC’s public IP addresses are required to configure Azure SQL Query for use with D3 SOAR. If unknown, contact D3 to obtain them.

1. Log into the Azure portal.

   

2. Enter SQL servers in the search bar, then select the matching result.

   

3. Select the desired server.

   

4. Open the Security accordion, then select the Networking tab.

   

5. Allow the D3 vSOC public IP address to access the SQL Server by creating a new firewall rule.

   

   1. Click the + Add a firewall rule button.

   2. Provide a descriptive name for the rule

   3. Enter the IP address(es) obtained from D3.

   4. Click the OK button to save the rule.

Configuring D3 SOAR to Work with Azure SQL Query

1. Log in to D3 SOAR.

2. Find the Azure SQL Query integration.

   

   1. Navigate to Configuration on the top header menu.

   2. Click on the Integration icon on the left sidebar.

   3. Type Azure SQL Query in the search box to find the integration, then click it to select it.

   4. Click on the + Connection button on the right side of the Connections section. A new connection window will appear.

3. Configure the following fields to create a connection to Azure SQL Query.

   

   1. Connection Name: The desired name for the connection.

   2. Site: Specifies the site to use the integration connection. Use the drop-down menu to select the site. The Share to Internal Sites option enables all sites defined as internal sites to use the connection. Selecting a specific site will only enable that site to use the connection.

   3. Recipient site for events from connections Shared to Internal Sites: This field is displayed when Share to Internal Sites is selected for the Site field, allowing selection of the internal site for deploying the integration connection.

   4. Agent Name (Optional): Specifies the proxy agent required to build the connection. Use the dropdown menu to select the proxy agent from a list of previously configured proxy agents.

   5. Description (Optional): Add a description for the connection.

   6. Tenant (Optional): When configuring the connection from a master tenant site, users have the option to choose the specific tenant sites to share the connection with. Once this setting is enabled, users can filter and select the desired tenant sites from the dropdowns to share the connection.

      

   7. Active: Check the checkbox to ensure the connection is available for use.

   8. Configure User Permissions: Defines which users have access to the connection.

   9. System: This section contains the parameters defined specifically for the integration. These parameters must be configured to create the integration connection.

      

      1. Input the Server URL in the following format: <your-server-name>.database.windows.net.
      2. Input the Database name.

      3. Input the Username.

      4. Input the Password.

   10. Enable Password Vault: An optional feature that allows users to take the stored credentials from their own password vault. Refer to the password vault connection guide if needed.

   11. Connection Health Check: Periodically checks the connection status by scheduling the Test Connection command at the specified interval (in minutes). Available only for active connections, this feature also allows configuring email notifications for failed attempts.

4. Test the connection.

   

   1. Click on the Test Connection button to verify credentials and connectivity. A success alert displays Passed with a green checkmark. If the connection fails, review the parameters and retry.

   2. Click OK to close the alert window.

   3. Click + Add to create and add the configured connection.

Commands

Azure SQL Query includes the following executable commands for users to set up schedules or create playbook workflows. With the Test Command function, users can execute these commands independently for playbook troubleshooting.

List Tables

Retrieve all tables in the database.

Input

N/A

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.

SQL Query

Executes an SQL query. A list of all tables in the database can be obtained using the List Tables command.

Input

Output

To view the sample output data for all commands, refer to this article.

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.

Test Connection

Allows users to perform a health check on an integration connection. Users can schedule a periodic health check by selecting Connection Health Check when editing an integration connection.

Input

N/A

Output

Error Handling

If the Return Data displays Failed, an Error tab will appear in the Test Result window.

The error tab contains the details responded from D3 SOAR or third-party API calls, including Failure Indicator, Status Code, and Message. This can help locate the root cause of a command failure.