Azure SQL Database cannot be deleted - stale Job Agent association

Question

Azure SQL Database cannot be deleted - stale Job Agent association

Hans-Christian Höpfl 0

Hello, I cannot delete an Azure SQL Database because Azure reports: CannotMoveOrDropJobAccountDatabase "The database confis001dev on server conservis01 is used by job account SQL Agent. Database cannot be deleted or renamed while associated with job account." Environment: Resource Group: Conservis SQL Server: conservis01 Database: confis001dev Region: West Europe Using the Azure REST API, I found the following Job Agent: Name: SQL Agent State: Ready SKU: JA100 The Job Agent has the following databaseId: /subscriptions/<subscription-id>/resourceGroups/Conservis/providers/Microsoft.Sql/servers/conservis01/databases/confis001dev However, the Job Agent appears to be in an inconsistent state. GET on the individual Job Agent returns ParentResourceNotFound. GET on: /jobAgents/SQL Agent/jobs also returns ParentResourceNotFound. DELETE on the Job Agent returns HTTP 204, but the Job Agent remains listed afterwards with state "Ready" and still references confis001dev. The database itself cannot be deleted. How can I remove this stale Job Agent association so that the database can be deleted? Thank you.

Kvns Krishna Teja 0 Reputation points Microsoft External Staff Moderator

2026-09-16T09:26:01.9266667+00:00

Hello @Hans-Christian Höpfl

Thank you for reaching out to Microsoft Q&A.

Could you kindly try the suggestion provided by @Deepesh Dhake and let us know if you still get any issues.

1 answer

Your answer

Kvns Krishna Teja 0 Reputation points Microsoft External Staff Moderator

2026-09-16T09:26:01.9266667+00:00

Hello @Hans-Christian Höpfl

Thank you for reaching out to Microsoft Q&A.

Could you kindly try the suggestion provided by @Deepesh Dhake and let us know if you still get any issues.

Answer 1

You can try these steps, in order

Wait and re-check: In the documented case, the agent was initially absent from the server and only appeared after ARM cache synchronization, after which the database deleted successfully. If this state is fresh, give it a few hours and re-GET the agent before doing anything else.
Verify with a clean, correctly formed call: Use the current API version and URL-encode the space in the agent name:

   az rest --method get \
--uri "https://management.azure.com/subscriptions/<sub>/resourceGroups/Conservis/providers/Microsoft.Sql/servers/conservis01/jobAgents/SQL%20Agent?api-version=2025-01-01"

A malformed path can itself produce ParentResourceNotFound, so rule that out first.

Check for resource locks on the RG, server, or database, a lock makes DELETE report success without acting:

   az lock list --resource-group Conservis