←   All free Insights THE TECBUILDR365 FIELD GUIDE / 02

Security starts
with who gets in.

A practical guide to MFA, Microsoft Entra ID and smarter access controls. Understand what to protect, where to start and how to improve security without disrupting the working day.

✓ 100% free guidance✓ No sign-up required✓ Built for UK SMEs
FREE MICROSOFT 365 SECURITY HANDBOOKSTART READING   ↓
01 / START WITH THE BASICS

A password should never
be your only defence.

Your security doesn't start with a complicated product. It starts with identities: who has an account, how they prove who they are and what they are allowed to access.

01
✦

Verify the person

Use MFA and approved authentication methods to make stolen passwords less useful.

02
◎

Limit the access

Give people the permissions they need—not Global Administrator by default.

03
◇

Check the context

Consider the device, location, app and sign-in conditions before granting access.

04
↗

Stay prepared

Review sign-in activity, plan account recovery and practise your response before an incident.

!
MFA is essential—but not a magic shield.

It substantially improves protection against password-only attacks. Phishing-resistant methods provide stronger assurance than methods such as SMS. Device security, access control and staff awareness still matter.

Microsoft's MFA overview ↗
02 / CHOOSE THE RIGHT METHOD

Not all MFA is
created equal.

The aim is to make secure access workable for real people: office employees, engineers on the road and teams replacing lost devices.

01 / STRONGEST STARTING POINTPHISHING-RESISTANT
⌁

Passkeys & FIDO2 security keys

Designed to resist common phishing and credential-replay attacks. Especially worth prioritising for administrators and high-risk roles.

BEST FOR Privileged and sensitive access
02 / PRACTICAL STEP UPWIDELY USED
#

Authenticator app + number matching

An accessible choice for many staff. Teach users to reject prompts they did not initiate and report unexpected verification requests.

BEST FOR Most staff and remote workers
03 / FALLBACK WHERE NEEDEDLESS RESILIENT
···

SMS or voice verification

Better than a password alone in many situations, but more vulnerable to telecoms-based attacks and social engineering. Prefer stronger methods when possible.

BEST FOR Considered fallback scenarios
PRO TIP

Plan how someone signs in on their first day and how they recover access after losing a phone. Microsoft Entra Temporary Access Pass can help with secure registration and recovery when configured appropriately.

Read Microsoft's TAP guide ↗
03 / MAKE THE RIGHT DECISION

From sign-in to
smart access control.

Entra ID helps you decide whether to allow a sign-in, require stronger verification or block it—based on policies you set and the licences you have.

ILLUSTRATIVE ACCESS JOURNEY

One sign-in.
Several checks.

Think of Conditional Access as a policy decision, not just another password prompt.

01PersonWho is trying to sign in?
↓
02ContextWhich app, location and device?
↓
03PolicyWhich conditions must be met?
↓
✓DecisionGrant, challenge or block
THREE PRACTICAL STARTING POLICIESEXAMPLES
01

Require stronger sign-in for admins

Protect privileged roles with appropriate authentication strength and narrow policy scope.

02

Protect Microsoft 365 from legacy sign-ins

Identify legacy authentication dependencies first, then test and block outdated methods safely.

03

Control access from unmanaged devices

Where licensing and management support it, use compliant-device requirements for sensitive resources.

Don't skip the safety steps.

Configure emergency access exclusions, test with a pilot group, use report-only mode and check sign-in logs before enforcement.

FREE BASELINE

Security Defaults

Microsoft's simplified security baseline. No Entra ID P1 licence required, but limited customisation.

Good when simplicity is the priority
CONTROL & CUSTOMISATION

Entra ID P1 / Business Premium

Conditional Access can apply more tailored access decisions. Microsoft 365 Business Premium includes Entra ID P1.

Good for businesses wanting defined policies
ADVANCED RISK SIGNALS

Entra ID P2

Adds eligible risk-based Conditional Access and Identity Protection capabilities. Requires appropriate licensing.

Good for higher identity security needs

Security Defaults and Conditional Access are alternative enforcement approaches; don't assume both can be used together. Confirm exact Microsoft licensing, user coverage and current functionality before implementation. Security Defaults ↗ Conditional Access ↗ Free Licence Finder ↗

04 / FREE INTERACTIVE TOOL

How ready is
your business?

Take a five-minute self-check of your Microsoft 365 identity controls. Answer honestly: “not sure” is useful information. You'll receive a tailored priority list you can print or share.

YOUR 12-POINT READINESS REVIEW

Choose one answer per safeguard. Nothing is sent to us.

◇ PRIVATE BY DESIGN
01Every user has MFA

MFA protects all interactive user sign-ins, including remote staff and shared-device workers.

02Administrators have stronger sign-in protection

