Many users reported that almost all Microsoft services hosted on Azure were shut down on the evening of April 1. Both the @AzureSupport and @MSFT365Status accounts on Twitter have confirmed the issue and pointed out that many users are in a non-working state as of 5:45 pm EST on the status page.
Users report that they cannot access the Azure portal, Azure services, Dynamics 365, Xbox Live and many other services. Bing.com is closed. Interestingly, my Exchange email has been activated at this time, but this may be because Microsoft has not yet completed the migration of Exchange to Azure.
It is not clear which country and region are currently affected because the alternate Azure status page suggested by Microsoft shows a green check mark-although the title states “An emerging issue is under investigation. We will provide an update as soon as possible and provide additional details.”
At 6pm Eastern Time, the MSFT365Status account posted: “We are investigating potential DNS issues and are evaluating mitigation options. “
Update: At 6:30 pm EST, the Azure status page launches (for me anyway). This is a worldwide disruption. Microsoft’s status message stated that “a portion of users” may experience “intermittent problems” with Microsoft services.
Update (6:35 PM EST): The MSFT365Status account report may be recovering: “Microsoft rerouted traffic to our resilient DNS function and has seen improvements in service availability. We are continuing to investigate the cause of the DNS issue. The next update will be provided within 60 minutes. Or it depends on the situation.”
I have seen several users say that today is not the first time Microsoft cloud services are in trouble this week. Microsoft customer Long Zheng pointed out: “This Azure DNS problem has not started today. Since a few days ago, I have seen random DNS resolution failures of App Services and Cloud Services, and it has been significantly upgraded. I am surprised that Azure engineers have not had some Internal indicators that may be discovered earlier.”