Microsoft Azure is announcing the commencement of Phase 2 multifactor authentication enforcement astatine the Azure Resource Manager layer, starting October 1, 2025.
As cyberattacks go progressively frequent, sophisticated, and damaging, safeguarding your integer assets has ne'er been much critical, and astatine Microsoft, your information is our apical priority. Microsoft research shows that multifactor authentication (MFA) tin artifact much than 99.2% of relationship compromise attacks, making it 1 of the astir effectual information measures available.
As announced successful August 2024, Azure started to instrumentality mandatory MFA for Azure Public Cloud sign-ins. By enforcing MFA for Azure sign-ins, we purpose to supply you with the champion extortion against cyber threats arsenic portion of Microsoft’s committedness to heighten information for each customers, taking 1 measurement person to a much unafraid future.
As antecedently announced, Azure MFA enforcement was rolled retired gradually successful phases to supply customers with capable clip to program and execute their implementations:
- Phase 1: MFA enforcement connected Azure Portal, Microsoft Entra admin center, and Intune admin halfway sign-ins.
- Phase 2: Gradual enforcement for MFA request for users performing Azure assets absorption operations done immoderate lawsuit (including but not constricted to: Azure Command-Line Interface (CLI), Azure PowerShell, Azure Mobile App, REST APIs, Azure Software Development Kit (SDK) lawsuit libraries, and Infrastructure arsenic Code (IaC) tools).
We are arrogant to denote that multifactor enforcement for Azure Portal sign-ins was rolled retired for 100% of Azure tenants successful March 2025. Now, Azure is announcing the commencement of Phase 2 MFA enforcement astatine the Azure Resource Manager layer, starting October 1, 2025. Phase 2 enforcement volition beryllium gradually applied crossed Azure tenants through Azure Policy, pursuing Microsoft safe deployment practices.
Starting this week, Microsoft sent notices to each Microsoft Entra Global Administrators by email and through Azure Service Health notifications to notify the commencement day of enforcement and however to hole for upcoming MFA enforcement.
Customer impact
Users volition beryllium required to authenticate with MFA earlier performing assets absorption operations. Workload identities, specified arsenic managed identities and work principals, aren’t impacted by either phase of this MFA enforcement.
Learn much astir the scope of enforcement.
How to prepare
1. Enable MFA for your users
To guarantee your users tin execute assets absorption actions, enable MFA for your users by October 1, 2025. To place which users successful your situation are acceptable up for mandatory MFA, follow these steps.
2. Understand imaginable impact
To recognize imaginable interaction up of Phase 2 enforcement, assign built-in Azure Policy definitions to artifact assets absorption operations if the idiosyncratic has not authenticated with MFA.
Customers tin gradually use this enforcement crossed antithetic assets hierarchy scopes, assets types, oregon regions.
3. Update your Azure CLI and PowerShell clients
For the champion compatibility experience, users successful your tenant should usage Azure CLI mentation 2.76 and Azure PowerShell mentation 14.3 oregon later.
Next steps for multifactor authentication for Azure sign-in
- To guarantee your users tin execute assets absorption actions, enable MFA for your users by October 1, 2025.
- To recognize the imaginable impact, use a built-in Azure Policy definition in audit oregon enforcement mode.
- For the champion compatibility experience, users successful your tenant should use Azure CLI mentation 2.76 and Azure PowerShell mentation 14.3 or later.
- If you can’t alteration MFA for your tenant by October 1, 2025, the Global Administrator for your tenant can postpone the enforcement day done Azure Portal.
- Keep an oculus retired for further communications done the previously communicated notification channels.