Can't delete non-existent ASR appliance in the Azure portal

Question

I keep getting the error above when we try and delete this old ASR applicance in Azure even though it's been off for many months. The error makes no sense.

Error ID

310161

Error Message

Delete operation for this appliance has failed as one or more of the appliance components are in a healthy state.

Possible causes

One or more appliance components are in a healthy state.

Recommendation

Delete operation is only allowed on an appliance which has all its components in a unhealthy state. To remove an appliance where not all the components are healthy, you must shut down the appliance machine and then trigger appliance deletion from Azure portal instead. Learn more - https://aka.ms/ApplianceReset.

Related links

https://aka.ms/ApplianceReset

First Seen At

6/9/2025, 9:22:38 AM

Answer 1

hi Juan Ramirez, thanks for posting this,

microsoft's docs say u gotta make sure ALL components of that asr appliance are properly marked as unhealthy before deletion will work. the error's basically screaming 'hey i think something here might still be working!' even if u know it's not.

what usually fixes it in azure land, lets review it, go back to that appliance machine (the physical or virtual one u used for asr). make triple sure it's 100% powered off. like, not sleeping, not hibernating - full shutdown, wait like 5-10 mins because azure sometimes takes its sweet time updating statuses. check the appliance health status again in the portal. if it still shows healthy components, u might need to manually mark them as unhealthy. microsoft's got a guide for that exact scenario https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-overview

worth checking if u have any old replication jobs hanging around in 'pending' state. those can trick azure into thinking the appliance is still needed. clear those out first if u spot any.

now for some general tech wisdom that works anywhere )) when u hit phantom health status issues like this, always check cached data in ur browser (try incognito mode), background services that might be pinging the old appliance, dns records that could be pointing to it this kinda thing happens in aws and google cloud too, not just azure.

sometimes just leaving it alone lol (why not) for a day lets azure's backend finally realize 'oh yeah this thing is dead'. their health checks can be stubborn like that )))

microsoft actually explains why they do this https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-overview it's to prevent accidental deletion of stuff that's still working. annoying when u know better, but kinda smart overall.

try these steps and hit me back if it's still being weird .....

Best regards,

Alex

and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer
PPS That is my Answer and not a Comment

https://ctrlaltdel.blog/