Azure Cloud Discovery Incorrectly Marks Active Logical Datacenters and Child CIs as Retired After Discovery Run on Discovery and Service Mapping plugin v1.30 on Zurich family.DescriptionStarting with the Zurich release and later, if the customer’s instance has the Discovery and Service Mapping plugin version 1.30, Azure Cloud Discovery incorrectly marks active Logical Data Centers (LDC) and their child CIs as Retired in CMDB after every discovery run.Steps to Reproduce Install Discovery and Service Mapping plugin version 1.30.Configure an active Azure service account Create an azure discovery schedule and run itAfter completion, check LDC and child CIs in CMDB — operational_status will show Retired despite resources being live in AzureWorkaroundThis problem has been fixed, please update Discovery and Service Mapping plugin to version 1.30.2 . After plugin update follow these steps to make data correction on your instance. Commit the attached update set on your instance.Open the fix script directly using the link below (replace <your-instance> with your actual instance name): https://<your-instance>.service-now.com/sys_script_fix.do?sys_id=429a38a7930c4f108691f83a7bba1095&sysparm_record_target=sys_script_fix&sysparm_record_row=1&sysparm_record_rows=1326&sysparm_record_list=ORDERBYDESCsys_updated_on Alternatively, navigate to Fix Scripts in the Left navigation and search for "Azure LDC Cascade Retire Fix".Click Run Fix Script to execute it in the background.The script will identify all Azure LDCs and CIs that were incorrectly marked Install status as Retired due to the cascading retire issue, and reset their install status back to Active.Related Problem: PRB2009714