When I send a GET request using the Azure Resource Management REST API to get the resource health status of all the resources under a particular subscription Id like below:
I get the response as below:
{
"id": "/subscriptions/<subscriptionId>/resourceGroups/<resGrp-name>/providers/Microsoft.Web/sites/<webAppName>/providers/Microsoft.ResourceHealth/availabilityStatuses/current",
"name": "<webAppName>",
"type": "Microsoft.ResourceHealth/AvailabilityStatuses",
"location": "northeurope",
"properties": {
"availabilityState": "Unknown",
"summary": "We are sorry, we are unable to report the health of your Web App",
"reasonChronicity": "Persistent",
"recommendedActions": [
{
"action": "Continue to monitor this page for updated status",
"actionUrl": "",
"actionUrlText": ""
}
],
"detailedStatus": "No health activity detected on your Azure Web App in past 10 minutes.",
"occuredTime": "2015-11-18T23:54:59.543Z"
}
}
As shown above, the Availability State for the particular web app is "Unknown".
However, in the Azure portal, this web app has been deliberately paused for more than 15 minutes to check whether the REST API response is consistent with the actual status in the portal, which is expected to return "Stopped" instead of "Unknown".
Does anyone encounter similar behavior or have any idea on this? This result is consistently reproducible with the same unexpected availability status.
Thanks very much.