Azure AD Conditional Access What If tool says Not enough information, what does that mean?

Question

Hi,

I am configuring some new conditional access rules in Azure and am using the whatif tool to check their workings before putting them into production. With one rule the whatif tells me the reason for not being applied is: Not enough information

Besides not being able to see what is wrong with the rule I cannot find any information as to why there is not enough information, as far as I can see there is very little to no documentation on that specific reason. Funny thing is that when I test the rule on one account the logs tell me that the rule is being applied so that seems to contradict the whatif tool.

Has anybody seen this behavior or has anybody seen any documentation on this reason?

Kind regards,
Michiel

Answer 1

Hi everyone,

I got an update from the product team that a fix has been pushed, but it may take up to two weeks for the changes to be applied in production.

This is an issue only when the What-If tool is run on a Conditional Access policy (CAP) where there is a group assigned. Therefore, the workaround for now in this limited testing capacity is to assign users directly to the CAP instead of specifying a group.

A recommended approach to test Conditional Access Policies and understand how a policy acts is to use the Conditional Access Report-Only mode functionality. The results are logged to the Conditional Access and Report-only tabs in the Sign-in log details. The Conditional Access Insights workbook in Activity Monitor can be used to visualize queries and the impact of multiple report-only policies for a given time-range, set of apps and users. This is a good option if you are currently testing policy assignments.

Answer 2

Hi - having the same issue. Any update on further fixes?

Answer 3

@Marilee Turscak-MSFT
Got the same issue in three of our tenants.... pretty annoying to be honest.. I mean already one week and not even an official statement somewhere from MS Side?
Please tell us how to go on.

Answer 4

@Marilee Turscak-MSFT

Same problem here. Please let me know if there's an update?

Answer 5

Got the same issue, been driving me nuts for days.