We implemented our MS SQL Database to leverage the native Azure Virtual Machine feature and access the MS SQL Database from the Azure-hosted website via a private static IP address (not DNS) of the Azure VM. We configured this static IP address setting in Azure VNet, a feature that Microsoft has indicated is pending GA.
However, in two subsequent issues in the Azure hosting environment (first incident: related to an Azure patch from Microsoft; the second incident: related to a hardware failure).
In either of these instances, the system failed to gracefully re-connect to the MS SQL Database from Azure-hosted application website.
We have configured Endpoint monitoring and an Azure Notification alert in the Azure-hosted website to check the status of the MS SQL Database access from Azure website every 5 minutes. This Azure notification alerts when our Azure-hosted application website can’t connect to the Azure Virtual Machine. Outtage issues in the Azure environment have resolved automatically on both production and Test environment in last few weeks.
Has anyone else experienced similar issues with the Vnet configuration, or implemented similar monitoring to ensure stability?