Microsoft Azure PostgreSQLManagementClient
Browse all Azure APIs★ Only Publicly Available OpenAPI DocumentStorageDatabaseoauth233 EndpointsREST
For Agents
Provision and manage Azure Database for PostgreSQL servers, databases, firewall and VNet rules, replicas, and server configuration through 33 ARM operations on Microsoft.DBforPostgreSQL.
Use for: I need to provision an Azure Database for PostgreSQL server in West Europe, Create a new database on an existing PostgreSQL server, Allow a specific IP range through the server firewall, Add a virtual network rule to restrict server access to a VNet subnet
Not supported: Does not run SQL queries, manage table schemas, or back up data - use for Microsoft.DBforPostgreSQL server and resource provisioning only.
Jentic publishes the only available OpenAPI specification for PostgreSQLManagementClient, keeping it validated and agent-ready. The Azure Database for PostgreSQL management API exposes 33 operations under Microsoft.DBforPostgreSQL for provisioning and managing managed PostgreSQL servers, databases, firewall rules, virtual network rules, replicas, configuration parameters, server administrators, and security alert policies. Use it to spin up a PostgreSQL server in a region, create databases, allow client IPs and VNets, configure server parameters, set up read replicas, and inspect log files at the server level.
Install Jentic One Beta
Connect the PostgreSQLManagementClient to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PostgreSQLManagementClient, 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-postgresql-management" | sh2
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-postgresql-management" | 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 PostgreSQLManagementClient API.
Provision Azure Database for PostgreSQL servers with chosen SKU, storage size, and region
Create databases, configure server parameters, and apply firewall and virtual network rules
Set up read replicas to scale read traffic and provide regional failover
Manage Active Directory administrators on a server for AAD-based authentication
Configure server-level security alert policies for threat detection and notification
List performance tier options and check name availability before placing an order
Restart a server and retrieve log files for performance and incident investigation
Use Cases
Patterns agents use PostgreSQLManagementClient API for, with concrete tasks.
★ Managed PostgreSQL Provisioning
Provision a managed PostgreSQL server for a new application. The flow is: check name availability, list performance tiers, create the server with the chosen SKU and storage size, add firewall rules for application IPs, configure VNet rules for private connectivity, create application-specific databases, and tune key server parameters. The 33 endpoints cover the full provisioning surface so the entire setup completes in a single playbook.
Check availability of name 'app-prod-pg', create a GP_Gen5_2 server in westeurope with 100 GB storage, add a firewall rule for the office IP range, and create database 'app'
Read Replica Scaling
Scale read-heavy workloads by creating PostgreSQL read replicas in the same or another region. Listing replicas under a server returns the full replica topology and their replication state. The replica sits behind its own connection string so the application can route SELECT traffic away from the primary, while writes continue to land on the primary. Cross-region replicas double as warm standby for regional failover.
Create a read replica of server 'app-prod-pg' named 'app-prod-pg-replica1' in northeurope, then list replicas and confirm the replication state
Network Hardening
Lock down PostgreSQL server access to specific IPs and virtual networks. Firewall rules control public IP access at the server level and virtual network rules restrict access to specific subnets in an Azure VNet. An audit query lists every firewall and VNet rule across every PostgreSQL server in the subscription, surfacing rules that are too broad (0.0.0.0/0) or no longer needed.
List firewall rules and virtual network rules on every PostgreSQL server in the subscription, flag rules with start IP 0.0.0.0, and remove flagged rules after operator confirmation
AI Agent Database Operator
An AI agent supporting a platform team can provision and manage PostgreSQL servers through Jentic. The agent searches by intent ('create an azure postgresql server'), Jentic returns the Servers_Create operation with its schema, and the agent executes the call with managed Azure credentials. Replica setup, firewall rule changes, and parameter tuning follow the same intent-driven flow.
Search Jentic for 'create an Azure PostgreSQL server', load the Servers_Create schema, and execute it with the supplied SKU, storage, and region
Key Endpoints
33 endpoints — jentic publishes the only available openapi specification for postgresqlmanagementclient, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/subscriptions/{subscriptionId}/providers/Microsoft.DBforPostgreSQL/checkNameAvailability
Check whether a server name is available
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforPostgreSQL/servers
List PostgreSQL servers in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforPostgreSQL/servers
List servers in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforPostgreSQL/servers/{serverName}
Get a specific PostgreSQL server
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforPostgreSQL/servers/{serverName}/Replicas
List read replicas of a server
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforPostgreSQL/locations/{locationName}/performanceTiers
List performance tiers available in a region
GET
/providers/Microsoft.DBforPostgreSQL/operations
List Microsoft.DBforPostgreSQL operations
POST
/subscriptions/{subscriptionId}/providers/Microsoft.DBforPostgreSQL/checkNameAvailability
Check whether a server name is available
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforPostgreSQL/servers
List PostgreSQL servers in a subscription
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforPostgreSQL/servers
List servers in a resource group
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforPostgreSQL/servers/{serverName}
Get a specific PostgreSQL server
GET
/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforPostgreSQL/servers/{serverName}/Replicas
List read replicas of a server
GET
/subscriptions/{subscriptionId}/providers/Microsoft.DBforPostgreSQL/locations/{locationName}/performanceTiers
List performance tiers available in a region
GET
/providers/Microsoft.DBforPostgreSQL/operations
List Microsoft.DBforPostgreSQL operations
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PostgreSQLManagementClient by hand means acquiring an Azure AD token from login.microsoftonline.com, routing every request to management.azure.com with the right preview api-version, and threading server provisioning, replicas, and performance tiers across the Microsoft.DBforPostgreSQL namespace yourself. Through Jentic you install once, import PostgreSQLManagementClient from the API Directory, store the Azure AD credential once, and your agent calls it.
Permission scoping
This API puts the subscription id, resource group, and server name in the URL path (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DBforPostgreSQL/servers/{serverName}), so a rule can pin your agent to one server in one resource group. You choose the operations it may call, so deleting a server or a firewall rule is not included unless you add them, letting the agent list servers and read replicas.
Credential isolation
Your Azure AD credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an Azure PostgreSQL server' or 'add a PostgreSQL firewall rule', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without learning the Microsoft.DBforPostgreSQL namespace.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PostgreSQLManagementClient API through Jentic.
Why is there no official OpenAPI spec for PostgreSQLManagementClient?
Microsoft Azure does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call PostgreSQLManagementClient 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 Azure PostgreSQL management API use?
It uses Azure Active Directory OAuth 2.0 against https://management.azure.com/ with the user_impersonation scope. The caller needs Contributor or a custom role with Microsoft.DBforPostgreSQL/* permissions on the resource group. Jentic stores service principal credentials encrypted and issues short-lived bearer tokens at execution time.
Can I provision a PostgreSQL server through this API?
Yes. PUT to /subscriptions/{id}/resourceGroups/{rg}/providers/Microsoft.DBforPostgreSQL/servers/{name} with the SKU, storage size, version, administrator login, and password in the request body. Server provisioning is a long-running operation that returns 202 Accepted with an Azure-AsyncOperation header you poll until the server reports Ready.
What are the rate limits for the PostgreSQL management API?
Azure Resource Manager applies subscription-level throttling at roughly 1,200 reads and 1,200 writes per hour. Server provisioning typically takes several minutes so async polling, not retry storms, is the right pattern.
How do I create a PostgreSQL read replica through Jentic?
Run pip install jentic and search for 'create an azure postgresql replica'. Jentic returns the Servers_Create operation with createMode set to Replica; load its schema and execute it with the source server resource ID in the properties.sourceServerId field.
Does this API run SQL queries against the database?
No. This is the management API for provisioning and configuring servers. Application SQL traffic uses the standard PostgreSQL wire protocol against {server}.postgres.database.azure.com on port 5432, typically through psycopg, libpq, or any standard PostgreSQL client.
Can I limit what my agent is allowed to do with the Azure PostgreSQL Management API?
Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. This API carries the subscription ID, resource group, and server name in the URL path, so you can pin the agent to a single server in one resource group and let it only list servers and read replica state. Destructive calls like deleting a server or a firewall rule are excluded unless you explicitly add them, and your Azure AD credential is injected at execution time rather than exposed to the agent.
GET STARTED