Azure Database Connection Guide

Use this page when your source or target is hosted in Azure Database for MySQL or Azure Database for PostgreSQL.

This guide focuses on the base connectivity steps that DBConvert Streams needs:

• firewall and network access
• server endpoint and credentials
• TLS/SSL requirements
• the extra PostgreSQL setting needed before CDC setup

For current workflow boundaries, see the product introduction page.

Base setup

1. Sign in to the Azure Portal.
2. Open your MySQL or PostgreSQL server resource.
3. Confirm the server endpoint, port, and allowed network path from the DBConvert Streams deployment.
4. Confirm which workflow you want: Load only, or PostgreSQL CDC source.

Network access

1. Open the server Networking section.
2. Add the public IP address of the DBConvert Streams deployment, or the appropriate IP range if your environment requires it.
3. Save the firewall rule.
4. Confirm the server is reachable on:
   • 3306 for MySQL
   • 5432 for PostgreSQL

TLS/SSL configuration

TLS/SSL is typically enforced on Azure-managed databases by default.

1. Download the Azure CA certificate from Microsoft's documentation for the selected service.
2. In DBConvert Streams, enable SSL/TLS for the connection.
3. Use a verification mode that matches your certificate setup.

Use SSL Configuration for the general certificate workflow.

Connection setup in DBConvert Streams

Typical MySQL fields:

• host: <servername>.mysql.database.azure.com
• port: 3306
• username
• password
• database
• SSL/TLS settings

Typical PostgreSQL fields:

• host: <servername>.postgres.database.azure.com
• port: 5432
• username
• password
• database
• optional schema scope
• SSL/TLS settings

Use:

• MySQL Server Configuration for server-level MySQL guidance
• PostgreSQL Server Configuration for server-level PostgreSQL guidance

PostgreSQL CDC preparation

If Azure PostgreSQL is the CDC source, base connectivity is not enough.

1. Open Server parameters in Azure Portal.
2. Confirm your deployment uses Azure Database for PostgreSQL — Flexible Server, which supports logical replication. Single Server deployments have limited or no support for wal_level = logical.
3. Set wal_level to logical.
4. Restart the server when Azure prompts for it.
5. Then complete the remaining steps in PostgreSQL CDC Source Configuration.

After restart, verify:

SELECT name, setting
FROM pg_settings
WHERE name IN (
  'wal_level',
  'max_replication_slots',
  'max_wal_senders'
);

Validation checklist

1. Test the connection from the Data Explorer sidebar (right-click → Test connection) or from the connection editor. If TLS fails, verify the Azure CA certificate is uploaded and the SSL mode matches the server enforcement setting.
2. Open the connection in Data Explorer to confirm visibility.
3. For PostgreSQL CDC, confirm the deployment is Flexible Server and run SHOW wal_level — it must return logical. Single Server deployments may not support this.
4. For MySQL, verify the @servername suffix is included in the username if Azure requires it (e.g. user@servername).

Related docs

• MySQL Server Configuration
• PostgreSQL Server Configuration
• PostgreSQL CDC Source Configuration