Blog Post

Microsoft Entra Blog
2 MIN READ

Act now: Turn on or customize Microsoft-managed Conditional Access policies

Nitika Gupta's avatar
Nitika Gupta
Icon for Microsoft rankMicrosoft
Mar 19, 2024

As part of our Secure Future Initiative, we announced Microsoft-managed Conditional Access policies in November 2023. These policies are designed to help you secure your organization's resources and data based on your usage patterns, risk factors, and existing policy configuration, all while minimizing your effort. Our top recommendation for improving your identity secure posture is enabling multifactor authentication (MFA), which reduces the risk of compromise by 99.2%. This is why our first three policies are all related to MFA for different scenarios. 

 

Since we announced Microsoft-managed Conditional Access policies, we’ve rolled out these policies to more than 500,000 tenants in report-only mode. In this mode, the policies don’t impact access but log the results of policy evaluation. This allows administrators to assess the impact before enforcing these policies. Thanks to proactive actions taken by administrators to enable or customize these policies, over 900,000 users are now protected with MFA.  

 

We’ve been actively listening to your feedback. Customers shared that Microsoft-managed policies impact the number of Conditional Access policies that organizations can create. We’ve addressed this by making a significant change: Microsoft-managed policies will no longer count towards the Conditional Access policy limit. Another adjustment relates to existing Conditional Access policies. If you already have a policy in the “On” state that meets or exceeds the requirements set by the Microsoft-managed policy, the latter will not be automatically enforced in your tenant. 

 

Initially, we communicated that these policies would be automatically enabled 90 days after creation. However, based on customer feedback, we recognize that some customers need additional time to prepare for these policies to be enforced. As a result, we have extended the time frame before enforcing the policies for this initial set of policies. For these three policies, you will have more than 90 days to review and customize (or disable) your Microsoft-managed Conditional Access policies before they are automatically enforced. Rest assured, you’ll receive an email and a Message Center notification providing a 28-day advance notification before the policies are enforced in your tenant.  

 

Call to Action

  1. Review these policies in the Conditional Access policies blade. 
  2. Add customizations such as excluding emergency accounts and service accounts. 

  3. Once ready, the policies can be moved to the ON state.

For additional customization needs, you can duplicate these policies and make further adjustments. 

 

To learn more about how to secure your resources, visit our Microsoft-managed policies documentation.   

 

Nitika Gupta   

Principal Group Product Manager, Microsoft  

LinkedIn 

 

  

Learn more about Microsoft Entra: 

Updated Mar 18, 2024
Version 1.0
  • Maybe late to the game but what about licensing? Just theoretically but when a tenant doesn't have Security Defaults and no CA policies enabled and no P1 licenses and then MS does enable the Microsoft Managed CA Policies. Would the tenant then be non compliant? Can you say that MS does force the tenant to be out of license compliance?

    Just theorizing the (possible) scenarios I see as an MSP unfortunately with many tenants. 

  • Hello Nitika Gupta , found this CA "Multifactor authentication for Microsoft partners and vendors" added and can't seem to manage it (can't edit or make exclusions). I can't set it to report-only mode or off with below error.

     

    How to workaround this?

  • Ron Ron's avatar
    Ron Ron
    Brass Contributor

    Like I already said: If you have covered the items that the Microsoft managed policies would do, they aren't added by Microsoft.

  • ITGuyOhio's avatar
    ITGuyOhio
    Copper Contributor

    Ron Ron 

    Maybe I'm missing the obvious from above but, It's not clear to me why these Microsoft-managed Conditional Access policies are not visible in our tenant. We have not seen an email regarding them and I do not find a message center notification. So, should we assume they are not available to us yet?

    screenshot of our Conditional Access Policies

     

  • Ron Ron's avatar
    Ron Ron
    Brass Contributor

    ITGuyOhio As far as I read this in the post above:

    @Cary SiemersThats what you suppose to do.
    Microsofts managed CA will only cover scenarios you do not.

     

    It looks like you've covered everything already.
    We only have one created by Microsoft and working on it.

  • ITGuyOhio's avatar
    ITGuyOhio
    Copper Contributor

    I checked our Admin portal and don't see these new Microsoft-managed Conditional Access policies. Will they appear automatically or can we add them manually?

  • john66571's avatar
    john66571
    Brass Contributor

    C_the_SThats what you suppose to do.
    Microsofts managed CA will only cover scenarios you do not.
    Take covering Admin portals as an example, if you cover ALL USERS and the admin portals the Microsoft managed CA will not identify that you do that (it only covers 14 admin roles). So you have to validate the gap, that you actually have the coverage and use your own CA rules. If you have no CA rules, you should let the Microsoft managed CA rules go active.

    Another example,
    per user mfa, make use of the Microsoft Managed CA to see which users you have forgotten to set to disable in legacy m365. Once done, make sure you have a CA that covers all users, all apps with MFA and you are good 🙂 (then disable the Microsoft Managed).

    See them as setting "the lowest bar" possible for a CA framework. Which is a great step to increasing overall security worldwide.

  • C_the_S's avatar
    C_the_S
    Bronze Contributor

    Yeah, didn't work for us.

    I was unable to do the simple task of adding a new employee to the Microsoft managed policies so that they'd be "protected" from day 1. 

    I disabled the Microsoft ones and kept the ones I've been using for several years now.