503 response from atlas.microsoft.com apis

Question

I have been experiencing issues last weekend and now today (Sunday midday AEST) when it comes to rendering Azure Maps. I wondered if it were something I was doing but both occasions I try out the Azure Samples (any sample) and disable caching in Google Chrome Azure devtools.

The first time it occurred things just came good after a few hours. I'm yet to see a repeat of things coming good with this occurrence yet. I'm concerned if this is some issue ongoing or maybe just a transitionary issue related to crowdstrike's influence? I certainly don't want to see maps go down every weekend so would appreciate if there's any insight as to some backend problem. The Azure status website indicates no problem at this time.

The issue is always a 503 response, and just for extra confidence it's not my machine I had 2 other people with their own internet try the samples and experienced the same results.

Answer 1

Disabling caching shouldn't be an issue when querying one of the REST services, most of them don't have caching headers as it is. I'd be surprised if it was related to crowdstrike.

We can't really debug this from the forums, please open a support ticket in the Azure portal using the following steps:

1. Go into the Azure portal and open up your Azure Maps resource.
2. On the left side bar, scroll down to Help -> Support and Trouble shooting and click the button.
3. Follow the steps to create a ticket (it will first ask you about the issue and then try and make some suggestions, they may have some related things to test out, if you keep going through you will be able to raise a support ticket and someone from the Azure support team will be able to investigate this issue and if needed, have the Azure Maps team investigate it's backend).