Azure Database for PostgreSQL

Create a PostgreSQL flexible server and a database on it through the local management API, run SQL on the database with psql over TLS, then delete them.

Plan: Pro74 of 74 operations implemented across its API3Known differences

Servers share one local engine, which answered as PostgreSQL 15.19 despite version 16; tiers, regions, high availability, backups and migrations are metadata only.

Example checked on Vera 1.2.2, 8 November 2026. Each coverage note names its own evidence and date.

Connect

Start Vera as in Get started, with your license key activated and the emulator started by the Vera launcher (Activate Pro). Then open Bash in a terminal of its own (on macOS, whose terminal starts zsh, type bash first), go to an empty scratch directory and run this; it needs curl and Python 3, and jq. It fetches the emulator's own certificate, so every request checks TLS, and defines data_request and data_arm, which this page's commands use. The bearer token vera-local is a dummy local credential, not your license key.

export VERA_CA_CERT="$PWD/vera-ca.pem"
curl --fail --silent --show-error --noproxy '*' --insecure \
  https://localhost:8543/_vera/ca.pem --output "$VERA_CA_CERT"
curl --fail --silent --show-error --noproxy '*' \
  --cacert "$VERA_CA_CERT" https://localhost:8543/_vera/health; echo

export VERA_CA="$VERA_CA_CERT"
export ARM='https://localhost:8543'
export SUB='00000000-0000-0000-0000-000000000001'
export TENANT='00000000-0000-0000-0000-0000000000a1'
export RG='azdata-rg'
export ROOT="/subscriptions/$SUB/resourceGroups/$RG"
export AUDIT_TMP="$(mktemp -d)"

56 more lines: show the full setup
# Every .localhost host name is connected to loopback, and TLS is verified.
# DATA_RESPONSE is replaced after each call: copy any IDs before the next one.
data_request() {
  local method="$1" url="$2" host status
  shift 2
  case "$url" in
    https://localhost:8543/*|https://*.localhost:8543/*) ;;
    *) printf 'Refusing non-local URL: %s\n' "$url" >&2; return 1 ;;
  esac
  host="${url#https://}"
  host="${host%%/*}"
  host="${host%:8543}"
  status=$(curl --noproxy '*' --silent --show-error \
    --cacert "$VERA_CA" --resolve "$host:8543:127.0.0.1" \
    -H 'Authorization: Bearer vera-local' \
    -X "$method" "$url" "$@" \
    -D "$AUDIT_TMP/headers" -o "$AUDIT_TMP/body" -w '%{http_code}') || return
  DATA_RESPONSE=$(cat "$AUDIT_TMP/body")
  printf 'HTTP %s\n%s\n' "$status" "$DATA_RESPONSE"
  case "$status" in 2??) ;; *) return 1 ;; esac
}

