Skip to content
iTekConnect

EP 030 / Companion article

Conditional Access: Four Questions Before You Enable More Policies

Conditional Access: Four Questions Before You Enable More Policies

I group Conditional Access planning into four questions rather than treating twenty policies as switches to turn on at once. This episode is a planning explainer: the boards are illustrative, and they do not prove enforcement in a tenant.

Who is signing in?

Start by reviewing legacy authentication, MFA coverage and administrator access. Decide which people, groups and resources a policy should cover, and document the recovery path.

What device and application are they using?

Device compliance, mobile app protection and unmanaged access requirements serve different purposes. Check the relevant app and platform support before choosing controls.

What does risk tell you?

Keep sign-in risk and user risk distinct. Match session controls to the application and user experience. Conditional Access generally requires Microsoft Entra ID P1; risk-based policies require P2, and connected services can have separate licensing requirements.

How does authentication happen?

In the full episode I also discuss device code flow, authentication transfer, token protection and sensitive administrator actions. Treat each as a scoped design decision that needs support checks and testing.

My rollout approach

Choose one gap, assign an owner, preserve emergency access, and test a small pilot. Use report-only where supported to understand potential impact; observation is not proof of an enforced sign-in outcome. Record expected access, expected denial and recovery before expanding.

Watch the full episode for the twenty policy purposes and use the four questions to organize your own review.

Primary sources

Take it with you

Related resources.

No downloads are attached to this article yet.

Start with a discovery conversation

What could work better?

Discuss a project