Control 7 MFA: The foundational block of phishing-resistant defence
ACSC Essential Eight Control 7 (Australian Cyber Security Centre — Implementing multi-factor authentication, accessed 16 June 2026) mandates Multi-Factor Authentication (MFA) on all user accounts, with progression from basic SMS codes to phishing-resistant methods. This post outlines method comparisons, phased implementation, Azure AD configuration, and operational procedures for recovery and exceptions.
1) MFA maturity levels and method comparison
- Level 1: SMS OTP or authenticator apps — baseline protection.
- Level 2: App-based MFA with conditional access and phased SMS removal.
- Level 3: Phishing-resistant FIDO2 hardware keys or passwordless biometrics for privileged roles (Microsoft Learn — Authentication strengths (phishing-resistant MFA), accessed 16 June 2026).
2) Implementation strategy
- Phase 1: Protect privileged accounts with FIDO2 keys within 3 months.
- Phase 2: Extend to sensitive roles over months 3–6.
- Phase 3: Enterprise-wide rollout months 6–12 with backup keys and recovery plans.
3) Azure AD deployment and conditional access
- Use Conditional Access policies (Microsoft Learn — Microsoft Entra Conditional Access overview, accessed 16 June 2026) to require MFA for admin roles, sensitive apps, and risky locations. Use P1/P2 licensing for advanced controls.
4) Recovery, lost devices and resilience
- Establish helpdesk flows for lost phones/keys, register backup methods, and maintain limited break-glass accounts with strict controls.
Call to action
Begin with privileged account protection and plan a phased rollout with training, backup keys, and exception governance to reach phishing-resistant MFA for critical roles.
Sources referenced in this article: Australian Cyber Security Centre — Implementing multi-factor authentication; Microsoft Learn — Microsoft Entra Conditional Access overview; Microsoft Learn — Authentication strengths (phishing-resistant MFA).


