Azure mandatory multifactor authentication: Phase 2 starting in October 2025
Microsoft Azure is announcing the start of Phase 2 multifactor authentication enforcement at the Azure Resource Manager layer, starting October 1, 2025.
Microsoft Azure is announcing the start of Phase 2 multifactor authentication enforcement at the Azure Resource Manager layer, starting October 1, 2025.
Microsoft values our ongoing collaboration with the security research community to not only identify vulnerabilities in our products and services but also to provide a more consistent and reliable experience for customers.
Azure Service Health helps you stay informed and take action when Azure service issues like outages and planned maintenance affect you, and provides a personalized dashboard that can help you understand issues that may be impacting resources in your Azure subscriptions.
After you experience a Microsoft Azure service issue, you likely need to explain what happened to your customers, management, and other stakeholders. That’s why Azure Service Health provides official incident reports and root cause analyses (RCAs) from Microsoft.
When your Azure resources go down, one of your first questions is probably, “Is it me or is it Azure?
Azure Service Health is extending its ability to help you stay informed about the availability of your Azure resources.
Today I am excited to announce the general availability (GA) of Azure Service Health, a personalized dashboard that provides guidance and support when issues in Azure services affect you.
An industry-wide, hardware-based security vulnerability was disclosed today.
When an Azure service incident affects you, we know that it is critical that you are equipped with all the information necessary to mitigate any potential impact.
On November 18, 2014, many of our Microsoft Azure customers experienced a service interruption that impacted Azure Storage and several other services, including Virtual Machines.
Yesterday evening Pacific Standard Time, Azure storage services experienced a service interruption across the United States, Europe and parts of Asia, which impacted multiple cloud services in these regions. I want to first sincerely apologize for the disruption this has caused.
Introduction As a follow-up to my March 1 posting, I want to share the findings of our root cause analysis of the service disruption of February 29th.