We have filed a high priority ticket with Azure. They have acknowledged the issue, and currently we are waiting for an update on recovery.
We are currently investigating this issue.