MSP Insights··5 min read

Client refuses MFA? How an MSP puts the risk in writing

When a client says no to multi-factor authentication, a signed risk acceptance protects both sides before insurance renewal. Here is what to put in it.

By Pardeep Sharma

The short version: when a client refuses multi-factor authentication (MFA), the work is not over. Get the refusal in writing, signed by a director, before the insurance renewal season starts in December. The signed page protects you, protects the client's honesty on their insurance form, and gives you a date to ask again. Most refusals are about friction, not principle, so offer an easier way in first.

Why does a refused MFA request matter to you?

An unsigned refusal is a problem you own the moment something goes wrong. If an account without MFA is breached, the first question is whether anyone told the client. A phone call and a shrug will not answer it.

It also shows up on paper. The cyber insurance questionnaire walkthrough covers how MFA is usually the most scrutinised answer on the form. Partial coverage is treated as a risk factor, so "we mostly have it" is a poor answer.

Why do clients say no?

Usually for one of four reasons. Knowing which one tells you what to offer.

What the client saysWhat it usually meansWhat to offer
"My staff hate the codes"Friction at sign-inA passkey or the Microsoft Authenticator app with number matching
"It locks me out when I travel"No plan for a lost phoneA documented recovery process and a second method
"I don't have time"The rollout feels bigSwitch on admin accounts first, then the rest in groups
"We've never been hacked"The risk feels abstractOne page showing what an attacker gets from one stolen password

Microsoft Research studied Entra (formerly Azure AD) accounts and reported that MFA cut the risk of compromise by about 99.22% across the population studied, and by about 98.56% where credentials had leaked. It is a study of Microsoft accounts, so use it as direction, not a promise. It is still a better argument than "the insurer says so".

What is the one-page conversation?

Keep it to three sentences, in this order:

  1. "A stolen password is enough to sign in to your email and files today."
  2. "A second step stops almost all of those attempts, and we can make it a tap or a fingerprint."
  3. "If you still choose not to, I will ask you to sign a page that says so."

Do not argue past the third sentence. The page does the persuading.

What goes in the risk acceptance?

One page, plain English, signed by a director or owner:

  • The business name, the date and the person signing.
  • Exactly which accounts or systems will not have MFA, and why.
  • What you told them the risk is, in one sentence.
  • What you offered instead, and that they declined.
  • Any compensating step you are taking, such as blocking sign-ins from overseas.
  • A review date, no more than 90 days away.
  • A line saying the client must answer insurance and supplier forms to match, so exceptions must be listed.

Ask your lawyer to review the template once. Then reuse it.

If you're a small business

If your IT provider asks you to sign one of these, read it. It means you have chosen to carry a risk, and you are the one who answers the insurance form. The Insurance Contracts Act 1984 puts a duty of disclosure on the insured for business policies, so the form must match what is switched on. If the reason you said no was inconvenience, ask for a passkey or the Authenticator app.

If you're an MSP

Add the refusal to the same file as the rest of the client's evidence. A signature with no scan date next to it is weak. Record which accounts have no MFA today, taken from the tenant, not from memory. If you need the "needs review" label for an account you cannot confirm, use it.

Do not quietly absorb the risk. A refusal that sits in an email thread is a refusal you will not find in January. For how this fits a paid compliance line, see the MSP compliance pricing guide.

Worked example

This is a made-up example, not a real client.

A 20-person accounting firm is due for insurance renewal in January. Two partners refuse MFA because they sign in from home on shared devices. The MSP offers passkeys on their work laptops. One partner agrees. The other still says no.

The MSP prepares a one-page acceptance for that partner's mailbox only, lists the compensating control (sign-ins limited to Australia) and sets a review date 60 days out. The firm's broker form says "MFA on all users except one mailbox, accepted by the director, review due March". That answer is true and can be backed up.

Where does CYBERWHITE fit?

CYBERWHITE does not write your contracts. It gives you the evidence the page needs. One Microsoft 365 connection feeds the Essential 8 and SMB1001 scans, and a scan takes about five minutes per tenant. It shows MFA by account as met, not met or needs review, with a date. ASD's Essential Eight maturity model sets the MFA expectations the scan checks against. Where a control sits outside Microsoft 365, you record who attested to it.

To see what an assessor would still ask for on one of your clients, book a free proof check. We scan one tenant with you. You can also read the Essential 8 compliance guide, SMB1001 for MSPs or try the cyber insurance calculator.

Your checklist

  • List every client with accounts that have no MFA, from the tenant.
  • Offer a passkey or authenticator app before accepting a no.
  • Use the three-sentence conversation once. Do not debate.
  • Get a director to sign a one-page acceptance.
  • Name the exact accounts excluded, and why.
  • Add one compensating control where you can.
  • Set a review date within 90 days.
  • Make sure the insurance form lists the same exceptions.

Sources

  • Microsoft Research: How effective is multifactor authentication at deterring cyberattacks?
  • Australian Signals Directorate, cyber.gov.au: Essential Eight maturity model
  • Insurance Contracts Act 1984 (Cth), section 21, via legislation.gov.au and AustLII

Keep reading: Essential 8 MFA Requirements: What Counts, What Doesn't, and Phishing-Resistant MFA and SMS MFA retirement and passkey rollout

Frequently asked questions

What should an MSP do when a client refuses MFA?
Explain the risk once in plain English, offer an easier option such as a passkey or an authenticator app, and if the answer is still no, get the decision signed by a director. Record the date, the accounts affected and the date you will ask again.
Does a signed risk acceptance protect the MSP from liability?
It records that the client was told and chose the risk. It does not guarantee protection, because that depends on your contract and the facts. Ask your lawyer to review the template once, then reuse it.
Will the insurer accept a client who refuses MFA?
Do not assume so. Insurers commonly ask about MFA on the proposal form, and partial coverage is treated as a risk factor. The client signs the form, so the client must answer it truthfully. Under the Insurance Contracts Act 1984 the insurer's remedies depend on what was wrong, and a business policy carries a duty of disclosure.
Can I exclude a few accounts from MFA and still be honest on the form?
Yes, if the form answer says which accounts are excluded. A statement like 'MFA on all users' is false if three accounts are exempt. List the exceptions and the reason for each.
How often should I revisit a refusal?
Every 90 days at the latest, and before every insurance renewal. A refusal from last year does not describe the client today.