Contributor
ContributorFurther information on this issue for anyone experiencing the problem.
It turns out I had 2 issues:
- There was a DNS issue on with our collectors in Azure UK West, I spotted this when our on-prem exchange servers had the same issues contacting Azure. The DNS server forwarders were pointing to another internal DNS server that was decommissioned rather than a working internal (or external) DNS server
- The second issue was a collector based in Azure UK South where DNS was working fine , muddying the water for troubleshooting. This issue was down to the Subscription being monitored missing part of the URL.
So for a working subscription you would see it accessing https://management.azure.com/subscriptions/abcdefg12345 etc. The non working subscription in my case was missing a / and subscription so looks like: https://management.azure.comdefg12345
I have checked the credential page, which is how the url is pulled together and it is being passed to the SaaS backend correctly.
Support are still troubleshooting for me but I hope this helps. To check the URL check the summary tab of the subscription and the device logs section at the bottom
