Microsoft Azure MariaDBManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth229 EndpointsREST
For Agents
Provision and operate Azure Database for MariaDB servers: create or scale servers, manage databases, configure firewall and VNet rules, and read log files. Useful for managed MariaDB lifecycle automation.
Use for: I need to provision a new Azure MariaDB server in West Europe, Scale a MariaDB server to a higher performance tier, Add a firewall rule allowing my office IP to reach a MariaDB server, List all databases on an Azure MariaDB server
Not supported: Does not run SQL queries, manage table schemas, or handle data plane operations — use for control-plane MariaDB server lifecycle and configuration only.
Jentic publishes the only available OpenAPI specification for MariaDBManagementClient, keeping it validated and agent-ready. Azure Database for MariaDB exposes a control-plane API for provisioning and operating fully managed MariaDB servers, including server lifecycle, databases, firewall rules, virtual network rules, log files, replicas, security alert policies, and configuration parameters. Use it to spin up a server in a chosen performance tier, configure access, and tune server parameters without managing the underlying VM. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
Install Jentic One Beta
Connect the MariaDBManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MariaDBManagementClient, 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 MariaDBManagementClient API.
Create or scale a managed MariaDB server in a chosen region and performance tier
Provision and drop logical databases inside an existing MariaDB server
Configure IP firewall rules and virtual network service endpoints to control server access
Read and update server configuration parameters such as max_connections and innodb_buffer_pool_size
List replicas and downloadable log files for an Azure Database for MariaDB server
Restart a MariaDB server through a single POST call without filing a support ticket
Manage server-level security alert policies for threat detection
Use Cases
Patterns agents use MariaDBManagementClient API for, with concrete tasks.
★ Provision a managed MariaDB server
Application teams use the API to provision Azure Database for MariaDB servers as part of an environment bootstrap. A single PUT call creates the server with the chosen SKU, storage, geo-redundant backup, and admin login, and Azure handles patching, replication, and backups. Follow-up calls add databases and firewall rules so the application can connect.
PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName} with SKU, storageProfile, and adminLogin; poll the async operation until provisioning completes.
Lock down server access
Security teams use the firewall rule and virtual network rule endpoints to ensure servers only accept connections from approved networks. Firewall rules whitelist single IPs or ranges, while VNet rules tie a server to specific subnets through service endpoints. Both are stored as named child resources of the server so they can be inventoried and removed cleanly.
List existing firewall rules with FirewallRules_ListByServer, then PUT each missing rule with the start and end IP for an approved range.
Tune server configuration
DBAs adjust MariaDB server parameters such as innodb_buffer_pool_size or wait_timeout to fit workload patterns. The configurations endpoints list every tunable setting along with its current value, allowed range, and source, and PUT updates a single setting. Some parameters are static and require a server restart, which the same API can trigger.
GET Configurations_ListByServer to find the parameter, PUT Configurations_CreateOrUpdate with the new value, then POST Servers_Restart if the parameter requires it.
Agent-driven database lifecycle
Through Jentic, an AI agent can read a deployment ticket and provision a complete MariaDB environment: server, database, firewall rule, and configuration overrides. The agent searches Jentic for 'create azure mariadb server', loads each operation in turn, and chains the calls. Jentic injects the Azure AD bearer token at execution time so the agent never handles secrets.
Use Jentic search 'create azure mariadb server', execute Servers_Create, then chain Databases_CreateOrUpdate and FirewallRules_CreateOrUpdate to complete environment setup.
Key Endpoints
29 endpoints — jentic publishes the only available openapi specification for mariadbmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}
Create a MariaDB server
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}
Update or scale a MariaDB server
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/databases/{databaseName}
Create a database on a server
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/firewallRules/{firewallRuleName}
Create a firewall rule
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/configurations/{configurationName}
Update a server configuration parameter
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/restart
Restart a MariaDB server
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/replicas
List replicas of a server
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}
Create a MariaDB server
PATCH
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}
Update or scale a MariaDB server
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/databases/{databaseName}
Create a database on a server
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/firewallRules/{firewallRuleName}
Create a firewall rule
PUT
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/configurations/{configurationName}
Update a server configuration parameter
POST
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/restart
Restart a MariaDB server
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/replicas
List replicas of a server
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Azure AD client credentials are stored encrypted in the Jentic vault. Jentic mints a short-lived ARM-scoped bearer token at execution time so the agent only ever sees structured request and response payloads.
Intent-based discovery
Agents search Jentic with intents like 'create azure mariadb server' and Jentic returns the matching Servers_Create operation with its full input schema, including SKU and storage options.
Time to first call
Direct integration: 3-5 days to handle MSAL, ARM async polling, the long-running operation pattern, and SKU validation. Through Jentic: under an hour.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using MariaDBManagementClient API through Jentic.
Why is there no official OpenAPI spec for MariaDBManagementClient?
Microsoft Azure does not publish a standalone OpenAPI specification for the MariaDB management resource provider. Jentic generates and maintains this spec so that AI agents and developers can call MariaDBManagementClient 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 MariaDB Management API use?
The API uses Azure Active Directory OAuth 2.0 via the azure_auth scheme on https://management.azure.com/. Through Jentic, your Azure AD client credentials are stored encrypted in the Jentic vault and exchanged for a short-lived bearer token at execution time.
Can I create databases on a MariaDB server through this API?
Yes. After the server exists, call PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/databases/{databaseName} with the desired charset and collation in the body. Use Databases_ListByServer to inventory existing databases first.
How do I add an IP firewall rule with this API?
Call PUT /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/firewallRules/{firewallRuleName} with startIpAddress and endIpAddress in the body. The rule applies immediately and is also visible to the Azure portal.
What are the rate limits for the MariaDB Management API?
The control-plane endpoints inherit standard Azure Resource Manager throttle quotas, surfaced through x-ms-ratelimit-remaining-* response headers. Long-running operations such as Servers_Create return 202 with an Azure-AsyncOperation URL the agent should poll rather than retry.
How do I provision a MariaDB server through Jentic?
Search Jentic for 'create azure mariadb server', load Servers_Create, supply the SKU, storageProfile, and administratorLogin in the body, and execute. Jentic surfaces the returned 202 status URL so your agent can poll for completion.
Can the API restart a MariaDB server?
Yes. POST /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforMariaDB/servers/{serverName}/restart triggers an asynchronous restart. Combine it with Configurations_CreateOrUpdate when changing static parameters that require a restart to take effect.
GET STARTED