MGB
MGB // Cyber security notes
← All posts

Conditional Access change MC1223829: baseline scopes are now enforced

Microsoft Message Center item MC1223829 closes a long-standing gap in Entra Conditional Access. If any of your policies target All resources and have an exclusion, sign-ins that used to skip them may now meet MFA or device checks.

TL;DR
  • What changed: Conditional Access policies that target All resources and have at least one resource exclusion are now enforced for sign-ins that request only a small set of "baseline scopes". They used to be skipped.
  • When: progressive rollout from 15 June 2026. Check your tenant now rather than assuming it has or hasn't reached you.
  • Who is affected: only tenants with an All resources policy that has exclusions. If you got MC1223829, that includes you.
  • What you may see: new MFA or device-compliance prompts for apps such as the Visual Studio Code or Azure CLI sign-in, and failures in apps that can't handle a Conditional Access challenge.
  • What to do: find the affected policies and apps, fix or replace the ones that can't cope, then leave enforcement on.
15 JunEnforcement began
4OIDC scopes
7Directory scopes
3Enforcement settings

The gap Microsoft is closing

Many tenants have a Conditional Access policy that targets All resources, usually "require MFA", with a few apps excluded because they can't cope with it. Microsoft explains that when a policy had any exclusion, certain low-privilege scopes were automatically left out of enforcement as well, so that apps could still read the signed-in user's basic profile and group membership as part of authentication. The side effect was that a sign-in requesting only those scopes skipped the policy entirely, even though the policy said "all resources".

Microsoft's own docs now call the old behaviour "legacy". The new behaviour treats those scopes as directory access, mapped to Azure AD Graph (the "Windows Azure Active Directory" resource) for Conditional Access evaluation, so your All resources policy applies to them. Microsoft ties the change to its Secure Future Initiative and describes it as defence in depth.

Which scopes count as "baseline"

Microsoft's list is two groups:

  • OpenID Connect scopes: email, offline_access, openid, profile
  • Baseline directory scopes: User.Read, User.Read.All, User.ReadBasic.All, People.Read, People.Read.All, GroupMember.Read.All, Member.Read.Hidden

Public clients (desktop apps, single-page apps) only had the narrower set, and confidential clients that were excluded from the policy had the wider one. One third-party write-up leaves offline_access off its list, so use Microsoft's page as the reference.

Timeline

  • 29 January 2026: MC1223829 first published. The Message Center post went through seven versions, the last on 31 July 2026.
  • March and May 2026: earlier planned dates, moved. Microsoft's own pages still mention a March start in places, which is one reason to check your tenant rather than rely on a date.
  • 15 June 2026: progressive rollout starts. Microsoft says tenants get a notice about two weeks before and another once rollout completes in their tenant.
  • Mid-August 2026: one commentator expected worldwide deployment to be done by then. I couldn't find Microsoft stating a completion date, so treat that as an expectation, not a fact.

Who is affected

Microsoft says it affects you if all of these are true:

  1. You have one or more Conditional Access policies that target All resources.
  2. Those policies have one or more resource exclusions.
  3. Users sign in through apps that request only baseline scopes.

A policy on All resources with no exclusions is unaffected, and so is a tenant that never received the notice. Microsoft's docs give a Graph query to list the policies that meet the first two conditions:

GET https://graph.microsoft.com/v1.0/identity/conditionalAccess/policies
  ?$filter=conditions/applications/includeApplications/any(a:a eq 'All')
    and conditions/applications/excludeApplications/any()
  &$select=id,displayName

What might break or prompt

Microsoft names two scenarios that can now trigger a challenge such as MFA or device compliance:

  • Public client apps that request only baseline scopes. Microsoft's examples are the Visual Studio Code desktop client (openid and profile) and Azure CLI (User.Read).
  • Confidential client apps that you excluded from the policy and that request only baseline directory scopes, for example a web app asking for User.Read and People.Read.

The challenge you get depends on the controls in your All resources policies, or in any policy that explicitly targets Azure AD Graph.

Apps that already request anything beyond the baseline (for example Mail.Read) were already enforced, so nothing changes for them. Neither does a confidential client that requests only OIDC scopes. Two third-party write-ups also warn that apps using a password-based flow with no browser (ROPC) can't complete MFA and will fail. That's their reading rather than something Microsoft spells out, but it's a sensible thing to test for.

Heads up Users who never saw a prompt for these apps may now get one, and any app that can't handle a Conditional Access challenge may simply stop signing in. Expect help desk tickets that say "it asked for MFA out of nowhere".

The three settings

The change applies to every tenant, but you control how it lands through Baseline scopes settings in Conditional Access. Microsoft notes you need the direct link (aka.ms/BaselineScopesSettingsUX) to see the page, and that anything you configure isn't overridden by the rollout.

OptionWhat it doesMicrosoft's view
Enable enforcementNew behaviour applies to all All resources policies with exclusions.Recommended
Customize behaviorKeep legacy behaviour for chosen policies by excluding a dedicated, tenant-owned placeholder app and selecting it in the settings.A bridge for apps you can't fix yet
Disable enforcementLegacy behaviour for every policy in the tenant.Not recommended; creates gaps

Customize behavior also helps with discovery. Once it's configured, sign-ins that request only baseline scopes show your placeholder app as a Conditional Access audience in the sign-in logs, so over a few days you get a list of the apps affected. Microsoft supplies a Microsoft Graph sign-in query for this. Keep in mind it's a beta API.

What to do

  1. Find the policies. Run the query above, or review every policy with a resource exclusion in the Entra admin centre.
  2. Find the apps. Use Customize behavior to tag baseline-only sign-ins, then review the app list. Third-party tools can help, but one write-up cautions that OIDC scopes don't always show up as persistent grants, so those methods can miss apps.
  3. Decide per app. Microsoft's guidance by app type:
    AppAction
    Public client, baseline scopes onlyDecide whether it should be exempt. If there's a real business reason, retain legacy behaviour with Customize behavior.
    Your own confidential client, excluded, baseline directory scopes onlyAsk the developers whether it can request OIDC scopes (openid, profile) instead of User.Read for basic user info.
    Supplier's confidential client, same patternAsk the supplier to do the same. If they can't, use Customize behavior.
  4. Make sure your own apps can handle a challenge. Microsoft says apps owned by your tenant must cope with MFA or compliance challenges, otherwise they need updating. See its Conditional Access developer guidance.
  5. Review the exclusions themselves. The cleanest end state is the one Microsoft recommends: a baseline MFA policy for all users and all resources with no resource exclusions. Each exclusion you can remove is one less exception to reason about.

Why this matters for security

Exclusions tend to be added in a hurry and forgotten. This change means an excluded app no longer quietly widens an exemption to anything that only asks for a basic profile. It fits the wider theme of the AiTM post: controls that look complete on paper often have gaps in the detail, and the details are where attackers look. Treat it as a prompt to audit your exclusions, not just to keep the lights on.

The bottom line

For most organisations Microsoft says no action is needed, but "most" isn't a check. If you have an All resources policy with exclusions, confirm where your tenant stands in Baseline scopes settings, find the apps that depend on the old behaviour, and fix or replace them rather than switching enforcement off. The Message Center item has expired, so the Microsoft Learn page is now the place to look.