Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Storage / Azure / MariaDBManagementClient
MariaDBManagementClient logo

Microsoft Azure MariaDBManagementClient

Browse all Azure APIs
43
AI ReadinessFoundational (D)43/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticStorageDatabaseoauth229 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-mariadbmanagementclient" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fazure.com%2Fazure-mariadbmanagementclient" | 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

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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

M

MariaDBManagementClient

- Foundational (D)
43/100
64
Foundational Compliance
58
Developer Experience & Jentic Compatibility
22
AI-Readiness & Agent Experience
94
Agent Usability
35
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
64

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4
83%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

58

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

31%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

22

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
87%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

35

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
35%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Azure Database for MariaDB by hand means setting up MSAL and an Azure AD service principal, minting bearer tokens against management.azure.com, validating SKU shapes, and polling the Azure-AsyncOperation URL that server creates and restarts return. Through Jentic you install once, import MariaDBManagementClient from the API Directory, store the service principal credentials once, and your agent calls it.

Permission scoping

The server name and its child names travel in the URL path (/servers/{serverName}, /servers/{serverName}/databases/{databaseName}, /firewallRules/{firewallRuleName}), so a rule can pin your agent to a named server. You choose the operations it may call, so restarting a server or deleting a database is not included unless you add it.

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.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

MySQL Management Client

→

Provision and operate Azure Database for MySQL servers - same shape, different engine.

Pick MySQL when the application requires MySQL-specific features; pick MariaDB for MariaDB-only extensions.

Alternative

PostgreSQL Management Client

→

Managed PostgreSQL on Azure with a parallel API surface.

Choose PostgreSQL when the workload needs PostgreSQL features such as JSONB or PostGIS.

Alternative

SQL Management Client

→

Provision Azure SQL Database, the SQL Server-based managed offering.

Pick SQL Management when the workload requires SQL Server compatibility, transaction features, or Hyperscale.

Complementary

Resource Management Client

→

Manage resource groups that contain MariaDB servers.

Use Resource Management to provision the resource group before creating MariaDB servers inside it.

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.

GET STARTED

Start building with MariaDBManagementClient API

Explore with Jentic One
View OpenAPI Document