Why do Conditional Access changes seem to take so long?

November 16, 2026 3 answers
Asked by 6w~hexspool_293

When I change a Microsoft Entra Conditional Access policy, it can take 20 to 30 minutes to settle. During that time, sign-ins sometimes alternate between matching the old and new policy. What could cause that?

Answers

Kavrin.5b

A plausible explanation is that the change takes time to propagate through a distributed service. If different sign-in requests are evaluated using different copies or caches of the policy, some could see the old version while others see the new one.

That fits the intermittent behavior, but it doesn't prove which part of Microsoft's infrastructure is responsible. The discussion doesn't establish that Entra Conditional Access is evaluated by traditional Active Directory domain controllers, for example.

Reply to this answer
_j82~fusebasket.4

Check the individual sign-in records rather than just whether the login succeeded. Compare the time, account, application, Conditional Access result, and policies listed for each attempt. Also give the logs time to appear before drawing a conclusion, since delayed records can make the sequence harder to read.

If the same kind of sign-in keeps showing inconsistent results after the change has had time to settle, collect those records and open a Microsoft support case. They should have a better chance of investigating the service side.

8q~modnotch_374:

Keeping the test conditions consistent matters too. A different account or application can bring different policies into the evaluation.

Reply to this answer
q.319~valvecrayon

Plan policy changes as if there's a transition window, not an instant cutover. For a blocking policy, don't assume an exclusion is effective just because you've saved it. Test and allow time for the results to settle before relying on it.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions