An Azure relational database service.
There is no documented self-service command to force-release an Azure SQL logical-server hostname without restoring the deleted server; first determine whether klevio is soft-deleted, then wait for its retention period—or, if it is not retained, for the asynchronous backend cleanup.
1. Check whether the server is soft-deleted
Azure SQL logical-server soft delete is currently in preview. When enabled, retention is 1–7 days; logical servers older than two years automatically receive seven-day retention, while newer servers have it disabled by default. A retained server is not permanently removed until that period expires.^1^
Using Azure CLI 2.84.0 or later:
az sql server deleted-server show \
--name klevio \
--location westus2
# Alternatively, list all retained servers in the old region:
az sql server deleted-server list \
--location westus2 \
--output table
Interpret the result as follows:
-
kleviois returned: it remains in its configured soft-delete window. Since recovery is not wanted, leave it deleted and wait for retention to expire. - It is not returned: the server was permanently deleted, but its hostname/DNS cleanup has not completed. Microsoft publishes no guaranteed release interval for this post-deletion state, so retry name availability and alias creation with backoff.
The test completing in six seconds does not establish a normal release time because the test servers might not have had soft-delete retention enabled.
2. Do not treat the two-minute alias delay as the server-name release time
Azure SQL DNS alias names are globally unique across servers, just like logical-server names. Dropping a server also drops aliases that refer to it.^2^
The documented up-to-two-minute delay applies when an existing DNS alias is updated or removed. It does not specify how quickly the hostname of a deleted logical server becomes reusable. Therefore, the remaining CNAME and checkNameAvailability: AlreadyExists indicate that Azure still considers klevio reserved; repeatedly deleting an alias from the new server will not release it.
3. Available remediation paths
Because you do not want to restore the deleted server:
- If it appears in
deleted-server show, wait until its retention expires. - If it does not appear, retry periodically rather than relying only on DNS resolution. DNS results can remain cached, while
checkNameAvailabilitydirectly reflects whether Azure permits reuse. - In Azure portal → Help + support → Create a support request, select Azure SQL Database and the server creation/deletion or provisioning category. Include:
- deletion timestamp;
- old region (
westus2); - new region (
swedencentral); -
ServerDnsAliasDnsRecordInUse; - the
checkNameAvailabilityresponse; - current CNAME result;
- confirmation that the server is absent from the deleted-server list.
Manual investigation or release is a technical-support operation. Standard Azure technical support requires a support plan; free subscription-management support covers billing, quota adjustments, and account transfers, not this provisioning problem.^3^ If your subscription has no technical plan, use an existing organization-wide, Enterprise Agreement, CSP, or partner support entitlement if available. There is no documented free purge/release endpoint for this Azure SQL condition.
Azure does document an early-purge procedure—restore the server, set retention to 0, and delete it again—but that necessarily recovers the server temporarily, so it conflicts with your stated requirement and is not the recommended path here.^1^
References