Overview
What is Azure Database for MySQL: Azure Database for MySQL is Microsoft's fully managed MySQL database service, built on MySQL Community Edition and deployed exclusively as Flexible Server. It handles patching, backups, scaling, and high availability automatically, freeing operators to focus on application logic rather than infrastructure. The service supports MySQL 8.0 and 8.4, runs across 50+ Azure regions, and offers up to 99.99% SLA with zone-redundant high availability.
Datagrid's Azure MySQL Database integration imports Azure MySQL data and metadata into Datagrid datasets. In the Datagrid setup flow, operators select the database objects they want to include, such as tables, views, or stored procedures. Datagrid's documented supported object list for this integration also includes Azure management-plane objects such as Server, Configuration, Database, Firewall Rule, Log File, and Operation. That means the setup selection covers the database objects you import, while the documented supported object list also references Azure server-level and management objects.
The primary data flow is one-way: Azure MySQL into Datagrid. Operators configure the connection with server credentials, select the specific data to import, and set a sync schedule. From there, Datagrid's AI agents access the latest imported information to execute tasks like anomaly detection across tables, automated report generation, and cross-platform data validation without manual exports or custom pipelines.
How to integrate Azure MySQL Database with Datagrid
The Azure MySQL Database integration imports Azure MySQL information into Datagrid datasets on a configurable schedule. The setup follows four steps: prepare Azure access, connect the integration, authenticate the connection, and configure scheduled syncs.
Prepare Azure access
Before connecting, confirm the following:
You have an active Azure account with permissions to access Azure Database for MySQL.
You have your Flexible Server details ready: server name, database name, username, and password.
Datagrid's IP addresses are allowlisted in your Azure MySQL firewall rules. Firewall changes take up to 5 minutes to propagate.
Your server uses public access networking, not private VNet integration. The networking model is set at server creation and cannot be changed afterward.
Connect the integration
Click + Create in the top left of the Datagrid interface.
Select Connect Apps.
Search for Azure MySQL Database in the integration list.
Enter your server name, database name, username, and password.
Click Next.
Select the data objects you want to import, including tables, views, or stored procedures.
Click Start First Import to begin your first data sync.
Authenticate the connection
The integration uses username and password authentication against your Azure MySQL Flexible Server. All connections require TLS 1.2. Azure enforces this by default on every Flexible Server instance. Use the server's fully qualified domain name for the connection, not the IP address.
host: <servername>.mysql.database.azure.com
database: <database_name>
username: <username>
password: <password>
authentication: username_password
tls: "1.2"
network_access: public
selected_objects:
- tables
- views
- stored_procedures
sync_direction: azure_mysql_to_datagrid
See Azure's TLS connection setup guide for certificate details.
Configure scheduled syncs
Navigate to your Azure MySQL Database dataset in the left panel.
Click ... in the top right corner of the dataset.
Click Edit Pipeline to adjust your integration settings.
Click Schedule next to the Import Configuration button.
Set the sync frequency: daily, weekly, or monthly.
Specify the time of day for the sync to run.
Define optional downtime windows when syncs should not occur.
Click Update to save the new schedule.
Review data sync behavior
The integration runs as a scheduled import from Azure MySQL into Datagrid.
Direction: One-way (Azure MySQL → Datagrid)
Setup selection: Tables, Views, and Stored Procedures
Documented supported objects: Server, Configuration, Database, Firewall Rule, Log File, Operation
Frequency: Configurable: daily, weekly, or monthly
Method: Scheduled import with optional downtime windows
Once the schedule is in place, Datagrid keeps the dataset current for downstream agent workflows. For full setup details, use the Datagrid integration documentation linked at the top of this page.
Why use Azure MySQL Database with Datagrid
Datagrid gives operators running mission-critical programs a direct way to bring managed MySQL data into the workflows their teams already run.
AI agents execute work on imported database information: Datagrid's AI agents work with the Azure MySQL information brought into Datagrid datasets for cross-referencing, reporting, and autonomous workflows.
Scheduled syncs without custom pipelines: Configure daily, weekly, or monthly imports from the Datagrid interface. No ETL scripts or middleware required.
Structured data across connected workflows: Combine Azure MySQL data with files, documents, and records from other connected systems so Datagrid's AI agents can reason across your full data stack.
Managed infrastructure on both sides: Azure handles database patching, backups, and scaling. Datagrid handles data processing and agent orchestration.
Granular data selection: Select the tables, views, or stored procedures you want during setup. This keeps datasets focused and agent workflows precise.
What you can build with Azure MySQL Database and Datagrid
Connecting Azure MySQL Database to Datagrid gives teams a way to turn database records into repeatable execution workflows.
Common workflows include the following:
Automated business intelligence from transactional data: Import order, customer, and product tables from Azure MySQL into Datagrid. AI agents cross-reference records against data from your CRM or analytics platforms, then generate summary reports and flag anomalies like revenue drops or fulfillment delays without manual dashboard configuration.
Cross-platform data validation for e-commerce operations: Sync product catalog and inventory tables from your MySQL-backed e-commerce platform into Datagrid. AI agents compare inventory counts against shipment records from cloud storage or ERP exports and identify mismatches before they reach customers.
CMS content audit and compliance checks: Pull content management tables backed by MySQL into Datagrid. Agents scan metadata, publication dates, and author records, then flag outdated content, missing fields, or records that violate internal publishing standards.
Application performance monitoring with contextual data: Import slow query logs and operational metrics from your Azure MySQL Flexible Server. Datagrid's AI agents correlate database performance data with application-level logs from developer tools and identify root causes across systems.
These workflows work best when teams need one place to compare structured database records with the rest of their operating data.
Similar integrations
Teams that work across structured data and connected business systems may also look at these related Datagrid integrations already referenced on this page:
CRM integrations: Relevant when AI agents cross-reference Azure MySQL records against customer and account data for reporting and validation workflows.
Analytics integrations: Relevant when teams compare imported MySQL tables with reporting systems to generate summaries and investigate anomalies.
Document management and file storage integrations: Relevant when teams compare database records against file-based exports, stored records, and supporting metadata.
Developer and utility tool integrations: Relevant when teams correlate Azure MySQL operational data with application logs and technical workflow data.
Resources and documentation
Use the following resources for setup details, Azure configuration, and service reference material:
Azure MySQL Database connector documentation - Setup steps, prerequisites, and supported data objects
Azure Database for MySQL Flexible Server overview - Architecture, deployment model, and feature reference
Azure MySQL REST API reference - Management-plane operations for programmatic server access
Azure MySQL networking overview - Public access vs. private VNet integration models
Azure MySQL service tiers and storage - Burstable, General Purpose, and Memory Optimized tier details
Frequently asked questions
Do I need to configure anything in Azure before Datagrid can connect?
Yes. You must add Datagrid's IP addresses to your Flexible Server's firewall rules. In the Azure portal, navigate to your server's Networking settings and add a firewall rule with Datagrid's IP range. Firewall changes can take several minutes to propagate, so wait before testing the connection.
What MySQL versions does Azure Database for MySQL support?
Azure Database for MySQL Flexible Server supports MySQL 8.4 and 8.0. See the Flexible Server overview for the complete list of supported engine versions.
Can I change my server from private to public network access after creation?
No. The connectivity method is chosen at server creation and cannot be changed afterward. If your server uses private access only, you would need to provision a new server with public access to connect with external platforms like Datagrid.
Does Datagrid connect as read-only or read-write to Azure MySQL?
Datagrid's integration performs import-based data sync, pulling data from Azure MySQL into Datagrid datasets. The access level depends on the credentials you provide. For read-only imports, grant the integration user SELECT permissions only.
What are the differences between Burstable, General Purpose, and Memory Optimized tiers?
The three Flexible Server tiers target different workloads. Burstable suits low-cost dev/test environments. General Purpose handles production workloads with high concurrency. Memory Optimized supports high-performance transactional or analytical applications with up to 32 TB of storage. Full tier specifications are in the service tiers documentation.
Browse by category
Database
CRM
Document management and file storage
Analytics and marketing
Developer and utility tools