Skip to content

Identity and access security notes. What to check, and what to fix first.

Identity is where most Microsoft 365 security control actually lives. These notes cover Conditional Access rollout, MFA scope, passkeys, admin sprawl, OAuth consent, password spray defence and the boring break-glass design that saves you when policy goes wrong.

Notes on this topic

Short guides on what to check and why it matters.

What MFA changes

In Microsoft’s study of business accounts, MFA cut the risk of compromise by more than 99%.

99.22%lower risk of account compromise with MFA on
98.56%lower risk even where the password had already leaked
Relative risk of compromise
  • Without MFA100
  • With MFA0.78
Source: How effective is multifactor authentication at deterring cyberattacks? (opens in a new tab), Microsoft (Meyer et al.), May 2023. Microsoft Entra ID business accounts.

How attacks get in

Phishing is by far the most common attack on UK businesses. Stolen passwords are what identity controls protect.

38%of UK businesses were targeted by phishing in the last 12 months
69%of breached organisations named phishing their most disruptive attack
Types of attack businesses reported
  • Phishing38%
  • Impersonation in emails or online12%
  • Malware on devices7%
  • Online bank account hacking3%
  • Denial of service3%
  • Account takeovers2%
  • Ransomware1%
Source: Cyber Security Breaches Survey 2025/2026 (opens in a new tab), DSIT and Home Office, April 2026. UK businesses.

Entra ID & Conditional Access

Bring a named admin role list, the current Conditional Access policies, any recent audit log concerns and the last time access exceptions were reviewed. Guest users and OAuth app consents are worth listing separately.

See the related service

Ask yourself first

If any of these is hard to answer, a review will help. Move from reading to action when access rules are trusted by memory rather than evidence. Identity controls need a clean map before enforcement gets tighter.

  1. 01

    Are Conditional Access policies documented, tested and owned by someone current?

  2. 02

    Do privileged roles, guests, OAuth apps and break-glass accounts have a review habit?

  3. 03

    Can the team explain why each MFA exception still exists?

Common questions

What does a review look like?

A typical review maps admin roles, MFA methods, Conditional Access policies, exclusions, guest users and break-glass accounts so the team can see which access paths are intentional and which are inherited drift.

Keep exploring

Ready to turn this into a scoped review?

Start a conversation