Microsoft Azure MySQLManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth233 EndpointsREST
For Agents
Provision and manage Azure Database for MySQL servers, databases, firewall rules, vnet rules, and configurations. Covers 33 control-plane endpoints under Microsoft.DBforMySQL.
Use for: Provision a new Azure Database for MySQL server in eastus, Add a database named orders to an existing MySQL server, Create a firewall rule allowing traffic from 203.0.113.0/24, I need to attach a virtual network rule for subnet appsubnet to my MySQL server
Not supported: Does not execute SQL queries, manage backups, or perform point-in-time restore — use for Azure Database for MySQL control plane operations only.
Jentic publishes the only available OpenAPI specification for Azure Database for MySQL management, keeping it validated and agent-ready. The Microsoft.DBforMySQL Resource Provider exposes full lifecycle management for managed MySQL servers, databases, firewall rules, virtual network rules, configurations, log files, and Active Directory administrators. It is the control plane behind Azure Database for MySQL on the Single Server tier, covering provisioning, scaling, network access, security configuration, and operational telemetry. Server names, regions, and SKUs can be checked, validated, and changed without restarting the engine in many cases.
Install Jentic One Beta
Connect the MySQLManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MySQLManagementClient, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with MySQLManagementClient API.
Provision MySQL servers with a chosen SKU, version, and storage profile
Add or remove databases on an existing managed MySQL server
Configure firewall rules to allow traffic from specific IP ranges
Attach virtual network rules so that a subnet can reach the server privately
Update server configuration parameters such as max_connections without restart
Manage Azure Active Directory administrator on a MySQL server for AAD-based login
Retrieve performance tier definitions and check name availability before provisioning
Use Cases
Patterns agents use MySQLManagementClient API for, with concrete tasks.
★ Automated MySQL server provisioning
Platform teams provisioning per-environment MySQL servers from CI run a single workflow that checks name availability, picks the right performance tier, creates the server with a chosen SKU and storage size, then layers on databases and firewall rules. Provisioning a new general-purpose server typically completes in under 10 minutes, and the API returns a fully qualified hostname ready for the application to connect.
Create a MySQL server named orders-prod in resource group app-prod with SKU GP_Gen5_4, 100 GB storage, version 5.7, and admin login orders-admin.
Network access management for managed MySQL
Security teams limit MySQL server reachability by configuring firewall rules and virtual network rules through the API. Firewall rules allow specific IPv4 ranges; vnet rules permit specific Azure subnets to reach the server over service endpoints. Adding or removing rules is a control-plane operation that takes effect within seconds and does not require a server restart.
Add firewall rule office-corp allowing 203.0.113.10 to 203.0.113.50 on server orders-prod, and add a vnet rule attaching subnet app-subnet from vnet app-vnet.
Performance tuning via configuration updates
Database engineers tune Azure Database for MySQL server parameters such as innodb_buffer_pool_size, max_connections, and slow_query_log without redeploying the server. The configurations endpoint accepts a value update in place, and most parameters apply on the next session without downtime. Combined with reading server metrics through Azure Monitor, this allows iterative tuning loops driven entirely from code.
Update the max_connections parameter on server orders-prod to 600 by patching the configurations subresource and verify the new value via a follow-up GET.
Agent-driven Azure MySQL operations
AI agents can use Jentic to discover Microsoft.DBforMySQL operations by intent, load the structured input schema, and execute calls against management.azure.com without browsing the Azure REST docs. A platform agent that handles new database requests can stand up the server, create the application database, open the right firewall holes, and return the connection string from a single natural language request.
Search Jentic for create azure mysql server, load the input schema, and execute it for a Basic tier server with SKU B_Gen5_1 in westus2 and admin login appuser.
Key Endpoints
33 endpoints — jentic publishes the only available openapi specification for azure database for mysql management, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMySQL/servers/{serverName}
Create or update a managed MySQL server
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforMySQL/servers
List MySQL servers in a subscription
POST
/subscriptions/{subscriptionId}/providers/Microsoft.DBforMySQL/checkNameAvailability
Check MySQL server name availability
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMySQL/servers/{serverName}/Administrators/activeDirectory
Set the AAD administrator on a MySQL server
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforMySQL/locations/{locationName}/performanceTiers
List performance tiers in a region
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMySQL/servers/{serverName}
Create or update a managed MySQL server
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforMySQL/servers
List MySQL servers in a subscription
POST
/subscriptions/{subscriptionId}/providers/Microsoft.DBforMySQL/checkNameAvailability
Check MySQL server name availability
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMySQL/servers/{serverName}/Administrators/activeDirectory
Set the AAD administrator on a MySQL server
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforMySQL/locations/{locationName}/performanceTiers
List performance tiers in a region
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD OAuth credentials and service principals are stored encrypted in the Jentic vault. Agents receive scoped bearer tokens for management.azure.com at execution time; client secrets and certificates never enter the agent context.
Intent-based discovery
Agents search by intent (for example create azure mysql server or add azure mysql firewall rule) and Jentic returns the matching ARM operation with its full input schema, so the agent can call the correct path without browsing Microsoft Learn docs.
Time to first call
Direct integration with the Microsoft.DBforMySQL REST API: 2-3 days for AAD auth, long-running operation handling, and resource hierarchy modeling. Through Jentic: under 1 hour to search, load, and execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using MySQLManagementClient API through Jentic.
Why is there no official OpenAPI spec for MySQLManagementClient 2017-12-01-preview?
Microsoft Azure does not publish an OpenAPI specification for this preview slice of the Microsoft.DBforMySQL Resource Provider. Jentic generates and maintains this spec from the Azure Resource Manager contracts so that AI agents and developers can call MySQLManagementClient via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Azure Database for MySQL Management API use?
The API uses Azure Active Directory OAuth 2.0 with the user_impersonation scope against https://login.microsoftonline.com/common/oauth2/authorize. Jentic stores the AAD client secret or service principal credentials encrypted in its vault and supplies scoped bearer tokens to agents at execution time without exposing the underlying credential.
Can I create a database on a MySQL server through this API?
Yes. PUT under /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMySQL/servers/{serverName}/databases/{databaseName} creates or updates a database on a managed server. The body accepts charset and collation; once created, the database is reachable via the standard MySQL wire protocol on the server hostname.
What are the rate limits for the Azure Database for MySQL Management API?
The control plane follows the standard Azure Resource Manager throttling limits, which apply per subscription and per region. Read operations are limited to 1200 requests per hour per subscription. Server creation and SKU scale operations are long-running, so callers should poll the operation status endpoint rather than retry aggressively.
How do I add a firewall rule to a MySQL server through Jentic?
Search Jentic for create azure mysql firewall rule, load the schema for PUT under servers/{serverName}/firewallRules/{firewallRuleName}, and execute it with startIpAddress and endIpAddress. Jentic handles the AAD token exchange and returns the new rule resource.
Does this API connect to MySQL and run queries?
No. This is the control plane only; it provisions and configures servers and their network access but does not execute SQL. Once the server and its firewall or vnet rules are in place, applications connect using the standard MySQL wire protocol on the server hostname returned by the create call.
GET STARTED