Forum Discussion

Brass Contributor

Mar 17, 2021

Solved

Conditional Access Policy will not save "Validating Policy"

I have a conditional access policy to enable MFA. It's all set and good. I have it shown here. I later wanted to go into "Session" and enable "Sign-In Frequency" and set it to the recommended...

Azure Active Directory (AAD)

snout
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.

Tomnibus_MedOne

Brass Contributor

Mar 17, 2021

I read the two reference links before. From what your dirteam.com link suggests, they are advocating that the remember device is not to be used. But also suggests you can enable the session sign-in frequency along with MFA (mostly from the comments) but that isn't working for me. it won't enable it. But it sounds like unless i want to reduce it from 90 days, I don't need it.

ChristianBergstrom

Silver Contributor

Mar 17, 2021

Hello 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.

Brownin88
Copper Contributor
Mar 18, 2021
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.
- snout
  Brass Contributor
  Mar 18, 2021
  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.
  - ChristianBergstrom
    Silver Contributor
    Mar 18, 2021
    Hi, thanks for adding to the conversation. Could be what I said in a reply above, that it's an effect of the recent Azure outage (multiple M365 services). Please update with a response from the official support.