<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mfa on Jeremiah Windle</title><link>https://7f57629a.jeremiahwindle.pages.dev/tags/mfa/</link><description>Recent content in Mfa on Jeremiah Windle</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 28 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://7f57629a.jeremiahwindle.pages.dev/tags/mfa/index.xml" rel="self" type="application/rss+xml"/><item><title>Entra ID Conditional Access: Real Policies, Real Scenarios, What to Actually Enforce</title><link>https://7f57629a.jeremiahwindle.pages.dev/blog/conditional-access-policies/</link><pubDate>Sat, 28 Feb 2026 00:00:00 +0000</pubDate><guid>https://7f57629a.jeremiahwindle.pages.dev/blog/conditional-access-policies/</guid><description>Conditional Access is one of those features where the gap between &amp;ldquo;we have it enabled&amp;rdquo; and &amp;ldquo;we have it configured correctly&amp;rdquo; is wide enough that attackers drive through it regularly. I&amp;rsquo;ve managed CA policies across 100+ organizations at two MSPs. Here&amp;rsquo;s the framework I&amp;rsquo;ve landed on.
The Foundation: What CA Actually Is Conditional Access is Entra ID&amp;rsquo;s policy engine. Every sign-in attempt hits it, and the policy evaluates conditions — who is signing in, from where, on what device, to what application — and makes a decision: allow, block, or allow with requirements (MFA, compliant device, etc.</description></item></channel></rss>