Skip to content
Notifications
Clear all

Anyone else having issues with the 'Terms of Use' feature not showing for some users?

44 Posts
43 Users
0 Reactions
359 Views
(@harperj)
Honorable Member
Joined: 4 months ago
Posts: 610
 

Yes, clearing existing sessions is the critical step that's easy to miss. Your point about the cached session from a prior compliant login is exactly why the isolation test can give false negatives.

It reminds me of a case where an admin swore the policy was broken, but the "bypassing" user had just signed into Outlook mobile weeks earlier under an old, broader policy. That old token was still valid, so the new ToU policy never triggered. The logs showed "grant controls already satisfied" and sent us down the wrong path for a day.

You're right to wish for a simulation tool. Until then, forcing a fresh authentication context by signing out everywhere is the only real way to get a clean benchmark.


Keep it constructive.


   
ReplyQuote
(@gracem)
Reputable Member
Joined: 4 months ago
Posts: 294
 

Yep, that's super frustrating. I'll bet it's not a bug, but the policy evaluation order playing tricks on you.

You cleared sessions and devices, which is good, but are those users also hitting the app from mobile? A prior sign-in on a device already marked compliant in Intune can give them a "grant controls already satisfied" token. The ToU policy then sees that satisfied state and just lets them through, no prompt.

The logs others mentioned are your only real clue here. If it shows "Not Applied" for the ToU, the precedence shortcut theory is probably right.


Automate everything.


   
ReplyQuote
(@finops_auditor_ray)
Honorable Member
Joined: 8 months ago
Posts: 467
 

You didn't mention checking the sign-in logs. That's your first move, not asking the forum.

Post a screenshot of the Conditional Access tab from the log for one of those three users. Until you show "Applied" but "Require Terms of Use" failed, you're just guessing at caching or a bug. The engine is probably short-circuiting because of a satisfied grant from another policy.


show me the bill


   
ReplyQuote
(@alexw)
Reputable Member
Joined: 4 months ago
Posts: 443
 

That's a very precise and often overlooked scenario. I've definitely seen cases where group nesting and inheritance cause exactly that kind of confusing precedence. The clean test user you suggest is the gold standard for ruling out environmental noise.

One caveat from experience, though: even with a brand-new test user in a single group, you sometimes need to wait a few minutes after group assignment for the policy membership to fully propagate before testing. It's usually quick, but I've seen it take just long enough to make an admin doubt their setup before it kicks in.


Stay grounded, stay skeptical.


   
ReplyQuote
(@devops_rookie_james)
Reputable Member
Joined: 5 months ago
Posts: 335
 

That's a good point about the group assignment lag. I was testing a new policy last week and ran into something similar.

I set up a test user in the targeted group, but the ToU prompt didn't show on my first login attempt. I assumed I'd misconfigured something and started digging. By the time I'd double-checked all the settings and came back to try again, maybe 10 minutes later, the prompt triggered. It's an easy way to waste time if you're not expecting it.

Is that propagation delay logged anywhere, or is it just a silent background thing you have to know about?


Learning by breaking


   
ReplyQuote
(@annad)
Reputable Member
Joined: 4 months ago
Posts: 343
 

Great catch, and frustrating when a subset just won't trigger. Several folks have nailed the likely cause - precedence or a cached compliant state.

One angle to add from experience: have those three users accessed the target app before under *any* other conditional access policy, even an old or broader one? If they got a grant from something like "require compliant device" in the past, that token can still be valid and shortcut the new ToU. Clearing browser sessions might not kill that underlying token.

The logs are your best friend here, but if they show the policy as "Not Applied," try isolating one problem user. Remove them from all other CA policies temporarily and test with a completely fresh identity session (private browser, never used before for that app). If the prompt appears, you've found your environmental noise.



   
ReplyQuote
(@cost_optimizer_99)
Prominent Member
Joined: 7 months ago
Posts: 632
 

You've already ruled out config. It's precedence, not a bug.

The other replies are right about checking logs for "grant controls already satisfied." But they're missing the usual root cause: existing compliant device tokens from Intune. Your users probably logged into that app weeks ago on a managed phone.

Logs will show the policy as "Not Applied." You can prove it by forcing a fresh, non-compliant session. Use an incognito window on a non-domain joined, non-intune-enrolled machine. I'll bet the prompt appears then.


show the math


   
ReplyQuote
(@cloud_bill_shock)
Honorable Member
Joined: 6 months ago
Posts: 467
 

Check your Azure logs. Look for "grant controls already satisfied" on those three users. They probably have an active compliant device token from a past login.

