Four Microsoft 365 Security Settings We Fix on Almost Every New Client Account
If you set up Microsoft 365 yourself, or had someone set it up years ago and haven’t touched the security settings since, there’s a good chance you’re carrying at least one of four common gaps. We see them on almost every new client account we take over. None of them are obscure. They just never get cleaned up because the account keeps working fine until it doesn’t.
Here’s what to check.
MFA for everyone, not just some people
Multi-factor authentication is the single most effective thing a small business can do to protect its accounts. Microsoft’s data shows that more than 99.9% of compromised accounts didn’t have MFA turned on.[1] That number has held steady across several years of their reporting, and it still holds up.
The gap we see isn’t that businesses haven’t heard of MFA. It’s that it got turned on for some accounts and not others. The admin has it. The owner has it. But the person in accounts payable who was added during a busy week three years ago? Nobody went back to check.
In Microsoft 365, MFA lives under Security > Authentication > Multi-factor authentication. If you’re on a Business Premium plan, Conditional Access policies are the right way to enforce it across all accounts. The setup takes about 20 minutes. The protection it adds is not marginal.
Shared logins need to go
A lot of small businesses have one or two email addresses where multiple people log in with the same username and password. It makes sense at first. Everyone needs to see the info@ inbox. But shared logins mean no audit trail, no way to remove one person’s access without changing the password for everyone, and no option to enforce MFA on that account.
The right approach in Microsoft 365 is a shared mailbox. Everyone keeps their own account and gets delegate access to the shared inbox. They sign in as themselves. Their individual actions are traceable. Microsoft includes shared mailboxes in standard Microsoft 365 Business plans at no extra cost.[4]
One thing to get right: the shared mailbox has a backing user account in Entra ID. Block sign-in on that account. The Center for Internet Security’s Microsoft 365 Foundations Benchmark flags this as a Level 1 control.[2] Level 1 means basic. If you don’t block it, that account is a sitting target with a static password and no MFA option, which makes it one of the more attractive ways into a tenant.
Your admin account and your email account should be separate
If you manage Microsoft 365 for your business, your account probably has Global Administrator access. If that’s also the account you use for your regular email and Teams messages, then one stolen session token gives an attacker admin-level control over your entire tenant. They can create new accounts, change passwords, turn off security policies, and read everyone’s email.
The fix is a second account used only for admin tasks. It doesn’t need a license. It doesn’t need email. You log in, make the change you need, and log out. It’s a bit of a hassle to maintain. But it’s also why a phishing link clicked on a Tuesday afternoon doesn’t turn into a tenant-level incident.
We handle Microsoft 365 setup and security as part of our managed IT onboarding, and separating admin accounts is always one of the first things on the list.
When someone leaves, closing the account isn't the whole job
A Beyond Identity survey found that 83% of former employees admitted to still accessing accounts at their previous employer after leaving.[3] That’s not always malicious. Sometimes the access was just never removed.
Blocking sign-in on someone’s Microsoft 365 account is a start. It’s not the whole job. Here’s what full offboarding actually looks like:
- Block sign-in on their account
- Revoke active sessions (this invalidates any tokens they may have cached before you disabled the account)
- Remove them from distribution groups and shared mailboxes
- Transfer any mailbox content you need before the account expires
- Review what licenses, apps, and third-party integrations they had access to
Microsoft 365 won’t alert you when a former employee still has delegate access to a shared mailbox through a group membership. That part requires a manual review. Worth running any time someone leaves, even on good terms.
None of this requires a large IT budget or a formal security audit. These are defaults that should have been set on day one. If you’re not sure where your account stands, now’s a good time to check.
Not sure if your Microsoft 365 is configured the right way? We can run through it with you. Reach out here or call us at (412) 307-8313.
- Microsoft, “Microsoft Digital Defense Report 2025,” microsoft.com
- Center for Internet Security, “CIS Microsoft 365 Foundations Benchmark,” control 1.2.2: Ensure sign-in to shared mailboxes is blocked (Level 1), cisecurity.org
- Beyond Identity, “Former Employees Admit to Using Continued Account Access to Harm Previous Employers,” 2021, beyondidentity.com
- Microsoft Learn, “About shared mailboxes,” learn.microsoft.com