Update from Microsoft regarding this issue:
Incident Title: Issue with Azure SQL Server Private Connection
Incident Summary:
The incident started on Feb 9, 2024. It affected the SQL server [iverxue-logisql] and disrupted its normal operation. This incident did not allow resources to be deployed due to a continuous "Ready" status response which caused ARM deployment jobs to go past their allowed timeout period.
Analysis and Mitigation:
Investigations show that a provisioningState value of "Ready" was continuously returned which is seen as a non-terminal state and resulted in the ARM deployment jobs running over the allowed timeout period. These jobs were expecting a terminal state of "Succeeded" for successful resource provision. The issue was fixed via a reconfiguration of the SQL server and private endpoint connections.
Next Steps:
To avoid repeats of this issue in the future, steps have been put in place to ensure operations run smoothly and that the "Ready" status does not cause the ARM deployment jobs to overrun their timeout period. We have created a repair item to fix this issue. We assure you that we are doing our best to provide the highest quality service and will address this incident accordingly. We are sorry for this disruption, and we appreciate your understanding.