Microsoft Azure MariaDBManagementClient

Name: MariaDBManagementClient API
Brand: MariaDBManagementClient
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth229 EndpointsREST

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with MariaDBManagementClient API

Explore with Jentic

View OpenAPI Document

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.

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}

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Azure AD client credentials are stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived ARM-scoped bearer token at execution time. The raw secret never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create an azure mariadb server' or 'add a firewall rule to a mariadb server', and Jentic returns the matching Servers or FirewallRules operation with its full input schema, including SKU and storage options, so the agent calls the right endpoint directly.

Time to first call

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 with Jentic One, the self-hosted execution layer.

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 your Jentic One instance 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.

Can I limit what my agent is allowed to do with the Microsoft Azure MariaDB Management API?

Yes. Jentic One runs self-hosted, so your own rules decide which operations and credentials the agent may use. Because the server name and its child names travel in the URL path, such as /servers/{serverName} and /servers/{serverName}/databases/{databaseName}, you can pin the agent to a single named MariaDB server. You also choose exactly which operations it may call, so destructive actions like Servers_Restart or Databases_Delete stay off limits unless you explicitly add them.

Microsoft Azure MariaDBManagementClient

Connect the MariaDBManagementClient to your agent

Capabilities

Start building with MariaDBManagementClient API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs