Skip to content

Blog

SSO vs MFA: do you need both?

MFA vs SSO: SSO cuts your logins to one, MFA makes that login hard to steal. How they differ, how they combine, and which a small team should turn on first.

· 8 min read

MFA vs SSO comes down to this: SSO cuts the number of logins down to one; MFA makes that login much harder to steal. Single sign-on decides where people prove who they are: once, at your identity provider, instead of at every tool. Multi-factor authentication decides how: with a password plus something else, such as a code, a phone prompt or a security key.

They are not alternatives. They solve different halves of the same problem, and they work best together. If you can only do one this month, do MFA.

The difference

SSO (single sign-on) is an arrangement between your identity provider (Google Workspace, Microsoft Entra ID, Okta) and your tools. The tool stops checking passwords and accepts a signed statement from the identity provider instead. Result: one account, one login page, one place to suspend someone. What SSO is has the full explanation.

MFA (multi-factor authentication) is a rule about what a single login requires. A factor is a kind of evidence, and there are three kinds. Something you know is a password or PIN. Something you have is your phone, an authenticator app or a hardware security key. Something you are is a fingerprint or face, usually used to unlock the thing you have rather than sent anywhere.

MFA means at least two different kinds. 2FA (two-factor authentication) is the same idea with exactly two, and in everyday use the terms are interchangeable. So "SSO vs 2FA" is the same question as "SSO vs MFA". Two passwords are not two factors, by the way: they are both something you know, and both can be phished from the same fake page.

SSOMFA
Question it answersWhere do people log in?What does a login require?
Main benefitOne account to protect, manage and suspendA stolen password alone is not enough
Main risk it addsOne account now opens everythingLockouts when someone loses their phone
Usual costOften a higher plan in each toolFree in most identity providers and many tools
Stops leavers?Blocks new logins; does not remove accountsNo

How SSO and MFA combine

With both in place, a login looks like this: someone opens Slack, Slack sends them to your identity provider, the identity provider asks for their password and their second factor, then vouches for them to Slack. How SSO works walks through each step. Three things follow from that arrangement.

MFA moves to one place. You set it once, in the identity provider, and every connected tool inherits it. Slack's own help center says that if you use SSO, 2FA should be set up through your identity provider, and that a member's Slack 2FA is turned off when they connect their SSO account.

The identity provider account becomes the crown jewel. With SSO, one login opens every connected tool. That makes MFA on the identity provider non-negotiable. SSO without MFA concentrates risk; SSO with MFA concentrates protection.

The quality of the second factor starts to matter. Codes sent by SMS and one-time codes typed into a page can be phished: a fake login page asks for both and replays them. Passkeys and hardware security keys are tied to the real site's address, so a fake page cannot use them. If you are setting rules in one place anyway, set strong ones there.

Does SSO include MFA? Not by definition. SSO protocols carry the result of a login, not the method. But every mainstream identity provider offers MFA, and some SSO protocols can report which method was used (OpenID Connect has a claim for it; see what OIDC is). In practice, buying SSO almost always means also turning on MFA, which is why the two get confused.

MFA without SSO: per-tool MFA

You can have MFA without SSO, and most small companies should start there. There are two ways.

MFA on the account people already use to sign in. If your people log in to tools with "Sign in with Google" or "Sign in with Microsoft", enforcing 2-Step Verification in Google Workspace, or MFA in Microsoft Entra ID, protects every one of those logins at once. This is the closest thing to SSO-plus-MFA that costs nothing, though it is not enforced in the tools: anyone with a separate password account in a tool skips it.

Both directories give you real control here. Google's 2-Step Verification deployment guide, as we read it on 27 October 2026, lets an admin enforce any method, any method except codes by text message or phone call, or only security keys, an option it says now covers passkeys too. It also lets you give new users an enrollment period of between one day and six months, during which they can sign in with just a password. On the Microsoft side, Entra ID's security defaults need no paid license, per the same page that day: they require every user to register for MFA, require administrators to use it, and block older sign-in protocols that cannot do MFA at all. Microsoft Entra ID pricing covers what the paid tiers add on top.

MFA in each tool. Many tools let an admin require two-factor authentication for everyone in the workspace. Two examples from the vendors' own help pages, read on 27 October 2026: Slack says mandatory workspace two-factor authentication is available on all plans, and members who do not set it up within 24 hours are signed out until they do. GitHub lets organization owners require 2FA for members; members who do not enable it cannot access the organization's resources, but keep their membership and still take up a seat.

The downside of per-tool MFA is the count. Twenty tools means twenty settings to turn on, twenty places to check, and people juggling a dozen entries in their authenticator app. It works, and it is free, but it does not scale gracefully.

