Forum Discussion
Conditional Access Policy will not save "Validating Policy"
- Mar 24, 2021
Tomnibus_MedOne Yes, it started working for me as well yesterday, with no intervention required.
In fact, I haven't even heard back from Microsoft Support yet, despite opening the case 6 days ago and sending a chasing email a day or two ago.
Hi, well the 90 days was something that just popped to mind so had to put it out there. As why it is not saving your settings I think it's better if I just link this for guidance.
https://dirteam.com/sander/2020/06/17/todo-move-from-the-allow-users-to-remember-multi-factor-authentication-on-devices-they-trust-option-to-conditional-access/
And for reference
https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-mfasettings
https://docs.microsoft.com/en-us/azure/active-directory/conditional-access/howto-conditional-access-session-lifetime
- ChristianBergstromMar 17, 2021Silver ContributorHello again, sounds right to me as well as it’s basically about adjusting the default rolling window (90). But I would open up a support ticket with Microsoft anyway to get an answer as to why you cannot save your policy with a custom number. Perhaps something to do with the recent incident.
- Brownin88Mar 18, 2021Copper Contributor
I too am experiencing the same hung 'validating policy' in conditional access. Mine is not a policy already active, a brand new policy with no bearing or effect on any other features or policies already being manipulated by conditional access.
- snoutMar 18, 2021Brass Contributor
Me too. I can't create a new CA policy (or edit an existing one) where I change the "sign-in frequency" option to On. I can edit a CA policy that has "sign in frequency" turned on but I can't change the values for that frequency. This is all irrespective of what value I use (e.g. 90 days, 1 hour, etc.).
It's been like this for a couple of days or more. I've opened a case with Microsoft.