How to implement ActiveSonar for Azure Cloud Discovery to reduce discovery duration to deal with large environmentsSummary A number of organizations have large scale (service accounts in the order of thousands) Azure cloud environments.Discovery may exhibit slow or incomplete discovery due to the size of the cloud.ActiveSonar is a workaround to alleviate performance issues when discovering large scale Azure cloud environments.When ActiveSonar is implemented, resource free regions are marked and Discovery skips scanning empty regions. Therefore, the number of jobs required for Discovery is reduced. This article describes the issues related to Azure and not other types of cloud providers such as AWS, GCP, etc. Implementing ActiveSonar for Azure Make sure Migrate CPG to Pattern for Azure is completed. Download the update sets. Update sets are available in the attachment section of this KB.Expand the zip file Check imported update sets in the Retrieved Update Sets module and validate the following are loaded. Import Active Sonar followed by ActiveSonar Global update sets. Note that Active Sonar and ActiveSonar Global contains modified patterns to Check resources and resource groups in each service account and mark corresponding Logical Data Centers (LDCs) either passive or active depending on wether any resources are present.exit out of the pattern (type 1) if the target LDC is marked "passive" The above features reduces the amount of steps to complete type 1 patterns.Since LDCs have to be marked so that the Type 1 patterns can utilize the extra information (passive/active), user will not observe performance enhancements until the second time Discovery is run or later. If the instance has gone through the migration to a new hardware type model as per KB0955939, the "Fix Azure Hardware Type" update set needs to be committed. When the above update sets were applies, it overwrites the change made during the migration. The KB is available from - https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0955939If no migration is done, do not apply the update set.Migration can help reduce the discovery duration time. If desired, follow the KB, KB0955939 and they apply the update set. The Sonar-limit-app-patterns update set contains a modified script includes that prevents the scheduler launching Type-1 patterns if the target LDCs are marked passive. Applying the update set will skip launching Type-1 patterns when the data center contains no resource. In an environment that has several service accounts, this help reduce the discovery duration considerably. The modification is made to the script include, CloudApplicationDiscovery.