Blog Post

Microsoft Entra Blog
3 MIN READ

Upcoming Conditional Access change: Improved enforcement for policies with resource exclusions

Swaroop Krishnamurthy's avatar
Jan 28, 2026

We’re strengthening how Microsoft Entra Conditional Access is enforced for a narrow set of authentication flows to improve your security posture.

In alignment with Microsoft’s Secure Future Initiative, we are taking the following proactive security measures for defense-in-depth. Please review the changes and take any required actions to prepare.

Note: We’ve adjusted the rollout timeline, with enforcement now starting on June 15, 2026. To support a smooth transition, customers will receive additional details and guidance through Microsoft 365 Message Center messages.

What is changing?

  • Today, when a user signs in through a client application that requests only OIDC scopes or a limited set of directory scopes, Conditional Access policies that target All resources are not enforced if the policy has one or more resource exclusions.
  • After this change, Conditional Access policies that target All resources will be enforced for these sign-ins, even when resource exclusions are present. This ensures that policies are consistently applied regardless of the scope set requested by the application. Read more about this change.

When will you see this change?

We’ve adjusted the rollout timeline, with enforcement now starting on June 15, 2026. To support a smooth transition, customers will receive additional details and guidance through Microsoft 365 Message Center messages.

Who will be affected by this change?

This change only affects tenants that have a Conditional Access policy targeting All resources with one or more resource exclusions, and these tenants will be notified through M365 Message Center messages. Tenants without this policy configuration will not be impacted.

How will this affect your organization?

When a user signs in through a client application that requests only the scopes listed above, they may now receive Conditional Access challenges (such as MFA or device compliance) where previously they were allowed access without enforcement. The specific challenge depends on the access controls configured in your policies that target All resources or explicitly target Azure AD Graph as the resource.

What do you need to do to prepare?

✔ Most customers: No action required

Most applications request additional scopes beyond the scopes listed above and are already subject to Conditional Access enforcement. In such cases, there is no change in behavior. We’re working with popular software vendors where updates may be needed to ensure their applications handle Conditional Access challenges appropriately.

⚠ Apps registered in your tenant and requesting only these scopes: Review recommended

If you have custom applications that are intentionally designed to request only the scopes listed above, evaluate whether they can handle Conditional Access challenges such as MFA or device compliance.

If they already handle Conditional Access challenges: no changes are required. If they do not, updates may be needed. Refer to the Microsoft Conditional Access developer guidance on how to update your application appropriately.

-Swaroop Krishnamurthy

 

Additional resources 

Learn more about Microsoft Entra

Prevent identity attacks, ensure least privilege access, unify access controls, and improve the experience for users with comprehensive identity and network access solutions across on-premises and clouds.

Updated May 14, 2026
Version 6.0

