How to Connect Your Azure Database for MySQL to Indiequery

Last updated: November 21, 2025

Connect your Azure Database for MySQL to Indiequery to query and explore data through a web interface. No desktop apps, no command line. Just configure your firewall rules and connect in minutes.

Get Your Azure MySQL Connection Details

Log into the Azure portal at portal.azure.com and navigate to your Azure Database for MySQL flexible server. On the Overview page, you'll see your connection information:

  • Server name (Endpoint) - Format: <your-server>.mysql.database.azure.com
  • Admin username - The username you created during setup
  • Database - Your database name (no default is created automatically)
  • Port - 3306

You'll need your admin password. If you don't remember it, click Reset password on the Overview page to generate a new one. Azure shows the new password once - copy it immediately.

Add Indiequery to Firewall Rules

Azure blocks all external connections by default. You must add Indiequery's IP address to your server's firewall rules.

Click the Networking tab in the left sidebar. Under Firewall rules, click + Add firewall rule:

  1. Rule name - Enter "Indiequery" or any descriptive label
  2. Start IP - Enter 91.98.141.61
  3. End IP - Enter 91.98.141.61
  4. Click Save

The firewall rule takes up to 5 minutes to take effect. Once active, Indiequery can connect to your database.

Verify SSL Configuration

Azure requires SSL/TLS connections by default. This is controlled by the require_secure_transport server parameter.

To verify your SSL settings, click Server parameters in the left sidebar. Search for require_secure_transport. If it's set to ON (the default and recommended setting), all connections must use SSL.

Leave this setting as ON for security. Indiequery supports SSL connections and will connect with the "Require SSL" checkbox enabled.

Connect to Indiequery

Navigate to app.indiequery.com and click Add Database Connection. Enter your Azure connection details:

  1. Host - Your server endpoint (ending in .mysql.database.azure.com)
  2. Port - Enter 3306
  3. Database - Enter your database name
  4. Username - Your admin username
  5. Password - Your admin password
  6. Keep "Require SSL" checked (Azure requires SSL by default)
  7. Name your connection (e.g., "Azure Production")
  8. Click Add Connection

Indiequery tests the connection automatically. Once successful, you're ready to query your Azure MySQL database.

Public Access vs Private Access

Azure offers two networking modes:

Public access (allowed IP addresses) - Your server gets a public endpoint accessible from the internet. Requires firewall rules to whitelist specific IP addresses. This is what Indiequery uses.

Private access (VNet Integration) - Your server only has a private IP address within an Azure virtual network. Only accessible from resources in the same VNet. Not accessible from external tools like Indiequery unless you set up VPN or ExpressRoute.

If your server uses private access only, you must enable public access and configure firewall rules before Indiequery can connect. You can enable both public and private access simultaneously.

Allow Azure Services Option

When configuring firewall rules, Azure offers a checkbox to "Allow public access from any Azure service within Azure to this server."

This option allows all Azure datacenter IP addresses to connect - useful if you have applications running in Azure that need database access. However, it's separate from Indiequery's firewall rule. You still need to explicitly add 91.98.141.61 for Indiequery to connect.

Common Connection Issues

"Connection timed out" or "Connection refused"

Verify you added the firewall rule for 91.98.141.61 in the Networking tab. Click Save after adding the rule and wait 5 minutes for changes to take effect. Confirm your server is running (check the Overview page for status).

"SSL connection required"

Azure enforces SSL by default. Keep "Require SSL" checked in Indiequery when connecting. If you see this error with SSL enabled, verify your require_secure_transport parameter is ON in Server parameters.

"Authentication failed"

Double-check your admin username and password. If you don't remember the password, use Reset password on the Overview page. Admin usernames have specific requirements - they can't be reserved names like admin, root, mysql, or azure_superuser.

"Unknown database"

Unlike some other MySQL services, Azure Database for MySQL doesn't create a default database automatically. You must create a database first. Check the Databases section in the left sidebar to see available databases, or create one using SQL: CREATE DATABASE your_database_name;

"Firewall rule not taking effect"

Firewall rule changes take up to 5 minutes to propagate. If you just added the rule, wait a few minutes and try connecting again.

Connection String Format

Azure provides connection strings in the format:

mysql://username:[email protected]:3306/database?ssl-mode=REQUIRED

Indiequery uses individual connection parameters (host, port, database, username, password) rather than connection strings. Extract each component from the connection string when entering details in Indiequery.

Read Replicas

Azure Database for MySQL supports read replicas for read scaling and disaster recovery. Create a read replica in the same region or a different Azure region.

In the Azure portal, navigate to your primary server and click Replication in the left sidebar. Click + Add replica and choose your configuration. Once the replica is running, it gets its own server endpoint.

Add the replica's endpoint to Indiequery as a separate connection. Configure firewall rules on the replica to allow 91.98.141.61. Queries against the replica don't affect your primary server's performance.

High Availability

Azure offers zone-redundant high availability for flexible servers. This creates a standby replica in a different availability zone but maintains a single endpoint.

You don't need separate connections for HA configurations - the primary endpoint automatically handles failover. Your Indiequery connection continues working even if Azure fails over to the standby server.

Next Steps

Once connected:

  • Browse tables and schemas in the schema explorer
  • Run SQL queries with autocomplete
  • Create charts and visualizations
  • Save queries for reuse
  • Build dashboards
  • Export results to CSV, JSON, or Markdown

Navigate to the query editor and start exploring your Azure MySQL data.

← Back to Hosting Integration