
www.simplify-data.de
Entra ID (formerly Azure AD) is the sign-in hub of Microsoft 365. In many small and mid-sized companies it still means password plus SMS, old mail protocols and a Global Admin who uses the same account day to day. Conditional Access sounds like an enterprise licence and weeks of consulting. A solid minimum, however, is achievable with Microsoft 365 Business Premium and the built-in security features, as long as you follow the right order. This article describes a path for SMEs without a corporate project (as of November 2026).
Why MFA alone is not enough
According to Microsoft, multifactor authentication blocks the vast majority of identity-based attacks. It only helps if it actually applies everywhere.
Old protocols bypass MFA
Legacy authentication (for example IMAP, POP3 or older Office clients) does not support multifactor authentication. An attacker can sign in through it even though MFA is switched on. As long as these paths stay open, the protection has a gap.
Admins, guests and sign-in conditions
Other typical weak spots are admin accounts used for email and browsing, guest accounts without an expiry date, and sign-ins from any country and unknown devices. That is why MFA and access conditions belong together. Conditional Access checks who is signing in, from where and with which device before access is granted.
What your licence includes
| Building block | Licence | Purpose |
|---|---|---|
| Security defaults | no extra cost, no premium needed | fixed baseline protection without customisation |
| Conditional Access | at least Entra ID P1, included in Microsoft 365 Business Premium | targeted rules instead of all-or-nothing |
| Risk-based policies (ID Protection) | Entra ID P2 | automatic response to risky sign-ins |
| PIM (time-limited admin rights) | Entra ID P2 | admin rights only when needed |
Business Premium is enough for a solid foundation. P2 features are an add-on, not a prerequisite.
Step 1: security defaults as a starting point
If you have no rules of your own yet, switch on security defaults first. They require MFA for all users and administrators, block legacy authentication and device code flow, and protect access to Azure management portals. They cannot be customised, though. Check beforehand whether printers, scanners or line-of-business applications still use old mail protocols, otherwise those devices lose access. Microsoft generally considers security defaults no longer a good fit for tenants with premium licences and more complex requirements.
Step 2: Conditional Access with a few rules
Once you have P1, replace the defaults with your own policies. Security defaults must be disabled for that. Microsoft provides pre-configured policies that reproduce the same protection. Most SMEs need no more than five production rules:
- Admins: always MFA, ideally phishing-resistant (passkey or FIDO2 security key).
- All users: MFA for all cloud apps.
- Block legacy authentication: for all accounts.
- Guests: require MFA and limit access to the apps they need.
- Risky sign-ins (with P2): extra factor or block.
Test in report-only mode first
Every new rule starts in report-only mode. After a few days the sign-in log shows who the rule would have affected. That way you do not lock accounting out on the last day of the month.
Setting up emergency (break glass) accounts correctly
Two emergency accounts prevent you from locking yourself out of the tenant, for example if all admin devices fail. Microsoft recommends:
- at least two cloud-only accounts on the onmicrosoft.com domain, not tied to individual people
- the Global Administrator role permanently active, not just eligible
- sign-in with a passkey (FIDO2), long-lived and different from your normal admin accounts; this method also satisfies the mandatory MFA for admin portals
- exclusion from policies that block or restrict sign-in; the passkey provides the protection
- an alert on every sign-in of these accounts
- a test at least every 90 days
Emergency accounts are therefore not an MFA-free entry point but one that uses a different, particularly strong factor.
Separate admin accounts
Use dedicated accounts for administration, separate from the daily mailbox. This reduces MFA prompts and prevents a single phishing click in everyday work from handing over admin rights.
Typical pitfalls in everyday SME life
Devices and services with old credentials
Multifunction printers, scan-to-mail, ERP or monitoring tools often send email via old protocols. If you block these paths without knowing about them, they fail silently. Check the sign-in log at least two weeks before the switch and move affected devices to modern methods.
Bringing staff on board
MFA rarely fails because of technology in everyday use, but because of missing preparation. Inform the team in advance, briefly explain how to register the authenticator app and have a contact person ready on launch day. This saves queries and prevents exceptions from creeping in out of convenience.
Checklist
- Reduce the number of Global Admins and separate admin accounts from daily accounts.
- Security defaults or Conditional Access active, never both at once.
- Find legacy authentication in the sign-in log, clarify dependencies and block it.
- Replace SMS as a second factor with an authenticator app or passkey where possible.
- Set up two emergency accounts with a FIDO2 passkey and enable an alert on use.
- Start new policies in report-only mode, then enforce them.
- Review guests regularly and remove unused ones.
- Apply the same principles to VPN and mail access.
How Simplify Data can help
We harden Entra ID tenants for SMEs: MFA, a few Conditional Access rules, emergency accounts and cleaning up admin rights. We also combine this with zero-trust access to your company network. Managed Services, Zero Trust VPN or get in touch.