The Reluctance Is Real
Multi-factor authentication (MFA) blocks over 99% of automated account compromise attacks. And staff will still complain about it.
“It slows me down.” “My phone is not always with me.” “Why can’t we just have a strong password?”
Rolling out MFA successfully is as much a communication and change management exercise as a technical one.
Choose the Right MFA Method First
Not all MFA is equal in terms of user experience:
Authenticator app (Microsoft Authenticator, Google Authenticator): A number-matching prompt on the user’s phone. The best balance of security and usability for most businesses.
SMS code: A six-digit code sent by text. Easy to set up but less secure (SIM-swap attacks) and slower than an app. Avoid for administrators.
Hardware security key (YubiKey): Physical key that plugs into USB. Highest security, most friction. Appropriate for administrators and high-risk accounts.
For most small businesses: Microsoft Authenticator with number matching is the right choice.
The Implementation Approach
Phase 1: Leadership First
Implement MFA for the business owner, directors, and any IT administrators before rolling out to all staff. Senior leaders will not be exempted from the process they are mandating for others.
Phase 2: Communicate Before Enforcing
Do not just switch MFA on and let staff discover it when they cannot log in. Send a brief communication explaining what MFA is, why you are doing it, what will change for staff (a 5-second extra step), when it will be required, and who to contact if they have trouble.
The framing matters. “We are adding security that protects you and the business” lands better than “you must now do an extra thing.”
Phase 3: Set a Deadline and Enforce
Enable MFA enforcement with a registration deadline — staff have two weeks to set up the Microsoft Authenticator app before enforcement begins. After the deadline, accounts that have not registered will be prompted at login.
Phase 4: Support During the Rollout
Be available during the rollout week. Common support requests: “I got a new phone — my authenticator is not working” (need to re-register), “I am overseas and cannot log in” (location policy may be blocking), “I changed my number” (SMS fallback needs updating).
Addressing Common Objections
“I don’t want to use my personal phone for work”: A reasonable concern. The authenticator app does not give IT access to the phone or personal data.
“What if I forget my phone?”: Conditional Access can be configured not to require MFA from trusted locations such as the office network.
“We never had to do this before and we were fine”: The threat environment has changed significantly. This is now standard practice, not an overreaction.
After MFA Is On
Once MFA is enforced, most staff stop noticing it within a week. The friction is minimal when using an authenticator app — a single tap to approve a login notification.
If staff receive unexpected MFA prompts (they did not initiate a login), they should decline the prompt and report it immediately. This is the signal that someone has their password and is trying to log in.
Worried About Your Business Security?
Netluma IT Business Shield ($69 per device or server per month, ex GST) includes antivirus, 24/7 cybersecurity alerts, automatic network isolation on ransomware or threats, 24/7 dark-web monitoring with leaked-credential alerts, email deliverability monitoring, managed patching, EDR and MDR (required for cyber insurance where applicable), staff security awareness training, automated daily cloud backup of user files, and SaaS backups for Google Workspace or Microsoft 365.
Related Services
CybersecurityPriority-based remote responseLocal Gold Coast team




