Do mandatory passkeys bypass traditional two-factor authentication?
Mandatory passkeys can completely bypass traditional two-factor authentication with a single button click if a computer is left unlocked. This leaves systems vulnerable to internal actors and agents that can inflict damage regardless of scoped access or marketing claims about sandboxing.
Core Friction Pattern
Analysis of 8 peer accounts across online developer and community forums reveals that “Do mandatory passkeys bypass traditional two-factor authentication?” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
+17 alternative community-tested workarounds cataloged below.
What the numbers show
Counted from the threads quoted below. How we count
- Most of it landed at once — the busiest month was September 2026, with 5 people.
- This comes up 61.5× more often in r/msp than across the site as a whole.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
Do mandatory passkeys bypass traditional two-factor authentication?
- 1patching exploits as soon as possibleDid this help you?
- 2utilizing network segmentationDid this help you?
- 3moving to strong encryption 2FA, and current best practice password policiesDid this help you?
- 4planning for failure as a foregone conclusion and planning for recoveryDid this help you?
- 5Using hardware passkeys like Yubico or Token2 that require a PINDid this help you?
- 6Falling back to traditional security methods like password reset by email where supportedDid this help you?
- 7Storing passkeys in password managers that require biometrics or a PINDid this help you?
- 8using device filters instead of device compliance rulesDid this help you?
- 9setting up separate browser profiles for admin accountsDid this help you?
- 10implementing Privileged Identity Management (PIM) with timed activationDid this help you?
- 11storing break-glass account passwords offline in physical safesDid this help you?
- 12Ask what business problem they are trying to solve and offer a secure alternative like an email export or delegate access.Did this help you?
- 13Explain the extensive risks (like giving access to all connected files and systems) to deter them.Did this help you?
- 14Make the client reset and share the password themselves, then immediately force a reset, revoke sessions, and check for forwarding rules when the third party is done.Did this help you?
- 15Create a temporary account with delegate access for the third party.Did this help you?
- 16Checking specific admin center settings manuallyDid this help you?
- 17Using checklists for partner relationships, enterprise apps, and service accountsDid this help you?
- 18Transitioning helpdesk staff to separate admin accounts with PIM activation linked to ticketsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“Client asking us to give his M365 email password so he can share it with his solicitor!!!”source ↗
“Whilst we can reset his password , we want to cover ourselves, and he can do whatever he wants to. Is there a waiver template anyone could share.”source ↗
“I would not put my name on a waiver for this one. A signed waiver does not really protect you if you hand over a credential you know should not be shared, and it still leaves you in the middle if anything goes sideways in that mailbox.”source ↗
“I found this by accident and was shocked when I investigated.”source ↗
“However, when I login it complains that I'm not logged in to the GA-account in Edge since I'm logged in as my regular user.”source ↗
“I have not seen the attack I am worried about. agent poisoning at the LLM level. The attacker will already be in the building and even if access is scoped correctly damage will occur.”source ↗
“how did it find credentials if it was sandboxed? Or is sandboxed just a general term to make CEO's and investors think the latest Frankenstein just broke its chains”source ↗
“With how frequently there are bugs for Intune Compliance detection (currently waiting for the antivirus check to work correctly again), I use a device filter instead filtered for AAD Join rather than rely on a device being marked compliant.”source ↗
“A bunch of tools we use are rolling out passkeys as mandatory instead of password/2FA requirement.”source ↗
“A user leaves their computer unlocked. A bad actor enters the user's email address on their computer. They click the one button to use the passkey. 2FA never played a factor in that login, it's barely even one factor...”source ↗
Where this came up
People with this problem also raised
Related community dilemmas clustered by discussion consensus
Locked out of new network switches because the consultant left
When an external consultant configures network gear and leaves without handing over the login credentials, incoming administrators are completely locked out of the equipment. This prevents anyone from managing the infrastructure or performing basic upkeep until the original configurator returns.
Can't log into AWS console with root email
The system redirects you to a Builder ID sign-up page without warning, prompting you to create a new password. This prevents you from logging into your AWS console with your original root email. Fixing the issue is frustrating, as support chats can remain unresponsive for 30 minutes or more.
How do you manage accounts and passwords that don't use SSO?
Break-glass accounts, contractor logins, and apps without SAML or OIDC often end up scattered in shared vaults, duplicated across teams, or owned by someone who leaves the company. Without a way to rotate, audit, or assign clear ownership, these credentials become a compliance risk and a single point of failure during critical deadlines.
Staying logged into apps when your identity provider goes down
Centralizing login through a single identity provider leaves you vulnerable when it fails, and authenticator apps can stop working during an outage. Long token lifetimes and offline access policies only buy a few hours of breathing room before access drops, and many SaaS apps do not support break-glass accounts or alternate login methods. Past 12 hours of downtime, businesses that rely on that provider can be brought to a standstill.
Why does accounting software force logins for every company file?
Desktop accounting software often forces users to tie multiple separate business files to a single online account, creating intense anxiety about losing access to older company data or violating subscription terms. This forced login structure traps users into cumbersome migrations and prevents them from managing distinct legal entities independently on a single machine.
How to clean up a hacked website and fix malware
Website hacks manifest as random redirects, injected footer scripts, and unexpected user logouts that force owners to spend entire weekends manually scanning files and troubleshooting PHP functions at 3 AM. This demanding clean-up process stems from neglecting basic security hardening before the breach occurs, leaving sites entirely vulnerable to compromises.