in this guide
For years, how people sign in to your tools was your decision. You turned MFA on, or you meant to. Since 2022 the big identity and SaaS vendors have started making that decision for you: MFA on admin portals, MFA for every password login, no more mail clients that sign in with a password alone. Each change is announced on the vendor’s site, rolled out tenant by tenant, and enforced on a date you did not pick.
The rule is right for people. The trouble is the accounts that are not quite people: a named user account that runs a nightly script, the emergency admin nobody has signed into since setup, the office scanner that sends mail with a stored password. These break on enforcement day, and the warning went to whoever holds an admin role, which at a 60-person company may be the founder, an IT person who left, or the outside provider.
This guide pairs with the identity you can’t offboard, which covers machine identities in general. This one is about the date someone else sets for them.
how a vendor change reaches your company
- 1vendor announcesA blog post or help page, months ahead, with a phased date.
- 2notice to adminsMessage Center, an email to admin roles, a console banner.
- 3nobody reads itThe admin inbox belongs to someone gone, busy, or outside.
- 4enforcement dayThe script, the scanner or the emergency login fails.
what the vendors changed, and when
Every item below comes from the vendor’s own announcement or documentation page, with the date shown there. Check the live page before acting: several of these dates have already moved.
Microsoft, admin portals. Microsoft’s mandatory MFA page says that from October 2024 MFA is required to sign in to the Azure portal, the Microsoft Entra admin center and the Intune admin center. The Microsoft 365 admin center followed: the Microsoft 365 blog of 11 November 2024 gave 3 February 2025 as the start. From 1 October 2025 the requirement extended to the Azure command line, PowerShell, the mobile app and infrastructure-as-code tools for any change to resources.
Microsoft, mail sent with a password. The Exchange team announced on 15 April 2024 that Basic authentication for SMTP AUTH, a sign-in method many older devices and small apps still use to send mail, would be retired in September 2025. That became a phased rejection from 1 March 2026 to 30 April 2026. The Exchange team’s post of 27 January 2026 moved it again: unchanged through December 2026, switched off by default for existing tenants at the end of December 2026 with an option to switch it back on, and a final removal date to be announced in the second half of 2027.
Google, password-only mail and calendar. Google’s Workspace Updates post of 29 September 2023 set 30 September 2024 as the end of “less secure apps”: password-only access over IMAP, POP, CalDAV, CardDAV and Google Sync. An update on 15 October 2024 paused it. Later updates gave 14 March 2025, then 1 May 2025.
Google, admin accounts. Google’s admin help page on 2-Step Verification enforcement says Google will require 2SV on all administrator accounts, rolling out gradually over several years and already under way for some editions. It publishes no single date. Each organisation is told on its own schedule.
Google Cloud. The Google Cloud blog of 5 November 2024 announced MFA for password sign-ins from early 2025, and for users who sign in through another identity provider by the end of 2025.
Okta. Okta’s security blog of 22 May 2025 says the Okta Admin Console now requires MFA, with the change dated August 2024 for new admin console policies.
Salesforce. Salesforce News reported on 1 February 2022 that Salesforce now requires all customers to use MFA, after giving notice a year earlier.
GitHub. The GitHub blog of 9 March 2023 announced that from 13 March 2023 everyone who contributes code would be required, group by group, to turn on two-factor authentication by the end of 2023.
AWS. AWS’s announcement of 17 June 2025 says MFA became required for root users of management accounts in May 2024 and standalone accounts in June 2024, and extends the rule to member accounts.
Snowflake. Snowflake’s documentation lays out three phases: MFA for people signing in to its web interface with a password (September 2025 to January 2026), then for new users (May to July 2026), then all users, with service users blocked from passwords altogether (August to October 2026). The Snowflake incident page covers what happened in 2024 to accounts protected by a password alone.
Every one of these changes is reasonable. None of them waited for your calendar.
what breaks first
The vendors’ own pages name the accounts that get caught. They are the same few kinds everywhere.
the sign-ins a vendor change hits
- people at a browserget a prompt, set up an app, carry on
- a user account running a scriptno one there to answer the prompt
- the emergency adminenforced like everyone else, rarely tested
- the scanner and the old appsend mail with a stored password
- the admin who signs in through SSOmay still need a second factor at the vendor
- the integration on a password flowan API login that cannot answer MFA
breaks on enforcement dayadapts
User accounts doing a machine’s job. Microsoft’s documentation says workload identities, meaning managed identities and service principals, are untouched by its enforcement, while a user account used to run automation has to complete MFA like any person. Microsoft also notes that the password-based token flow some older scripts use cannot do MFA at all. Snowflake goes further: by its third phase, service users cannot use a password. Google says service accounts do not need 2SV, but the admin account a service account impersonates does.
Emergency accounts. Microsoft’s page states that break-glass accounts must sign in with MFA once enforcement begins, and recommends a passkey or certificate for them. Its enforcement applies even to accounts you excluded in your own policies. Google says admins under its enforcement “cannot bypass it”, and that an admin who cannot enrol has to lose admin rights. An emergency account set up with only a password, kept in a safe, will meet that rule on the day you need it. The break-glass guide covers how to keep one working.
Devices and apps on old mail protocols. The scanner that emails PDFs, the accounting tool that sends invoices, the monitoring box that mails alerts. Microsoft’s SMTP AUTH change and Google’s less secure apps change both target exactly these. Microsoft lists OAuth, two of its own mail-sending services and a connector as the ways forward. Google suggested OAuth, or an app password for devices that cannot do OAuth.
Admins who sign in through SSO. Google’s help page says admins who sign in through another identity provider still need 2SV turned on in their Google account itself. A company with SSO everywhere can still have admins who have never set up a second factor at Google.
the dates move, and that is its own trap
Google moved its less secure apps cut-off three times between October 2024 and April 2025. Microsoft’s SMTP AUTH retirement has had three target dates, and the latest ends in a default you can reverse. Microsoft let tenants postpone its admin portal enforcement to 30 September 2025, and its command line enforcement to 1 July 2026.
Each move is a kindness to customers who were not ready. It also teaches everyone else that the date is soft. Somebody reads the first notice, sees the date pushed back, and stops reading. The final date arrives in a later update that nobody opened.
Postponing and switching something back on are decisions. Each needs an owner and a date written down. Microsoft’s own page puts it plainly: “There’s no way to opt out.”
who actually gets the warning
Vendors do warn, and their pages say how:
- Microsoft posts in the Message Center of the Microsoft 365 admin center about 30 days before a tenant is enforced, per the Microsoft 365 blog of 11 November 2024. For the Azure command line phase, the Azure blog of 5 September 2025 says notices went by email to all Global Administrators and through Azure Service Health.
- Google tells super admins about 90 days ahead and other admins about 60 days ahead, per its admin help page, by email, phone, sign-in reminders and a banner in the Admin console. After that come reminders at 7 days, loss of mobile app access at 15 days and loss of web access at 30 days.
- GitHub emailed people about 45 days before their deadline, per its blog of 9 March 2023.
Every one of these channels points at an admin role. Picture a 120-person company: the Global Administrators are the founder, the IT person who left in 2024, and two engineers at the outside IT provider. Microsoft’s notice reaches all four. The founder skims it, the ex-employee’s mailbox forwards nowhere, and the provider files it under the customer’s problem. The IT provider guide covers what the provider can do in your tenant. Notices are the part it usually does not read for you.
Nobody remembers why that rule exists describes the same loss with firewall rules: the reason survives only as long as the person who knew it stays. Here the lost fact is which scanner or script uses which account.
use the change as an inventory
A forced change is a cheap moment to find accounts nobody owns, because the vendor is pointing at them for you.
- Microsoft sign-in logs show which application enforced MFA on a sign-in, according to its mandatory MFA page, so you can see who hit the new rule.
- Google lets you add a “2-Step verification enforcement” column to the user list in the Admin console, per its help page, and enforcement starts the moment someone is given an admin role.
- Snowflake marks each user with a type, and its documentation ties the password ban to the service type.
The output is a short list: each account that would fail, who owns it, and what replaces its password. Most entries end in one of three ways. Move the job to a proper machine identity. Give the emergency account a hardware key and sign into it once. Retire the device or app that cannot change. The ten accounts that matter is a good companion list, because the registrar and cloud root accounts tend to be on both.
Which of your accounts would you rather find this week than on the vendor’s date?
sources
- Microsoft Learn: Plan for mandatory Microsoft Entra multifactor authentication (MFA), updated October 2026
- Microsoft Azure blog: Azure mandatory multifactor authentication, Phase 2 starting in October 2025 (5 September 2025)
- Microsoft 365 blog: Announcing mandatory multifactor authentication for the Microsoft 365 admin center (11 November 2024)
- Exchange Team blog: Exchange Online to retire Basic auth for Client Submission (SMTP AUTH) (15 April 2024, updated)
- Exchange Team blog: Updated Exchange Online SMTP AUTH Basic Authentication deprecation timeline (27 January 2026)
- Google Workspace Updates: Winding down Google Sync and Less Secure Apps support (29 September 2023, updated to 29 April 2025)
- Google Workspace Admin Help: About 2SV enforcement for admins
- Google Cloud blog: Mandatory MFA is coming to Google Cloud (5 November 2024)
- Okta Security: Okta's Secure by Design pledge, one year on (22 May 2025)
- Salesforce News: MFA the Salesforce way (1 February 2022)
- GitHub blog: Raising the bar for software security, GitHub 2FA begins March 13 (9 March 2023)
- AWS What's New: AWS IAM now enforces MFA for root users across all account types (17 June 2025)
- Snowflake documentation: Planning for the deprecation of single-factor password sign-ins
