Microsoft 365 Expert, Author, YouTuber, Speaker & Senior Technology Instructor (MCT)
Microsoft Entra Conditional Access policy plans group shared identities, resources and conditions so administrators can manage related access rules together. The feature matters to Entra administrators and security teams that need to organize sets of Conditional Access rules without repeatedly configuring common settings. Andy Malone [MVP] demonstrates creating and configuring a plan in a YouTube walkthrough.
A Conditional Access policy plan is a container for plan details, shared conditions and one or more sets of rules. The shared settings provide common targeting and context; individual rule sets define what to do when those conditions apply. That structure offers an alternative to maintaining a large collection of separately configured policies that repeat the same targeting or conditions.
In the demonstrated interface, administrators can start a plan from scratch or choose a template. The template picker includes options for scenarios such as Zero Trust, remote work, administrator protection, emerging threats and AI agent management. Plans can also be searched, and their settings can be downloaded or viewed in JSON.
A plan does not mean that every rule must have identical enforcement. The walkthrough distinguishes shared conditions from rules and shows that administrators can add further rule sets using the shared plan configuration. This can make it easier to arrange multiple related decisions under a common administrative structure.
The main audience is Microsoft Entra administrators, Microsoft 365 administrators, security engineers and identity specialists who manage Conditional Access. The starting point is the Conditional Access area in Microsoft Entra, where Policy plans appears alongside the existing policy management experience. The demonstrated feature is in public preview.
The walkthrough does not present a licensing prerequisite for creating a standard policy plan. It does show that targeting agents in the tenant used for the demonstration required Microsoft Agent 365 or an E7 license. The presenter also identifies risk-related capabilities tied to Microsoft Entra ID Protection and says that user risk is a P2 feature.
Available choices depend on the plan configuration and target scenario. The interface shown includes users and groups, workload identities and agents; it also offers options for guests or external users, directory roles, and exclusions. Administrators should select only the identity types and conditions that fit the rule they are building.
Open Microsoft Entra, go to Conditional Access and choose Policy plans. Start a new plan or select a template, then enter a name and, if useful, a description. The creation screen also supports assigning owners and adding tags, so responsibility and organization can be reflected in the plan.
Conditional Access conditions act as signals used to determine whether a rule applies. For example, a plan can account for the identity being targeted, the resource or action involved, device platform, location or risk. Grant controls determine whether access is allowed, blocked or requires a stronger check; session controls govern aspects of the user's session.
Policy plans are in public preview, so administrators should evaluate them carefully before relying on them for broad enforcement. The demonstrated workflow includes report-only mode, which lets teams review a plan before turning it on. The presenter also advises starting with a small group rather than assigning all users, to reduce the risk of locking people out.
Some settings depend on what resources the plan targets. In the walkthrough, persistent browser session was unavailable when specific cloud apps were selected; the presenter says the option would be active if all cloud apps were selected. Review the available controls for the scope you choose instead of assuming every session setting applies to every plan.
Traditional Conditional Access policies remain the comparison point: the presenter describes plans as a way to reuse shared settings and organize multiple rule sets rather than creating numerous separate policies. Check the target identities, exclusions, resources and resulting access behavior before broadening assignments. A report-only review and a limited initial assignment are practical ways to validate the configuration.
The demonstrated Policy plans feature is in public preview.
Yes. The plan groups shared identities, resources and conditions, and administrators can add multiple rule sets that use the shared configuration.
The plan settings shown include report-only mode. The walkthrough uses that option before enabling a plan.
The demonstrated tenant showed agent targeting requiring Microsoft Agent 365 or an E7 license.