Which to do first

MFA, almost always. The reasoning is plain. Passwords leak: they get phished, guessed and reused from other sites' breaches, and MFA stops a password on its own from being enough, while SSO alone just means one password unlocks more. MFA is cheap: Google Workspace and Microsoft 365 include it, and many tools include enforced 2FA on the plan you already have, whereas SSO often means moving every seat in a tool to a higher plan, the SSO tax. And MFA is quick: turning it on for your identity provider is an afternoon, plus helping the people who lose their phones.

A sensible order for a small team looks like this.

Enforce MFA on the directory first. Turn it on in Google Workspace or Microsoft 365 for everyone, starting with admins. Our Google Workspace security checklist covers the settings around it.

Raise the bar for the accounts that matter most. Prefer passkeys or security keys for admins and finance, and avoid SMS where you can.

Route logins through the protected account. Use "Sign in with Google" or "Sign in with Microsoft" wherever a tool offers it, so those logins inherit your MFA.

Cover the stragglers. Turn on required 2FA in the tools that sign people in with their own passwords.

Then, and only then, add enforced SSO for the tools where a customer or an auditor requires it, or where the risk justifies the upgrade.

Common mistakes with MFA and SSO

Exempting the people who complain. The founder who finds codes annoying is usually the account an attacker wants most. Exceptions for senior people are how MFA rollouts fail quietly.

Leaving password login on behind SSO. If a tool still accepts its own password, anyone who has one skips your identity provider and its MFA. Enforced SSO means switching that off.

Having no way back in. Microsoft's security defaults page recommends two cloud-only emergency access accounts with the Global Administrator role, kept for the day every other admin is locked out. Whatever your directory, know how an admin recovers before you enforce anything.

Forgetting shared logins. A shared social media account or a registrar login cannot sit behind SSO, because SSO is per person. Those need MFA in the tool itself and a home in a password manager; shared accounts at work covers how to handle them, and SSO vs a password manager explains why most teams need both.

The gap neither closes: removing people

Here is the part that catches companies out. Neither SSO nor MFA removes anyone from anything.

MFA protects a login. It does not care whether the person logging in still works for you: a leaver with their phone and their password passes MFA perfectly. SSO blocks new logins once you suspend the person in the identity provider, but their accounts in each tool stay, with their data, their access tokens and often a paid seat, and open sessions on their laptop or phone can keep working until they expire. And neither covers tools outside them. Any tool with its own password and no SSO keeps working for whoever knows the password.

Removing accounts is provisioning's job, usually via SCIM, usually on an even higher plan (SCIM vs SAML). Or it is someone working through an employee offboarding checklist by hand.

Where SmashSSO fits

SmashSSO is neither SSO nor MFA. It does not touch logins, and your identity provider's MFA rules stay exactly as they are.

It covers the gap above. It reads your people from Google Workspace with read-only access and shows who has an account in each tool, with what role. When someone is suspended in Google Workspace, it alerts you and shows every tool where they still have access, and it removes them through the tool's member API where you have added a token, or through an agent in your own Chrome, in tabs where you are already signed in as an admin. That browser has to be open, agent runs are slower than an API and can fail when a tool redesigns its screens, and every change is recorded in an audit log.

It costs a flat fee from $199 a month billed annually (pricing). Turn on MFA first, whatever else you do. If you need enforced login through an identity provider, you need SSO too.

FAQ

Is SSO the same as MFA?
No. SSO decides where people log in: once, at your identity provider, instead of at every tool. MFA decides what a login requires: a password plus a second factor such as a code, a phone prompt or a security key.
Does SSO include MFA?
Not by definition, but in practice they come together. The identity provider handles the login, so MFA you enforce there applies to every connected tool. Without MFA, SSO means one stolen password opens everything.
Can I have MFA without SSO?
Yes. Enforce it on Google Workspace or Microsoft 365, which protects every "Sign in with Google" or "Sign in with Microsoft" login, and require 2FA inside tools that offer it. Microsoft's security defaults turn on MFA in Entra ID without a paid license.
Which is more important, SSO or MFA?
MFA, for most small teams. It stops a stolen password from being enough, it is cheap or free, and it takes an afternoon. SSO is worth adding where a customer or auditor requires it or the risk justifies the tool upgrades.
Is SSO vs 2FA a different question?
No. 2FA is MFA with exactly two factors, and in everyday use the terms are interchangeable. Two passwords do not count as two factors, because both are something you know.

Keep reading

Stop paying for a login button.

Sign in with Google Workspace, connect your tools, and see who has access to what in minutes.

Sign up with Google