24 Comments

  • Jan_Gutjahr's avatar
    Jan_Gutjahr
    Iron Contributor

    Impact of Conditional Access Changes on WHfB During Autopilot Enrollment

    Hi Microsoft Entra team

    Can you clarify how this Conditional Access enforcement change will affect Windows Hello for Business setup during Autopilot?

    Our concern is the first user sign-in during enrollment, where the device may not yet be compliant, but the user still needs to complete Windows Hello for Business registration.

    How should we (re)configure Conditional Access so that Windows Hello for Business provisioning during Autopilot is not blocked by 'All resources' policies that have exclusions and require device compliance?

    Thanks

    • kr1zhna's avatar
      kr1zhna
      Icon for Microsoft rankMicrosoft

      Hi Jan_Gutjahr​ , this change is not intended to impact Windows Hello for Business provisioning during Autopilot. The baseline scopes enforcement change is focused on ensuring Conditional Access is evaluated consistently for requests that contain only baseline scopes when a policy targets "All resources" and includes resource exclusions. It does not change the experience for device enrollment, compliance establishment, or Windows Hello for Business provisioning.

  • tikuni26's avatar
    tikuni26
    Copper Contributor

    Raising a gap not yet covered in this thread: no CA mechanism to differentiate client apps that share the same target resource.

    In BYOD environments running a browser-based VPN with Entra user SSO, we're hitting an unresolvable scenario. Both our VPN client and our VoIP SaaS app (third-party, multi-tenant, no control over either client) resolve to Microsoft Graph (00000003-0000-0000-c000-000000000000) as the target resource — confirmed in sign-in logs. From CA's perspective they are identical.

    Our requirement: VPN SSO must work from unmanaged devices outside the corp network to bootstrap the tunnel. VoIP must only be accessible from a managed device or managed network. These are the same users on the same devices.

    Every CA lever is exhausted:

    • App ID exclusion: applies to the resource, not the initiating client — ineffective
    • Client app type condition: both apps resolve to the same type
    • Resource targeting: impossible — shared resource
    • Network/location condition: VPN bootstrap happens before the tunnel exists — circular dependency
    • Baseline scope proxy app: excludes all baseline-scope clients equally, can't split VPN from VoIP

    This gap predates MC1223829. Previously, baseline-scope sign-ins bypassed CA evaluation entirely when resource exclusions were present — masking the problem. The June 15 rollout correctly closes that bypass, but in doing so exposes an architectural gap that has no supported resolution: when multiple client apps share the same target resource, there is no CA mechanism to enforce different policies per client.

    The fix is conceptually simple: client application ID as a first-class CA targeting/exclusion condition, independent of resource. This exists in other policy frameworks. It doesn't exist in CA today.

    Has anyone found a workaround for this specific scenario? And is the product team tracking this as a gap?

    • kr1zhna's avatar
      kr1zhna
      Icon for Microsoft rankMicrosoft

      Hi tikuni26​,

      We appreciate the feedback and the detailed explanation of the scenario.

      The scenario you've described is not introduced by the baseline scopes enforcement change itself. Rather, the change makes Conditional Access evaluation consistent for requests containing only baseline scopes.

      Conditional Access is fundamentally designed to protect access to resources. As a result, when multiple client applications request access to the same resource, they may be evaluated similarly by Conditional Access even though the applications themselves serve different purposes.

      We appreciate the feedback regarding the ability to differentiate policy enforcement based on the initiating client application. Your feedback helps us better understand customer requirements in this area.

  • bipsy's avatar
    bipsy
    Copper Contributor

    Any further concrete info from MSFT on this?

  • skywww's avatar
    skywww
    Copper Contributor

    With the updated MC post:
    still no report mode.

    still no good exclusion mechanism.

    still no good timeline - post published today (April 20) and roll-out is May 13 - 23 days to prepare.

     

    This is a great example how good change could be fully compromised by the poor change management process.

    • kr1zhna's avatar
      kr1zhna
      Icon for Microsoft rankMicrosoft

      Hi skywww​, thank you for the feedback. We understand the importance of providing customers sufficient time to assess and prepare for changes to Conditional Access policies.

      Since the announcement, the rollout timeline has been adjusted, with enforcement beginning on June 15 rather than May 13, providing additional time for customers to review their configurations and make any necessary adjustments. We have also introduced baseline scopes settings, giving customers a direct way to manage this change and control enforcement within their tenant.

      In addition, we have published updated documentation with additional guidance: 

      Enforcement for baseline scopes in Conditional Access - Microsoft Entra ID | Microsoft Learn

      We will continue to monitor feedback as the rollout progresses.

      • skywww's avatar
        skywww
        Copper Contributor

        thank you for your reply!

        quick note - in the official documentation link you provided, in the "Customize behavior" section in step 1 stated: 
        "Register the application as a single tenant application."
        This is not correct as app should be multi-tenant.

  • povlhp's avatar
    povlhp
    Copper Contributor

    Already active here on some CA rules. This is the worst decision from Microsoft in a long time.

    We have tens of thousands of floor workers with no MFA method. They use some custom Microsoft apps, and we tried to use custom Apps fully, with permissions and everything, and acting as the signed in user.

    It seems that for those users (and for B2B users) we will have to drop MFA by default, as we can't exempt individual apps, and maybe move to enforcing MFA on specific apps only if that will work ? Or strip Microsoft Graph from MFA requirement for most users. This really will lower security.

    I can see one more workaround, a Custom Multifactor Strength, that includes password (aka single factor), targeting some users. But if we need to put it on Microsoft Graph, things are really bad.

    Please show me the considerations/user story for floor employees, accessing a custom application from a personal device at home, no MFA - no access to company confidential data (say a non-public intranet) - We generally require MFA for other things. And some floor workers might have mail where we require MFA - so they would be MFA ready. Do you think we can/will micromanage group memberships to control this ? 

    How about B2B ? Some have higher permissions and directory roles, they need phishing resistant MFA, others needs just a password. Again our security will then depend on our ability to micromanage groups ? rather than exempt the few apps with low security requirements ?

    • kr1zhna's avatar
      kr1zhna
      Icon for Microsoft rankMicrosoft

      Hi povlhp​, 

      Thank you for sharing the details of your scenario. The intent of this change is to ensure Conditional Access is evaluated consistently for requests containing only baseline scopes, even when a policy targeting "All resources" includes resource exclusions.

      Based on the scenario you described, we recommend reviewing the new baseline scopes settings, which provide customers with additional control over how this enforcement change is handled and can help manage the transition to the updated enforcement behavior.

      We also recommend reviewing Conditional Access policy design to ensure MFA requirements remain aligned with the sensitivity of the resources being accessed, rather than relying on legacy baseline-scope behavior.

      Additional guidance is available here:

      Enforcement for baseline scopes in Conditional Access - Microsoft Entra ID | Microsoft Learn

  • SIVASELVARAJ's avatar
    SIVASELVARAJ
    Copper Contributor

    Running into a challenge with the new Conditional Access behavior for “All cloud apps” + exclusions.

    Consider a scenario where organizations exclude apps like Microsoft Intune Company Portal (Linux), Jamf Pro macOS enrollment, and Azure AD connectors for Jamf (macOS login / enrollment flows) from CA policies (e.g., device compliance or MFA).

    With the new behavior, sign-ins are still impacted.

    The reason: Conditional Access now evaluates all resources involved in the request, not just the primary app. These flows depend on Microsoft Graph (e.g., openid, profile, User.Read), and since Graph isn’t excluded, the policy is enforced.

    This introduces challenges for common scenarios:

    • Device enrollment (Jamf Pro, Intune, macOS - login)
    • Platform-specific flows (Linux, macOS)
    • Cases where exclusions were previously used to prevent onboarding devices for compliance enrollment.

    Curious how others are approaching this:
    What’s the recommended design pattern to support these enrollment/login flows without weakening Conditional Access posture by exluding primary resources such as Microsoft Graph and Windows Azure Active Directory?

     

    • ykhan152's avatar
      ykhan152
      Copper Contributor

      I also experienced this issue and had to set to Disable Enforcement for Jamf to work. Jamf have provided guidance on this but I havent got round to implementing it as isnt very straightforward to implement - 

      https://learn.jamf.com/r/en-US/jamf-connect-documentation-current/Modifying_Jamf_Connect_for_Conditional_Access_Polices

    • c14g-Services's avatar
      c14g-Services
      Copper Contributor

      Ouch, I think TD Synnex just started rolling this out and borked ALL of their sharepoint shares.  Heads should be rolling at Microsoft AND Synnex for this one. I lost thousands of dollars today because I can't download something I NEED from their sharepoint site and they aren't willing to send the xlsx file like everyone else does in the world. They just lost my future business. I wonder how much this eff up will cost them from other clients leaving.

  • pfasser's avatar
    pfasser
    Brass Contributor

    Hello all, in AVD environment you need to disable MFA for the storage account used for profile management: https://learn.microsoft.com/en-us/azure/storage/files/storage-files-identity-auth-hybrid-identities-enable?tabs=azure-portal%2Cintune#disable-multifactor-authentication-on-the-storage-account

    When you are configuring the storage file setup, it automatically creates the Entra application with the following API permission:

     

     

     

     

     

    How is this change affecting the profile management service?

    • kimpa's avatar
      kimpa
      Copper Contributor

      From what i understand, which may be wrong, this will be our options for any app/resource exclusions using "low privilege permissions" moving forward, including AVD storageAccounts.

      1. Remove app exclusion from "main" MFA policy, this will then require MFA (not applicable for AVD)
      2. Alternatively exclude the "Windows Azure Active Directory" app from the CA policy (this effectively cancels the new change, lowering/resetting security to "pre-change")
      3. Create a separate CA policy "grant access, no MFA" for resources affected by the change, and leave the old "all resources" policy in place, without exclusions (i.e. remove old "app/resource exclusions from the "main" policy)
      4. (this option only feasible on self-develope applications) Add additional API permissions in the scope for the token request, and the same permissions on the affected appregistration resource (i.e. something more stringent than openid, profile, user.read), thus also "overriding" this new change (extraced from MS learn article: "There is no change in behavior when a client application requests a scope beyond those listed previously, as illustrated in the following examples.")

       

      I think for AVD, and possibly other apps that only require "openid, profile, user.read", option 3 should be the best way forward. 

      The evaluation of CA should then compile all policies during evaluation and apply the rules that trigger closest to the resource being evaluated, in this case it should be the resources with individual targets in the policy created in point 3. In this way, the "all resources"/"main" policy is filtered out of that evaluation and the policy in point 3 takes effect. 

      This is currently a hypothesis on top of my head and will of course need to be fully evaluated and validated before it can be presented as a viable solution...

      With that said it may provide some options to test and verify to get every app up and running again post this new CA "low-priv permissions" evaluation change.

      • povlhp's avatar
        povlhp
        Copper Contributor

        For now I asked developers to to refactor their code, and make 2 login buttons - each with their app registration. One for internal users, and one for the external nonMFA.

        Since it was activated for us around March 20 (the announcement), we are in a bit of a hurry. The May 13th does niot apply to us it seems.

        What is the "Windows Azure Active Directory" app ? Will excluding that really work ? What are the side effects ? Will I disable MFA from more than just the excluded apps ?

        BTW: How will 3 work ? If I have MFA on all apps in another ? 

        I have User.Read and User.Read.All triggering the MFA

         

    • JonasBack's avatar
      JonasBack
      Steel Contributor

      Also wondering about this since it’s the most common exclude we see.

  • Rafal_Fitt's avatar
    Rafal_Fitt
    Steel Contributor

    You can identify applications affected by this enforcement change

    https://learn.microsoft.com/en-us/entra/identity/conditional-access/concept-conditional-access-cloud-apps?tabs=powershell#how-to-identify-applications-affected-by-the-low-privilege-scope-enforcement-change

  • raghavmahajan's avatar
    raghavmahajan
    Copper Contributor

    Will the filtering with any method? example security attributes