Overview
What is Azure MySQL Database: Azure Database for MySQL is Microsoft's managed MySQL service for project teams that need a maintained relational database without having to manage the underlying server infrastructure. It runs MySQL Community Edition in more than 50 Azure regions. Microsoft manages service-level operations such as patching, backups, high availability, and monitoring, while the MySQL Community Edition engine is maintained upstream.
How to integrate Azure MySQL Database with Datagrid
The Azure MySQL Database Datagrid integration imports selected Azure MySQL rows and server context into Datagrid datasets on a schedule, so Datagrid's AI agents analyze the imported data, generate summaries, compare records, and flag defined exceptions alongside data from your other connected platforms. Azure MySQL is the source and Datagrid datasets are the destination: the documented integration supports scheduled, one-way imports and does not write back to or live-query the source server. Follow this setup order: prepare a reachable Flexible Server instance, authenticate with a read-only database login, then configure the scheduled data sync in Datagrid.
Prepare the Flexible Server
Confirm the access mode on the server's Networking page. For public access, add firewall rules in IPv4 format and keep TCP port 3306 open. Copy the server FQDN from the Azure portal in the format servername.mysql.database.azure.com. Microsoft requires the FQDN because the server IP is not guaranteed to remain static.
Use this configuration record to collect the required connection values before setup:
server_fqdn: servername.mysql.database.azure.com
tcp_port: 3306
database: <database-name>
authentication: MySQL username and password
objects: Selected database and management-plane objects
sync_schedule: <scheduled frequency>Authenticate the connection
Use MySQL native authentication for this procedure. Flexible Server accepts MySQL usernames and passwords by default. Azure enforces TLS 1.2 by default and denies TLS 1.0 and 1.1, so external connections run encrypted.
Record the authentication fields in this structure before opening Datagrid:
authentication_method: MySQL username and password
username: <mysql-username>
password: <mysql-password>Azure also offers Microsoft Entra ID authentication at the server level through the aad_auth_only parameter. That server capability is separate from the username-and-password path documented for this Datagrid connection.
Configure scheduled data syncs
Complete the integration in Datagrid with the prepared server, database, authentication, object, and schedule values.
In Datagrid, open Integrations > Connectors > Add new and select Azure MySQL Database.
Enter the prepared server address and the target Database.
Enter the MySQL username and password for the integration.
Select the sync objects in the Datagrid UI. Available objects include:
Database objects: tables, views, stored procedure objects
Management-plane objects: Server, Configuration, Database, Firewall Rule, Log File, Operation
Scope note: The MySQL REST API defines these Azure resource types. It does not provide another setup method for this procedure.
Set the Sync schedule and run the first import. Compare imported row counts against the source tables.
Use this field structure to verify the Datagrid configuration before running the import:
integration: Azure MySQL Database
database: <database-name>
authentication_method: MySQL username and password
selected_objects: <tables, views, stored procedure objects, metadata objects>
sync_schedule: <scheduled frequency>Why use Azure MySQL Database with Datagrid
Connecting Azure MySQL Database to Datagrid provides project teams with a structured execution layer for recurring analysis and oversight workflows.
Unified configuration review: Operations teams review firewall and configuration metadata in the same workspace as the tables they analyze, reducing separate configuration checks.
Managed data movement: Project teams avoid building and maintaining separate ETL jobs for the datasets used in recurring reports and audits.
Encrypted connectivity: Database operators keep imported data encrypted in transit through the documented MySQL authentication path.
Cross-platform context: Project teams compare MySQL tables against records from 100+ connected platforms in a single workspace and avoid manual reconciliation across separate systems.
Scoped imports: Imports include only the database and management-plane objects that operators select for agents.
Defined exception handling: Operations leaders compare imported configuration values against defined standards and route exceptions for operator review as part of the recurring oversight workflow.
What you can build with the Azure MySQL Database Datagrid integration
Synced datasets can power repeatable reporting, database analysis, cross-cloud comparisons, and server configuration reviews.
Scheduled operational reporting: Operations teams sync a subscription-billing or order table into Datagrid datasets on a recurring schedule. An agent analyzes the newest import and generates a period summary for the operators who own that table.
Plain-language analysis over production data: Account managers ask which accounts churned in the last billing cycle. The agent reads the synced MySQL dataset and returns the answer without handwritten SQL.
Cross-cloud database consolidation: Project teams sync Azure MySQL data into Datagrid alongside other managed MySQL sources or JDBC MySQL. Agents compare records across environments within a single workspace.
Server configuration and access audits: Database operators import selected management-plane objects during each sync. An agent summarizes the imported firewall rules, compares configuration values, and flags defined exceptions for review.
Resources and documentation
Entra ID authentication: Microsoft Entra ID sign-in requirements on Flexible Server.
Azure MySQL networking concepts: Public access, private access, and FQDN requirements.
Connection libraries reference: Supported client drivers and language quickstarts.
Frequently asked questions
Which MySQL versions does Flexible Server run?
The Flexible Server overview covers MySQL 5.7, 8.0, and 8.4. Use a reachable Flexible Server instance when configuring the Datagrid integration.
Which data objects can Datagrid import?
Operators select database and management-plane objects from the list in the setup procedure above. Stored procedures are selectable objects. The documented workflows analyze imported rows and metadata without executing the procedures.
How do you configure the Azure MySQL firewall for an external platform?
In public access mode, add the external service's IP addresses as firewall rules in IPv4 format. IPv6 entries produce a validation error; see the public access docs.
How do you verify TLS settings for external connections?
TLS 1.3 is available on MySQL 8.0 and later. The CA certificate is DigiCertGlobalRootG2. Clients should also trust Microsoft RSA Root CA 2017 during certificate rotation, per the TLS security docs.
How can external tools connect to a private access server?
Private access (VNet integration) removes the public endpoint. Non-Azure resources need a VPN or ExpressRoute connection, and external platforms can connect directly to public-access servers through firewall rules. If the server's access mode must change after creation, Azure generally allows a one-time move from private access to public access or Private Link, with 5 to 10 minutes of downtime and about 20 minutes for high availability servers, per the VNet networking concepts documentation.
Similar integrations
Amazon RDS: Common cross-cloud alternative and migration destination supporting MySQL-compatible instances and relational replication workflows.
JDBC MySQL: Direct TCP JDBC integration for MySQL, suited to operational workflows and agentic SQL automation against MySQL-compatible servers.
Google Cloud SQL - PostgreSQL: Cross-cloud PostgreSQL peer for migrating or comparing managed relational platforms across providers for analytics or transactional workloads.
Azure PostgreSQL Database: Azure-native PostgreSQL peer on the same managed platform, useful for migrations, analytics, and cross-engine architecture.