Azure - Unable to discover Cloud Resource for Traffic Manager ProfilesIssue If there is a request for the discovery of Azure Traffic Manager profiles as part of the horizontal discovery, this article provides a solution. The default "Azure Resource Inventory" pattern does not have the capability to discover the specific resource type, Microsoft.Network/trafficmanagerprofiles. However, this issue can be resolved by making a minor modification to the pattern.CauseAs part of the current pattern flow, they're getting filtered out because their "location" = "global" and the discovery pattern is filtering out all resources not associated with the targeted LDC (e.g. Central US). When looking at the list of LDCs, the concept of "global" is not represented, so these will never get imported.ResolutionBefore making any changes to the pattern, it is suggested to add the resource type (Microsoft.Network/trafficmanagerprofiles) to the Cloud Resource Whitelist. This will allow Discovery to start pulling the resource type from Azure as part of the Resource Inventory pattern. Note: Try these changes in the sub-prod instance before implementing them in the production environment. The changes that are made to the pattern are considered to be customization. Follow the below steps to achieve this. Log in to the instance. From the filter, the navigation type in "Discovery Pattern" opens the list of discovery patterns.From the Name filter search for the "Azure Resource Inventory" Pattern.From the identification, section click on the 'Resource Inventory Identification' link.Click on step 10 from the left navigation window and make the changes as listed in the below image.Once done. Save the changes. Publish it.Go to your mid server list and click on "Pattern Sync to Mid"Run discovery and check the results.