mfa

Rolling out MFA to staff: a practical rollout for Swiss SMEs

AA
Aurum Avis Labs Author
7 min read

Rolling out MFA to staff: start with admins, then mail, then the rest

Rolling out MFA to staff means every account that can read email or change payment data needs a second factor before an attacker with a stolen password gets in. For a Swiss SME on Microsoft 365 or Google Workspace, the project is as much communication as technology. MFA cuts business email compromise that leads to invoice fraud with a changed IBAN. It does not replace four-eyes payment controls. Plan phases, name a help window, and train people on MFA fatigue attacks where criminals spam approval prompts until someone taps approve.

Before you flip the switch, align with how staff report internal security incidents so locked-out users know where to call.

What to decide before week one

Inventory global admins, billing owners, finance mailboxes, and shared inboxes that still use a password only. Pick an authenticator app or passkey method your tenant supports. You are not choosing between ten products; you are picking what Microsoft or Google already offers.

Name an internal owner and your IT partner role: who writes conditional access policies, who answers the phone on go-live day, who escalates to leadership if an executive refuses enrollment. Finance should know MFA is coming the same week you publish the password policy for a small business, so identity rules read as one story.

  • List admin and finance mailboxes that must enroll first
  • Pick go-live dates outside month-end payment peaks if possible
  • Prepare a one-page setup guide with screenshots for your chosen app
  • Book double helpdesk coverage for the first rollout day
  • Draft the fatigue rule: deny unknown prompts, never read codes to a caller

Phased rollout that staff can follow

  1. Enforce MFA on admins

    Global admins, billing owners, and anyone who can reset passwords. Block legacy authentication where the tenant allows it.

  2. Pilot one department

    Choose a team that will tolerate friction. Fix helpdesk scripts from their feedback before you widen the policy.

  3. Require MFA on all mail users

    Apply conditional access or security defaults to every mailbox that can receive external mail.

  4. Roll out VPN and line-of-business apps

    Same identity provider where possible. Document each exception with an expiry date.

  5. Close the gap on new hires

    MFA registration becomes part of day-one onboarding, not a ticket three weeks later.

A made-up example: a logistics firm with 120 Microsoft 365 mailboxes enables the Authenticator app for IT and finance in week one, pilots operations in week two, and requires MFA for all mail users in week three. Helpdesk hours run 08:00 to 18:00 on rollout day. Two users call because they approved a prompt at lunch without logging in; IT resets sessions, blocks the foreign sign-in, and sends a short note on fatigue.

MFA fatigue: the attack your rollout must mention

After MFA is on, attackers who stole a password may send repeated push notifications or call the user pretending to be IT. Staff should know: if you did not just log in, deny the prompt and report it through the internal channel. Never read codes to a caller. That overlaps with deepfake CEO voice call fraud when “IT” asks for a code on the phone.

Put the fatigue rule in the same email as the setup link. One sentence in a team chat on go-live day is not enough.

Who may need a temporary exception

Legacy scanners, shared kiosk PCs, and one old line-of-business app sometimes lack modern authentication. Document each exception with owner, review date, and a compensating control such as network isolation.

Reasonable exceptions

  • Service account with certificate-based auth in progress
  • Kiosk PC on an isolated VLAN with no mail access
  • Scanner sending mail through a relay you are replacing

Not exceptions

  • Executive preference without a technical barrier
  • Shared finance login because “we always did it this way”
  • Permanent SMS-only for payment approvers

Review the exception list quarterly with leadership. Finance mailboxes should not stay on the list.

Communication that reduces lockouts

Two weeks before go-live, send the date, helpdesk hours, and a link to the setup guide. On the day, remind people in the chat tool they already use, not only an IT ticket. After one week, publish how many accounts still lack MFA and who owns follow-up.

  • If finance is in a payment run

    Schedule enrollment after the run or extend helpdesk hours for approvers.

  • If many staff work remotely

    Use self-service enrollment; avoid posting QR codes on paper that anyone in the post room could scan.

  • If the CEO has not enrolled

    Enroll leadership in the pilot so approval discipline is visible before the wider mail policy.

Technical sequence in Microsoft 365 and Google Workspace

In Microsoft 365, apply Security Defaults or conditional access in stages: block legacy auth, enforce MFA on admins, then on all users who reach Exchange Online. Review shared mailboxes separately; many still need a named delegate with MFA rather than a shared password.

In Google Workspace, use 2-Step Verification enforcement from the admin console with the same order: super admins first, then organizational units. Test whether legacy IMAP clients break before you announce a cut-off date.

Service accounts and integrations should move toward certificates or managed identities where the vendor allows. Mail-enabled service accounts that cannot use MFA need a written exception, not an open-ended waiver.

Admins should store backup codes sealed offline. Losing a phone should not mean bypassing MFA with a shared password. External IT partners need a written role before go-live: who sets policies, who runs the helpdesk, who reports incidents to leadership.

Guest accounts and contractors get MFA before VPN access is granted. Guest Wi-Fi does not replace identity controls. Contractor mailboxes with client data belong in the same policy as internal users.

One week after go-live, review sign-in logs for foreign countries, legacy auth, and repeated failures. A short phishing simulation can follow optionally, without scoring individuals; this is orientation on Swiss labour practice, not legal advice.

Measuring success without vanity metrics

Track the percentage of users with registered MFA, the number of fatigue reports handled, and time to enroll new hires. Sign-in logs two weeks after go-live should show fewer legacy authentication attempts.

65% / 82%

Deloitte Cyber Study 2026, firms under 250 staff: regular training in small versus medium firms. Not our survey. Pair MFA rollout with a short live session if your firm is below the medium-firm line.

Rollout is complete when registration hits your target, legacy auth drops, and finance has been briefed on rejecting prompts during payment approval unless they just logged in themselves.

Training that covers MFA and payment fraud

Finance and management benefit from one live hour on MFA, phishing, and payment verification. Callback habits for customer data reinforce security habits; see verifying identity on the phone for the privacy-side pattern. The Aurum session format for phishing and payment fraud is described on security awareness training.

Can we roll out MFA during holiday season?

Prefer a quiet week with helpdesk coverage. If you must go live before year-end invoice peaks, extend support hours for finance users.

Should we rank authenticator apps against each other?

No. Use what your tenant supports and document one standard method. This article is about rollout and fatigue, not a product shoot-out.

Start with finance and mail administrators. The rest of the team follows in the same month, with a named person to call when the prompt fails.

mfa multi-factor authentication rollout switzerland
AA

Written by

Aurum Avis Labs

Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.

Customize your cookie preferences. Essential cookies cannot be disabled as they are required for the website to function properly.

Essential Cookies

Required for basic website functionality, security, user authentication, and error tracking.

Always active

Analytics Cookies

Help us understand how visitors interact with our website to improve user experience. Includes Google Analytics and Microsoft Clarity session recordings.

Marketing Cookies

Used to track visitors across websites to display relevant and engaging advertisements.