The workspace was successfully unlinked. from an automation account, but on a refresh it is still there

Hi Robert Smit

You are correct — it typically takes around 48 hours for the status to update correctly.

In the meantime, could you please try one more time using the Azure CLI?

You can use the following command:

az monitor log-analytics workspace linked-service show -g MyResourceGroup -n automation --workspace-name MyWorkspace

Please make sure to replace MyResourceGroup with the resource group of the workspace, and MyWorkspace with the actual workspace name. The rest of the command remains unchanged https://learn.microsoft.com/en-us/cli/azure/monitor/log-analytics/workspace/linked-service?view=azure-cli-latest#az-monitor-log-analytics-workspace-linked-service-show-examples If you receive a response and the provisioningState shows Succeeded, it means the unlinking is still being processed in the backend.

If no response is returned, it indicates the unlinking has been completed, and the status will update in the Azure portal within approximately 48 hours.

Let me know how it goes!  

let us know if you have any further queries. I’m happy to assist you further.

If the comment is helpful, please click "Upvote it".

Hi,

It's already longer than 48 hours,
az monitor log-analytics workspace linked-service show -g "rg-azurehcibox" -n automation --workspace-name "HCIBox-Workspace" (tested it with and without "")

Operation returned an invalid status 'Not Found'
list my Workspaces then it is still there

What I think is that the sync between the portal and the back interface is gone, Saw this before. sometimes with a set or tag change it can be fixed but not this time.

az monitor log-analytics workspace list

"id": "/subscriptions/df34/resourceGroups/rg-azurehcibox/providers/Microsoft.OperationalInsights/workspaces/HCIBox-Workspace",

"location": "westeurope",

"modifiedDate": "2025-04-04T11:09:47.3195604Z",

"name": "HCIBox-Workspace",

"provisioningState": "Succeeded",

Hi Robert Smit

I have reached out to you in a private message

Thankyou

@Robert Smit Sorry to hear that you are experiencing issue while unlinking workspace during Automation Account deletion process. Just wanted to be double sure, if you have followed the guidance from the Microsoft documentation - https://learn.microsoft.com/en-us/azure/automation/delete-account?tabs=azure-portal#delete-your-azure-automation-account for deleting Automation Account.

Snippet from the URL shared above:

Removing your Automation account can be done using one of the following methods based on the supported deployment models:

• Delete the resource group containing the Automation account.
• Delete the resource group containing the Automation account and linked Azure Monitor Log Analytics workspace, if:
  • The account and workspace is dedicated to supporting Update Management, Change Tracking, and Inventory, and/or Start/Stop VMs during off-hours.
  • The account is dedicated to process automation and integrated with a workspace to send runbook job status and job streams.
• Unlink the Log Analytics workspace from the Automation account and delete the Automation account.
• Delete the feature from your linked workspace, unlink the account from the workspace, and then delete the Automation account.

Please keep us posted if further assistance is required in this matter!

Hi,

Keep in mind that "Delete the resource group containing the Automation account." this will fail as the workspace is still connected. This was the signal that I could not delete the RG.

I follow the guidance.

As of today, the automation account is "Automation Account 'HCIBox-Automation-xw3m6tjlq6urs' was deleted successfully."

Thanks for the help.