The incident has been successfully resolved and is now closed.
Brief description of the problem:
There was a service disruption affecting certain resources within the VNet, leading to connectivity issues and failures in communication between services hosted in Azure.
Actual state:
The affected services are now operational, and network connectivity between the impacted resources has been restored.
All related VNet configurations have been reverted to their previous, working state to resolve the immediate issue.
Root Cause:
The problem was triggered by a policy change applied to the Azure Virtual Networks (VNets). Specifically, the new policy inadvertently modified network security settings, causing unexpected connectivity restrictions. This resulted in some services being unable to communicate across subnets or with external resources. The change also affected route tables and security group rules, leading to disruptions in the internal traffic flow within the VNet.
The issue was resolved by identifying and rolling back the policy change, restoring the original VNet configurations. The Azure team is investigating the need for additional safeguards to prevent such policy impacts in the future.
Our systems are back to normal operation. Thank you for your understanding and support throughout this process.