Your business office manager turned on multi-factor authentication last year, and everyone felt better about it. Then one morning a staff member's mailbox starts sending odd messages, even though the code prompt was never approved. How? Often the answer is that the attacker never went through the front door. They used an older side entrance that does not ask for a code at all.
That side entrance is called legacy authentication. This article explains it in plain terms so administrators can ask the right question of their IT provider.
When a program signs in to your Microsoft 365 mailbox, it uses a method to prove who it is. Modern methods can pause and ask for a second step, such as an approval on a phone. Older methods, the kind used by older email programs and some older devices and scanners, send only a username and password and cannot ask for anything more.
Examples include older protocols for pulling mail (such as IMAP and POP), older ways of sending mail through SMTP with a password, and older versions of desktop Office. Microsoft has been retiring some of these for years, but they may still be switched on in a given organization, depending on how the tenant was set up and when.
If a password is stolen through a phishing email or reused from another breached site, the attacker tries it everywhere. Where a modern sign-in would stop and demand a code, a legacy protocol simply accepts the password. The multi-factor setting you paid for and trained staff on is then never consulted.
This matters in care settings because mailboxes hold resident names, referrals, family messages, payroll notes and invoices. A quiet sign-in through an old protocol can also leave less obvious trails than a normal login.
Nobody chooses to leave it on. It stays on because something old still depends on it. Common culprits:
A copier or scanner that emails documents to the nurses' station or business office.
An older fax-to-email service.
A third-party billing or reporting tool that sends mail on the organization's behalf.
An old phone or tablet using a built-in mail app that has not been updated.
A shared mailbox that a long-gone employee connected to an old program.
Blocking everything blindly can break the 6 a.m. scan-to-email that the dietary office relies on, which is why it needs planning.
You do not need to touch a setting. Ask these questions and expect clear answers:
Is legacy authentication blocked for all users in our Microsoft 365 tenant? If not, why?
If it is blocked, how is it blocked, for example through a policy that applies to everyone rather than one that can be skipped by certain accounts?
Before blocking, did you check sign-in records to see which accounts, devices and programs still use older methods?
Which of our scanners, copiers or other devices send mail, and have they been moved to a supported method?
Are there any exceptions, who approved them, and when will they end?
Who will we call if a device stops sending mail afterward?
Ask them to put answers in writing. A short email is enough for your records.
A sensible approach is to look first, then block. Your provider reviews recent sign-in history to see what is still using older methods, fixes or replaces what needs it, tests with a small group, then turns the block on for everyone. Some organizations apply the block in a report-only mode first so they can see what would break without breaking it.
Exceptions should be rare, narrow and temporary. An exception for "the scanner account" is better than one for the whole building, and the scanner should be moved to a safer method as soon as practical.
After the change, watch for scan-to-email failures and old phones that stop getting mail. Tell staff beforehand where to report problems.
If you do not have an IT person on staff, this still applies to you. The settings are the same whether you have ten mailboxes or a thousand. Ask once, ask in writing, and ask again after any new device or service is added.
UnityCare IT reviews Microsoft 365 sign-in methods for our clients, finds the scanners and older devices that still use them, and moves them to supported settings before turning the block on. We handle the change with your staff in mind, and our help desk is there if a device stops sending mail afterward.
Microsoft 365, cloud storage and tested backups with access controls built in.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support