Azure-docs: Hard delete does not work

[Mobrockers]

We have been trying to do a hard delete of a workspace to create a new one with that name in another resource group. This still results in a 409 conflict.

Situation:
resource group log-analytics-a
resource group log-analytics-b
log analytics log-analytics-to-recreate

Use DELETE on API to delete log-analytics-to-recreate in resource group log-analytics-a

Use az CLI to create new log analytics with name log-analytics-to-recreate in resource group log-analytics-b

Response is 409 Conflict. Try again half an hour later, result is 409 conflict.

Can anyone confirm the hard-delete is actually supposed to release the name to be re-used in another resource group?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 86984751-da7f-c77b-c78b-a9c9ffacb4a3
• Version Independent ID: 57838082-5ee8-097c-9814-803a5077ba4e
• Content: Delete and recover Azure Log Analytics workspace - Azure Monitor
• Content Source: articles/azure-monitor/platform/delete-workspace.md
• Service: azure-monitor
• Sub-service: logs
• GitHub Login: @bwren
• Microsoft Alias: bwren

[BharathNimmala-MSFT]

@Mobrockers Thank you for query, we will further look into it and get back to you at the earliest.

[BharathNimmala-MSFT]

@Mobrockers Apologies for delay on this, we have reached out to our internal team to further understand this behavior. Will keep you updated as we hear more on this.

[BharathNimmala-MSFT]

@Mobrockers Further validation of the documentation helped me to realize that we should be using the force tag so just making sure you are using the force tag as part of the Delete REST API call when doing the permanent delete. It is documented as below

With the force tage was able to succesfully do a permanent delete and recreate the same workspace name in another resource group.

So requesting you to please try that option and circle back if you still see any further issues. Thank you

[Mobrockers]

We are using the force delete flag.

Upon further investigation it appears that in our scripting we were performing a soft-delete first via deleting the containing resource group and then performing a hard-delete via the deletion API.

It appears that the force deletion is accepted when the log analytics workspace is in soft-deletion state but is not actually performed.

It might be useful to add to the docs that a hard deletion only works on a running state log analytics and does not work on a log analytics workspace that was already soft deleted.

[BharathNimmala-MSFT]

@Mobrockers That should be expected behavior where we are trying to redo the same activity of delete with additional force flag. It would return 204 status code. Will request to see the possibility to reverse the order in your script where you perform the hard-delete via the deletion API first with force flag and then delete the containing resource group. (or) also see the feasibility of using dependson flag with in your script.

At this point it appears that there's no direct edits needed to the documentation. We will certainly take your feedback back to our document author to evaluate any further document enhancement is needed or not. Thank you for sharing it.

We will go ahead and close this issue, however if you have any further queries please tag us in your reply and will be happy to reopen the thread and continue the conversation. Thank you

[Mobrockers]

Yes we have reversed the order. Was just suggesting that it might be useful to add to the docs that you cannot make a soft delete permanent by following with a hard delete. Thank you for your help.