https://www.servicenow.com/community/itom-forum/vm-instance-stuck-in-quot-off-quot-state-where-the-vm-was/m-p/3547730#M127251 <P>Hi,&nbsp;</P><P>&nbsp;</P><P>I have discovery schedules set up for our AWS and Azure environments. I noticed that when VMs are off then deleted from Azure or AWS, often VM instance CIs are stuck in off state instead of terminated</P><P>&nbsp;</P><P>I checked the related CI types table and deletion strategy is marked as retired for but AWS and AZure pattern. What do I miss?</P> Fri, 22 May 2026 13:26:54 GMT Nateu 2026-05-22T13:26:54Z https://www.servicenow.com/community/itom-forum/vm-instance-stuck-in-quot-off-quot-state-where-the-vm-was/m-p/3547730#M127251 <P>Hi,&nbsp;</P><P>&nbsp;</P><P>I have discovery schedules set up for our AWS and Azure environments. I noticed that when VMs are off then deleted from Azure or AWS, often VM instance CIs are stuck in off state instead of terminated</P><P>&nbsp;</P><P>I checked the related CI types table and deletion strategy is marked as retired for but AWS and AZure pattern. What do I miss?</P> Fri, 22 May 2026 13:26:54 GMT https://www.servicenow.com/community/itom-forum/vm-instance-stuck-in-quot-off-quot-state-where-the-vm-was/m-p/3547730#M127251 Nateu 2026-05-22T13:26:54Z