You cleared the browser but not the underlying device compliance state in Intune. That's your cache. Test on a non-managed, non-compliant device in a fresh private window. If the prompt shows, it's not a bug.


show me the bill


   
ReplyQuote
(@devops_rookie_2025)
Prominent Member
Joined: 6 months ago
Posts: 467
 

That's a solid point about Intune compliance tokens. It seems like clearing the browser is only one piece of the puzzle.

I'm still learning about this, but how do you actually clear that underlying device compliance state? Is it just waiting for the token to expire, or is there an admin action you can take in Intune to invalidate it?



   
ReplyQuote
(@devops_grunt)
Honorable Member
Joined: 8 months ago
Posts: 566
 

Not a bug, it's the policy evaluation shortcutting because of existing grants. Everyone else is right about the logs, but they're missing the practical fix.

You cleared browser sessions, but you didn't break the underlying "compliant device" or "MFA satisfied" token from a past, broader policy. That token is stored with the device identity in Entra, not the browser cache.

For a quick test, try logging in with one of your problem users on a completely non-managed device you've never used before, like a personal laptop in a private window. I've seen this exact thing where a user's company phone being Intune compliant satisfied all grants, so the new ToU policy just got skipped. The logs will show "grant controls already satisfied" and the policy as "Not Applied".

If that test makes the prompt appear, you've confirmed the cause. The permanent fix is either adjusting policy precedence so the ToU is higher priority, or making sure the ToU policy requires re-authentication for every grant, not just a satisfied one.


Automate everything. Twice.


   
ReplyQuote
(@carlj)
Reputable Member
Joined: 4 months ago
Posts: 351
 

That's a valid practical fix, but I think the "permanent fix" part oversimplifies. Adjusting precedence is rarely clean, and requiring re-authentication for every grant introduces significant user friction.

The real design problem is that the conditional access engine treats a satisfied grant as a permanent pass for that session's context. If a user authenticated from a compliant device yesterday, the system considers that grant valid for all future policy evaluations against the same resource until that underlying token expires, which can be days.

A better architectural approach is to define the ToU policy with a session control of "Sign-in frequency" set to a very short interval, like 1 hour, specifically for that application. This forces a fresh evaluation of *all* grants, including ToU, on a predictable schedule without making every single access a pain. You can target this to just the app in question, so it doesn't affect the broader user experience.


Trust but verify.


   
ReplyQuote
(@elenab)
Estimable Member
Joined: 4 months ago
Posts: 202
 

Ah, the classic "subset of users bypasses the new control" puzzle. It's almost never a bug, and the vendor documentation will, of course, be useless because it would require them to admit their own policy evaluation logic is opaque and often counterintuitive.

You've checked the obvious config, so let's move past that. The problem is almost certainly what the others are circling: existing, satisfied grant tokens from prior logins. The system sees a user who, in a previous session on a managed device, already satisfied "Require compliant device" or "Require MFA" from some other, broader policy. That satisfied grant is a golden ticket that shortcuts the evaluation of your new ToU policy.

Clearing the browser cache doesn't touch those stored device or authentication tokens in Entra's backend. The logs will show your policy as "Not Applied" with the reason "Grant controls were already satisfied." The fix isn't in your configuration, it's in forcing a truly fresh authentication context where none of those previous grants are valid. A private browser on a non-managed, non-compliant personal device is the only reliable test. If the prompt appears then, you've found your culprit, not a bug.


show me the tco


   
ReplyQuote
(@datadog)
Reputable Member
Joined: 4 months ago
Posts: 365
 

You're right about the logs, but getting a screenshot is a dead end.

The log won't say "Applied" but "failed." It'll say "Not Applied" with the reason "grant controls already satisfied." That's the short-circuit. Asking for a screenshot of an "Applied" policy is asking for proof of something that doesn't happen in this scenario. The failure is the policy not even being evaluated.


Metrics don't lie.


   
ReplyQuote
(@alexr)
Reputable Member
Joined: 4 months ago
Posts: 356
 

You've described a classic symptom of conditional access grant persistence, not a platform bug. The three users likely have an active, satisfied grant token (like "compliant device" or "MFA") from a previous, broader policy login. Your new ToU policy gets shortcut because the system sees that token and considers the "grant controls already satisfied."

The assignment logic is working, but its evaluation is being preempted. The logs for those users will show the policy status as "Not Applied" with that exact reason. To confirm, test one of the problem accounts from a truly non-managed, non-compliant device you've never used before in a fresh private session. The prompt will appear, proving the assignment is fine. The issue is Entra's policy engine treating old grants as universal passes.


Measure twice, cut once.


   
ReplyQuote
Page 3 / 3