Provide better reason codes for Azure SQL unavailability
When Azure SQL databases are unavailable the Reason "code" seems to always be "Unplanned". We know from research and confirmation from Microsoft that this can be due to back end service reconfiguration, issues after updates, etc. My suggestion is to provide enhanced reason codes so that we know when there is a problem and when it's due to something expected like back end service reconfigurations. Having a more granular view of the reasons would save a lot of troubleshooting time (for us and for MS). At a minimum, it would be nice to have categories such as:
Reconfiguration - caused by expected back end reconfiguration
SWUpdate - caused by expected back end or Azure SQL software
HWUpdate - caused by expected back end hardware update
Unplanned/Unknown - caused by an actual issue TBD
Andrew Falk commented
This a great idea. We just had another DB outage and raised a ticket  only to find out it was a "planned" upgrade. It sure would save us a lot of time and frustration if we knew these were expected. We just want to rule out something worse isn't happening.