Privileged accounts use phishing-resistant MFA where feasible, separate admin identities and minimal role assignments.

03Emergency access accounts are documented

Two cloud-only emergency access accounts are secured, excluded from accidental lockout policies, monitored and tested.

04Legacy authentication is reviewed

Any apps, printers or scripts using outdated authentication are identified and migration or blocking is planned.

05Security Defaults or Conditional Access is deliberate

Your team knows whether it uses Microsoft Security Defaults or licensed Conditional Access policies and why.

06Conditional Access changes are safely staged

New policies use report-only testing, staged groups and documented emergency access exclusions.

07Users have secure recovery options

People can register approved methods and know how to recover access when a device is lost or replaced.

08Joiners, movers and leavers are controlled

A repeatable process grants appropriate access, changes roles and promptly removes departing users.

09External and guest access is reviewed

Guests, shared resources and external collaborators are reviewed for continued business need.

10Sign-in alerts and audit trails are examined

The right people know how to review sign-in failures, suspicious events and privileged activity.

11Devices and access rules are aligned

The team understands whether device compliance is required and which Microsoft licences support that rule.

12Staff understand phishing and MFA prompts

Employees know not to approve unexpected prompts and how to report suspicious sign-in requests.

Educational self-assessment, not a certified security audit.
05 / IMPLEMENT WITHOUT SURPRISES

A safer rollout.
A smoother Monday.

Rolling out MFA and access controls is a people project as much as a technical one. This is the sequence we'd plan around for a small business.

01

Discover the current setup

Review tenant licences, users, admin roles, apps, authentication methods, guests and known business-critical dependencies.

DISCOVER
02

Secure recovery first

Establish and validate emergency access accounts; define lost-device and new-starter recovery procedures.

PREPARE
03

Choose a suitable authentication policy

Confirm Security Defaults versus Conditional Access, scope, exclusions and whether P1/P2 features are actually licensed.

DESIGN
04

Start with a pilot

Test with different job roles and devices; use report-only policies and investigate sign-in outcomes before broad enforcement.

TEST
05

Explain what users will see

Send a clear registration guide, offer an accessible support route and teach users to reject unexpected MFA prompts.

ENABLE
06

Monitor, support and improve

Check adoption and sign-in errors, manage exceptions and review permissions and risk over time.

IMPROVE
COMMON MISTAKES

What we'd avoid.

  • Switching on a blanket access policy without testing
  • Locking out the only administrator
  • Forcing staff to enrol without communication or support
  • Assuming MFA protects every application and protocol
  • Paying for P2 capabilities without checking who needs them
06 / THE QUESTIONS WE HEAR

Good questions.
Plain-English answers.

Practical answers for people responsible for Microsoft 365, whether you're the office manager or the person who looks after your IT.

Do we need Business Premium to use MFA?+

No. MFA is not exclusive to Business Premium. However, tailoring access through Conditional Access requires an appropriate Entra ID P1 entitlement; Business Premium includes P1.

Is an authenticator app enough?+

Authenticator with number matching can be a practical improvement over passwords. Phishing-resistant passkeys or FIDO2 security keys offer stronger protection, especially for admins.

What if an employee loses their phone?+

Plan a verified recovery route before rollout. Supported options can include alternative registered methods or an administrator-issued Temporary Access Pass, subject to configuration and policy.

Should we turn on every Conditional Access rule?+

No. Policies should be risk-based, licensed, tested and appropriate for how your team works. Report-only testing and emergency access are essential safeguards against accidental lockouts.

What's the difference between Entra ID P1 and P2?+

P1 supports Conditional Access. P2 adds advanced capabilities, including eligible risk-based Conditional Access through Identity Protection. Review entitlement for the exact users and features you need.

Can we secure road-based engineers differently?+

Yes, your access approach can consider different roles, devices and apps. Design policies around real work scenarios rather than forcing everyone into the same device or app restrictions.

Will turning on MFA stop all phishing attacks?+

No. MFA reduces risks, but attackers can still target sessions, approvals and users. Phishing-resistant MFA, email security, device protection and training work together.

Can we do this without an expensive project?+

Start with an inventory, admin protection and a manageable plan. Some security improvements use features you already have. Scope licence requirements and rollout time before committing.

GO DEEPER / FREE REFERENCES

Good advice should
be easy to verify.

Useful Microsoft documentation and our related guides. No account, download gate or sales meeting required.

Reviewed October 2026. Security configurations, feature availability and licensing can change; verify Microsoft's current documentation and your tenant's entitlement before making changes. The guide provides general educational information, not an audit of your systems.

READY WHEN YOU ARE

Security that's stronger.
Without the complexity.

Start with a free check, explore the right Microsoft 365 licences or talk through a sensible plan for your organisation.

✓ Helpful, not high pressure✓ Right scope, right licence