Databases
Managed role changes
Rotate or revoke one managed database role without changing other profiles.
POST
Managed role changes
This capability is in preview and requires activation for your database. An
unavailable target is refused before a new operation is created.
owner (including migration access), runtime
and readonly. Internal Explorer access is not a public profile.
Create an operation
Send a stableIdempotency-Key header and this exact JSON body:
kind: "revoke" to disable that login. Revoke preserves grants and data;
rotation does not reactivate a revoked profile. Do not send a password, physical
role name, database name, connection string or internal Explorer profile.
The response is 202 while pending or 201 when completed, with a Location
header pointing to the operation. It contains no credentials:
Read or reconcile
GET /api/v1/databases/{id}/role-changes/{operationId} returns 200 with operation
metadata. It performs no native mutation or reconciliation.
To reconcile an uncertain outcome, send POST to that same operation URL with
exactly {"confirmDisconnect": true}. The server reuses the recorded input and
returns 202 pending or 200 completed. An already completed replay performs no
native operation. Completed remote work can be finalized while new mutations are
disabled; unfinished native work waits for mutation availability and an active database.
Stopped databases retain metadata and completed replay; they cannot reserve a new
role change or dispatch a native credential mutation.
Errors
All responses use
Cache-Control: no-store. An unresolved operation prevents
owner reassignment until verified completion.