Blog Post
Upcoming Conditional Access change: Improved enforcement for policies with resource exclusions
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.
- kr1zhnaJun 23, 2026
Microsoft
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.
- skywwwJun 23, 2026Copper 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.- kr1zhnaJun 24, 2026
Microsoft
Hi skywww
Thank you for calling this out.
The application referenced in the documentation is intended to be a tenant-specific application used to control baseline scopes behavior within your tenant. Because the baseline scopes setting is configured and enforced at the tenant level, the application should be registered as a single-tenant application.
The purpose of this application is to act as a tenant-local identifier that administrators can exclude from specific "All resources" Conditional Access policies and then associate with the baseline scopes setting. Since this configuration is tenant-specific, a single-tenant application is sufficient and is the configuration used in the documented guidance.
A multi-tenant application may also work in this scenario, but it is not required for the baseline scopes setting to function.
We'll review the wording in the documentation to see if we can make this intent clearer.