Microsoft’s Azure portal down following new claims of DDoS attacks – Source: www.bleepingcomputer.com

Update at 6/9/23 1:33 PM ET added below

The Microsoft Azure Portal is down on the web as a threat actor known as Anonymous Suda claims to be targeting the site with a DDoS attack.

Attempting to access the portal at https://portal.azure.com displays an error message stating, “Our services aren’t available right now. We’re working to restore all services as soon as possible. Please check back soon.” The mobile app appears unaffected at this time.

The Microsoft Azure status page includes status information stating that Microsoft is aware of the incident and are attempting to mitigate it.

At the same time, a threat actor known as Anonymous Sudan claims to be conducting a DDoS attack against the Microsoft Azure portal, sharing an image of the page not working.

Anonymous Sudan claims to be a hacktivist targeting US companies to protest the United States’ involvement in Sudanese internal affairs. However, some believe this is a false flag and that the threat actors are actually Russian.

Regardless of the threat actor’s origins, this has not been a good week for Microsoft, with the threat actor conducting DDoS attacks on other Microsoft web portals for Outlook.com and OneDrive, which also suffered outages at the same time.

While Microsoft has not confirmed that these outages were due to DDoS attacks, they did share the following statement with BleepingComputer yesterday, hinting that the issues are more than just a technical problem.

“We are aware of these claims and are investigating. We are taking the necessary steps to protect customers and ensure the stability of our services,” Microsoft told BleepingComputer in a statement.

BleepingComputer has once again contacted Microsoft to ask if the services are down due to a DDoS attack, but a response was not immediately available.

Update 6/9/23 1:32 PM ET: The Azure portal appears to be live again and stable.

Microsoft has still not disclosed the underlying cause for the outage, only indicating that they applied more load balancing proccesses to the service.