Azure Automation recovery blade returns 404 for ManageDeletedAccounts

Question

Azure Automation recovery blade returns 404 for ManageDeletedAccounts

Adrian Dragomir 0

I’m trying to recover a soft-deleted Automation account. The documented list API returns the deleted account, and its original resource group still exists. It was deleted on 20 October 2026, so it is within the 30-day recovery period.

Opening Automation Accounts → Manage deleted accounts fails. The browser console reports Failed to retrieve the blade definition for 'ManageDeletedAccounts' and HTTP 404 for the HubsExtension/_generated/Blades/ManageDeletedAccounts.js script. I reproduced this in different browsers, Incognito, and on a different network.

Is there a supported recovery path while this portal blade is unavailable, or can the portal issue be investigated? I can provide the subscription ID and session ID privately if needed.

0 comments

1 answer

Your answer

Answer 1

Hello Adrian Dragomir,

Greetings! Thanks for raising this question in the Q&A forum.

The error you captured (Failed to retrieve the blade definition for 'ManageDeletedAccounts' with a 404 on HubsExtension/_generated/Blades/ManageDeletedAccounts.js) means the portal could not load the blade's script. Since you reproduced it in several browsers, in Incognito and on another network, the problem is on the portal side and not in your browser or your account. The documented recovery path for a deleted Automation account is the portal, so I cannot point you to a fully documented CLI or PowerShell recovery command, and I would not suggest trying undocumented API calls against a soft-deleted account. The documented conditions are met in your case: the account was created with the Azure Resource Manager deployment model, was deleted within the past 30 days, and its resource group still exists.

Here are the steps I would follow:

Try other portal entry points. Use the portal at https://portal.azure.com/?feature.customportal=false to bypass cached extension settings, or open the portal from another tenant sign-in. You can also try the direct path Automation Accounts > Manage deleted accounts again from a fresh session after signing out fully. A stale or partially rolled out HubsExtension build is a common cause of a missing blade script, and it sometimes clears by itself.

Confirm the recovery conditions. Check that the original resource group exists with the same name, that the account was deleted on 20 October 2026 (the 30 day window ends around 19 November 2026), and that you hold at least Contributor on the subscription and the resource group. You can confirm the deleted account is still listed with the same list API you already used.

Check Azure Service Health. Open Service Health in the portal and look for any portal or Azure Automation issue in your region. If an incident is open, recovery from the portal should work again once it is resolved.

Collect the details that support will need. Keep the subscription ID, the resource group name, the Automation account name and region, the deletion date, the portal session ID (found under the profile menu, Settings > Support + Troubleshooting or Help > Show diagnostics), and a HAR file or a screenshot of the browser console showing the 404.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,
Jerald Felix.