# Polls the operation URL from the last successful management change, even
# after HTTP 200 or 201. Don't replace it with a fixed sleep.
data_wait_arm() {
  local operation attempt status state delay
  operation=$(awk 'BEGIN {IGNORECASE=1} tolower($1)=="azure-asyncoperation:" {gsub("\r", "", $2); print $2; exit}' "$AUDIT_TMP/headers")
  if [ -z "$operation" ]; then
    operation=$(awk 'tolower($1)=="location:" {gsub("\r", "", $2); print $2; exit}' "$AUDIT_TMP/headers")
  fi
  [ -z "$operation" ] && return 0
  case "$operation" in "$ARM"/_vera/operations/*) ;; *) printf 'Inspect unexpected operation URL: %s\n' "$operation" >&2; return 1 ;; esac
  for attempt in $(seq 1 60); do
    data_request GET "$operation" || return
    status=$(awk '/^HTTP\// {code=$2} END {print code}' "$AUDIT_TMP/headers")
    state=$(printf '%s' "$DATA_RESPONSE" | jq -r '.status // empty' 2>/dev/null) || state=''
    case "$state" in
      Failed|Canceled|Cancelled) return 1 ;;
      Succeeded) return 0 ;;
      InProgress|Running|Accepted) ;;
      *) [ "$status" != '202' ] && return 0 ;;
    esac
    delay=$(awk 'tolower($1)=="retry-after:" {gsub("\r", "", $2); print $2; exit}' "$AUDIT_TMP/headers")
    case "$delay" in ''|*[!0-9]*) delay=1 ;; esac
    sleep "$delay"
  done
  printf 'Operation did not finish within the polling limit\n' >&2
  return 1
}

data_arm() {
  local method="$1" path="$2"
  shift 2
  data_request "$method" "$ARM$path" "$@" || return
  case "$method" in PUT|PATCH|POST|DELETE) data_wait_arm ;; esac
}

The health check answers {"cloud": "azure", "generation_status": "generated", "status": "ok"}. Requests go only to the emulator at https://localhost:8543: the helper refuses any other address, including the Azure-looking URLs some responses hold. When you've finished, close the terminal and delete the scratch directory; that removes only these local files, not what you created in the emulator.

Create flexible servers and databases through Resource Manager, then run SQL on the local PostgreSQL engine over TLS. The examples use the PostgreSQL flexible server management API at 2026-10-01 and resource groups at 2025-04-01, the versions tested with this build: keep them as shown. Management requests go to https://localhost:8543. SQL goes to the local engine at localhost, port 15432, which the Vera launcher publishes, and needs psql, the PostgreSQL client. TLS is checked against the emulator’s certificate, which the setup above saves as $VERA_CA_CERT. The server’s host name, azdatapg.postgres.localhost, is a value on its record: the example doesn’t connect to it.

Example

Create a flexible server and a database on it, read both back, run SQL on the database, then delete them. The administrator password is a dummy for this example: don’t use a real one.

Create the resource group the examples share, then the server, and read the server. Creating the server answers HTTP 202, and data_arm prints each response, then polls the operation until it has succeeded (long-running operations):

data_arm PUT "$ROOT?api-version=2025-04-01" \
  -H 'Content-Type: application/json' --data '{"location":"eastus"}'
PG="$ROOT/providers/Microsoft.DBforPostgreSQL/flexibleServers/azdatapg"
data_arm PUT "$PG?api-version=2026-10-01" -H 'Content-Type: application/json' \
  --data '{"location":"eastus","sku":{"name":"Standard_B1ms","tier":"Burstable"},"properties":{"administratorLogin":"veradocs","administratorLoginPassword":"VeraDocsOnly!2026","version":"16","storage":{"storageSizeGB":32}}}'
data_arm GET "$PG?api-version=2026-10-01"

The GET answers HTTP 200 with the server. These are selected fields:

{
  "name": "azdatapg",
  "properties": {
    "fullyQualifiedDomainName": "azdatapg.postgres.localhost"
  }
}

Create a database with a UTF8 charset and read it:

data_arm PUT "$PG/databases/azdatadb?api-version=2026-10-01" \
  -H 'Content-Type: application/json' \
  --data '{"properties":{"charset":"UTF8","collation":"en_US.utf8"}}'
data_arm GET "$PG/databases/azdatadb?api-version=2026-10-01"

The create answers HTTP 202, and the helper waits for its operation. The GET answers HTTP 200 with the charset and collation as created; these are selected fields:

{
  "name": "azdatadb",
  "properties": {
    "charset": "UTF8",
    "collation": "en_US.utf8"
  }
}

Now run SQL on the database with psql. It signs in as the server’s administrator, with the example’s dummy password, and verify-full checks the engine’s certificate against $VERA_CA_CERT:

PGPASSWORD='VeraDocsOnly!2026' PGSSLMODE=verify-full PGSSLROOTCERT="$VERA_CA_CERT" \
  psql -X -v ON_ERROR_STOP=1 -h localhost -p 15432 -U veradocs -d azdatadb \
  -c "CREATE TABLE vera_docs_probe (message text); INSERT INTO vera_docs_probe VALUES ('hello'); SELECT message FROM vera_docs_probe;"

It creates the table vera_docs_probe, inserts one row and returns hello from the SELECT. The engine that answered was PostgreSQL 15.19, although the server was created with version 16: that field doesn’t select the engine. Deleting the database below removes the table with it.

To clean up, delete the database, then the server:

data_arm DELETE "$PG/databases/azdatadb?api-version=2026-10-01"
data_arm DELETE "$PG?api-version=2026-10-01"

Each delete answers HTTP 202, and its operation then answers HTTP 204. A GET of the server then answers HTTP 404. The resource group azdata-rg stays, since deleting a group fails in Vera 1.2.2: see deleting resource groups. Other pages’ examples reuse it. To remove it and anything else left over, start a fresh emulator: see Stop and start again.

Supported features

Flexible servers: a Standard_B1ms Burstable server with version 16 and 32 GB of storage, created, read back with a fullyQualifiedDomainName under postgres.localhost, listed in its resource group and deleted. A missing server answers HTTP 404.
Databases: a database created with a charset and collation, read back with both, and deleted.
SQL over TLS: on Vera 1.2.2, psql connected to localhost:15432 with verify-full as the server’s administrator, created a table in the database, inserted a row and read it back. PostgreSQL 15.19 answered.
Long-running operations: each create and delete returned an operation that the helper polled until it finished.
Not run as examples: firewall rules, server configuration parameters, Microsoft Entra administrators, backups, replicas, virtual endpoints, migrations, starting, stopping and restarting a server, and the rest of the management API. The API coverage marks these from a review of Vera 1.2.0’s source, with their limits in the notes.

Limitations

The main limits are below. A few more apply to every service, and the API coverage notes cover smaller differences.

Servers share one engine. From a review of the source, every flexible server is served by the same local PostgreSQL engine, on port 15432. A second server isn’t a separate PostgreSQL instance, so don’t rely on servers to keep data apart: isolation between them isn’t established.
Only the example’s SQL was run. On Vera 1.2.2, psql created a table, inserted a row and read it back over TLS. Transactions, extensions and other PostgreSQL features weren’t tested.
The version, tier, region and high availability are stored values. The ARM version: "16" field doesn’t select the engine: on Vera 1.2.2, PostgreSQL 15.19 answered. A server’s SKU tier, region and high-availability settings are kept on its record and don’t change the shared engine. azdatapg.postgres.localhost isn’t an address a client was shown to reach: connect to localhost on port 15432.
Backups and migrations are metadata. A server backup captures the server’s resource metadata, not PostgreSQL data. BackupsLongTermRetention_Start creates a metadata-only manifest and doesn’t stream the database’s bytes to the destination you give. A migration (Migrations_Create, Migrations_Update) can’t inspect an external source: its validation fails, and no remote database is copied.
Capabilities and quotas are local. Capability, quota and maintenance responses come from the emulator’s local policies, not from Azure’s inventory.

API coverage

Every operation of the API on this page, from its pinned public definition, and whether Vera 1.2.0 implements it. Only the API surfaces in this release are listed, and each operation once. Implementation availability was reviewed against the Vera 1.2.0 source on 6 November 2026. Source inspection identifies a local implementation and its known limits; it doesn't mean every operation or API version was tested with a request. Each note names its evidence: a Local observation without a build or date is from Vera 1.2.0 preview, on 5 November 2026, and one from a later build, such as Vera 1.2.0-rc.3 or Vera 1.2.2, names that build and its date. No response was compared with Azure's. What the statuses mean

AdministratorsMicrosoftEntra

4 of 4 implemented

Operation	Status	Notes
AdministratorsMicrosoftEntra_CreateOrUpdate	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
AdministratorsMicrosoftEntra_Delete	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
AdministratorsMicrosoftEntra_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
AdministratorsMicrosoftEntra_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

AdvancedThreatProtectionSettings

2 of 2 implemented

Operation	Status	Notes
AdvancedThreatProtectionSettings_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
AdvancedThreatProtectionSettings_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

BackupsAutomaticAndOnDemand

4 of 4 implemented

Operation	Status	Notes
BackupsAutomaticAndOnDemand_Create	Implemented	Source inspection: Creates, reads, lists and deletes backup records; a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
BackupsAutomaticAndOnDemand_Delete	Implemented	Source inspection: Creates, reads, lists and deletes backup records; a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
BackupsAutomaticAndOnDemand_Get	Implemented	Source inspection: Creates, reads, lists and deletes backup records; a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
BackupsAutomaticAndOnDemand_ListByServer	Implemented	Source inspection: Creates, reads, lists and deletes backup records; a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

BackupsLongTermRetention

4 of 4 implemented · 1 known difference

Operation	Status	Notes
BackupsLongTermRetention_CheckPrerequisites	Implemented	Source inspection: Checks and reads long-term retention backup records; a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
BackupsLongTermRetention_Get	Implemented	Source inspection: Checks and reads long-term retention backup records; a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
BackupsLongTermRetention_ListByServer	Implemented	Source inspection: Checks and reads long-term retention backup records; a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
BackupsLongTermRetention_Start	Known difference	Source inspection: Creates a metadata-only manifest; it doesn't stream the database's disk bytes to the supplied destination, and a server backup captures resource metadata, not PostgreSQL data. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

CapabilitiesByLocation

1 of 1 implemented

Operation	Status	Notes
CapabilitiesByLocation_List	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

CapabilitiesByServer

1 of 1 implemented

Operation	Status	Notes
CapabilitiesByServer_List	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

CapturedLogs

1 of 1 implemented

Operation	Status	Notes
CapturedLogs_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

Configurations

4 of 4 implemented

Operation	Status	Notes
Configurations_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Configurations_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Configurations_Put	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Configurations_Update	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

Databases

4 of 4 implemented

Operation	Status	Notes
Databases_Create	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — `psql` signed in to the created database, `azdatadb`, as the server's administrator over TLS at `localhost:15432`, created a table, inserted a row and read back `hello`. Earlier, in Vera 1.2.0 preview, the create answered HTTP 202 for a database with charset `UTF8` and collation `en_US.utf8`, and its operation reached `Succeeded`.
Databases_Delete	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — the example's cleanup deleted the database, and the table `psql` had created in it, through Resource Manager. Earlier, in Vera 1.2.0 preview, the delete answered HTTP 202, and its operation answered HTTP 204.
Databases_Get	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — returned the example's database with the charset and collation it was created with (HTTP 200), and `psql` then reached that database at `localhost:15432`. Earlier, in Vera 1.2.0 preview, the read returned the same fields.
Databases_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

FirewallRules

4 of 4 implemented

Operation	Status	Notes
FirewallRules_CreateOrUpdate	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
FirewallRules_Delete	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
FirewallRules_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
FirewallRules_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

MaintenanceEvents

4 of 4 implemented

Operation	Status	Notes
MaintenanceEvents_ApplyNow	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
MaintenanceEvents_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
MaintenanceEvents_List	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
MaintenanceEvents_Reschedule	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

MajorVersionUpgradePrecheck

2 of 2 implemented

Operation	Status	Notes
MajorVersionUpgradePrecheck_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
MajorVersionUpgradePrecheck_List	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

Migrations

6 of 6 implemented · 2 known differences

Operation	Status	Notes
Migrations_Cancel	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Migrations_CheckNameAvailability	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Migrations_Create	Known difference	Source inspection: Validates the migration against source state held locally. An external source fails validation, and no remote database is copied. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Migrations_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Migrations_ListByTargetServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Migrations_Update	Known difference	Source inspection: Validates the migration against source state held locally. An external source fails validation, and no remote database is copied. Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

NameAvailability

2 of 2 implemented

Operation	Status	Notes
NameAvailability_CheckGlobally	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
NameAvailability_CheckWithLocation	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

Operations

1 of 1 implemented

Operation	Status	Notes
Operations_List	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

PrivateDnsZoneSuffix

1 of 1 implemented

Operation	Status	Notes
PrivateDnsZoneSuffix_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

PrivateEndpointConnections

4 of 4 implemented

Operation	Status	Notes
PrivateEndpointConnections_Delete	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
PrivateEndpointConnections_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
PrivateEndpointConnections_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
PrivateEndpointConnections_Update	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

PrivateLinkResources

2 of 2 implemented

Operation	Status	Notes
PrivateLinkResources_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
PrivateLinkResources_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

QuotaUsages

1 of 1 implemented

Operation	Status	Notes
QuotaUsages_List	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

Replicas

1 of 1 implemented

Operation	Status	Notes
Replicas_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

ServerThreatProtectionSettings

1 of 1 implemented

Operation	Status	Notes
ServerThreatProtectionSettings_CreateOrUpdate	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

Servers

11 of 11 implemented

Operation	Status	Notes
Servers_CreateOrUpdate	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — after the example created the server with version `16`, `psql` ran SQL on its database over TLS at `localhost:15432`, and PostgreSQL 15.19 answered: `version` doesn't select the engine. Earlier, in Vera 1.2.0 preview, the create answered HTTP 202 for a `Standard_B1ms` server, and its operation reached `Succeeded`.
Servers_Delete	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — the example's cleanup deleted the server after its database had served SQL through `psql`. Earlier, in Vera 1.2.0 preview, the delete answered HTTP 202, its operation answered HTTP 204, and a GET then answered HTTP 404.
Servers_Get	Implemented	Local observation: Vera 1.2.2, 8 November 2026 — returned the example's server with `fullyQualifiedDomainName` `azdatapg.postgres.localhost` (HTTP 200). SQL went to `localhost:15432`, not to that name. Earlier, in Vera 1.2.0 preview, the server was returned before and after its create operation had finished, and a missing server, and the server after deletion, answered HTTP 404.
Servers_ListByResourceGroup	Implemented	Local observation: Listed the resource group's servers (HTTP 200).
Servers_ListBySubscription	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Servers_MigrateNetworkMode	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Servers_Restart	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Servers_Start	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Servers_StartMajorVersionUpgradePrecheck	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Servers_Stop	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
Servers_Update	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

TuningOptions

3 of 3 implemented

Operation	Status	Notes
TuningOptions_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
TuningOptions_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
TuningOptions_ListRecommendations	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

VirtualEndpoints

5 of 5 implemented

Operation	Status	Notes
VirtualEndpoints_Create	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
VirtualEndpoints_Delete	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
VirtualEndpoints_Get	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
VirtualEndpoints_ListByServer	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.
VirtualEndpoints_Update	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.

VirtualNetworkSubnetUsage

1 of 1 implemented

Operation	Status	Notes
VirtualNetworkSubnetUsage_List	Implemented	Source inspection: Local flexible-server management; backup, restore and migration work on metadata, with no PostgreSQL data transfer established.