Skip to content
DYNACLOUDAFRICA

A pragmatic Conditional Access baseline for Entra ID

The handful of policies that stop most identity attacks — and how to roll them out without locking anyone out.

DynaCloud Africa · · 1 min read

Conditional Access is the policy engine at the heart of zero trust in Microsoft Entra ID. It’s also very easy to misconfigure. Here’s the baseline we start most organisations with.

The core policies

  1. Require MFA for all users — with phishing-resistant methods for administrators.
  2. Block legacy authentication — older protocols can’t do MFA and are a favourite of attackers.
  3. Require compliant or hybrid-joined devices for access to sensitive apps such as Dynamics 365.
  4. Sign-in risk and user risk policies to step up or block suspicious activity (these need Microsoft Entra ID P2).
  5. Restrict admin portals to privileged roles on trusted devices.

Rolling out safely

  • Create two emergency access accounts excluded from policies and monitor their use.
  • Run every new policy in report-only mode first and review the sign-in logs.
  • Roll out in waves — IT first, then pilot groups, then everyone.
  • Communicate early, with clear instructions for registering MFA methods.

Don’t forget the apps

Conditional Access protects the front door, but application security still matters. For Dynamics 365 and Power Platform, align policies with security roles and environment access so the right people reach the right data from the right devices.

Ready to modernise how you serve customers?

Tell us where you are today. We’ll come back within one business day with practical next steps — no hard sell.