Skip to content
Welcome
UK
Dragonfly ITDragonfly Insights
AWS & Cloud Platforms

Azure Mandatory MFA Is Now Enforced: What It Means for Scripts, Tools and the Admin Who Never Set It Up

Microsoft's mandatory multi factor authentication for Azure now covers command line tools, scripts and APIs as well as the portal. The postponement window closed on 1 July 2026.

5 min readDragonfly IT

Explainer. Written by Dragonfly IT. Drafted with AI help and checked against the sources listed on this page.

Microsoft has been rolling out mandatory multi factor authentication, MFA, for anyone managing Azure. The first phase covered the Azure portal and admin centres. The second phase, which began on 1 October 2025, extends the requirement to the tools that make changes from scripts and the command line. Microsoft allowed tenants to postpone the second phase until 1 July 2026, so that grace period has now passed.

For a small business with an Azure subscription, the risk is not a sudden outage of the whole service. It is the script, backup job or old admin account that quietly signs in as a person, without MFA, and starts failing.

What does each phase cover?

Microsoft's Learn page sets out the two phases:

  • Phase 1, from October 2024: MFA for anyone signing in to the Azure portal, the Microsoft Entra admin centre and the Microsoft Intune admin centre, extended to the Microsoft 365 admin centre from February 2025.
  • Phase 2, from 1 October 2025: MFA for accounts using Azure CLI, Azure PowerShell, the Azure mobile app, infrastructure as code tools, the Azure SDK and the REST API when they create, update or delete resources. Read only actions do not need MFA.

Who is affected, and who is not?

Every user account that makes these changes must complete MFA, including administrators and break glass emergency accounts. Microsoft says there is no way to opt out, and no exception for test tenants.

Workload identities, meaning managed identities and service principals, are not affected by either phase. That is the key point for automation. A script that signs in as a normal user account, for example a shared admin login used by a scheduled task, now needs MFA and will fail without it. Microsoft recommends moving that kind of automation to a managed identity or service principal.

Microsoft also notes that the Microsoft Entra Connect and Cloud Sync service accounts are not affected, so directory synchronisation keeps working.

What does a failure look like?

A user who has not done MFA can still open a Phase 2 tool, but when they try to create, change or delete something, Azure returns an error saying MFA is required. Some tools then prompt for MFA, while others simply show the error. Microsoft recommends Azure CLI version 2.76 or later and Azure PowerShell version 14.3 or later for the best experience.

How Microsoft suggests you prepare

Microsoft's guidance comes down to a few steps:

  • Create a Conditional Access policy that requires MFA, which needs Microsoft Entra ID P1 or P2, or switch on security defaults if you do not have those licences.
  • Use Azure Policy, in audit mode first, to see where MFA enforcement would bite before it does.
  • Set break glass accounts up with a passkey or certificate based authentication, both of which satisfy the requirement.
  • Move user based service accounts to managed identities or service principals.

What to do this week

A short check is usually enough for a small Azure estate:

  • List everyone with rights to change Azure resources and confirm each one has MFA registered.
  • Find any scripts, scheduled tasks or tools that sign in as a person, and note what they do.
  • Plan to move those to a managed identity or service principal.
  • Check the Microsoft Entra sign in logs for failed MFA prompts from Azure tools.
  • Make sure emergency access accounts use a passkey or certificate and are stored safely.

Where Dragonfly IT can help

Dragonfly IT's cloud services cover Azure management, Conditional Access and moving automation to workload identities, and its cyber security service covers identity security in Microsoft Entra. Azure subscriptions and services are in the Cloud and Hosting range at Darter Tech.

Frequently asked questions

Can I still postpone Azure mandatory MFA?

Microsoft allowed tenants to postpone Phase 2 enforcement until 1 July 2026, and that date has passed. Microsoft says there is no way to opt out. After enforcement begins, a Global Administrator can ask Microsoft support to lift it temporarily, but the sensible course is to fix the accounts and scripts that lack MFA.

Will my automated scripts break?

Only if they sign in as a normal user account and make changes. Microsoft says managed identities and service principals are not affected by either phase. Scripts that use a person's login for create, update or delete actions now need MFA, so they should be moved to a workload identity.

Do I need Conditional Access licences to comply?

Not necessarily. Microsoft recommends a Conditional Access policy requiring MFA, which needs Microsoft Entra ID P1 or P2. If you do not have those licences, Microsoft suggests switching on security defaults instead. Either way, the aim is that users complete MFA before Azure asks for it.

Does this affect Microsoft 365 admins?

Yes, for the admin portals. Microsoft says mandatory MFA began rolling out to the Microsoft 365 admin centre in February 2025 as part of Phase 1. Phase 2 is about Azure tools such as the CLI, PowerShell and APIs making changes to Azure resources.

Sources

More in AWS & Cloud Platforms

Is your business exposed to IT risks you can't see?

Our engineers audit your network, cyber security, backups and Microsoft 365 setup, then hand you a written report on where you're exposed and what we'd prioritise first.

Book My Free Risk Assessment

No cost · No commitment · 0333 0444 323