Could staged rollout features be coming to Conditional Access policies in Microsoft Entra? That is today’s question… It was recently picked up from the Microsoft Entra admin center a new status when filtering for Conditional Access policies by the status property. This status is ‘Staged rollout‘.
As of the time of writing this post, the feature or features seem to be entirely undocumented after searching vigorously through Google, Microsoft Learn and GitHub. So what do we know about the Staged rollout features so far?
Well, everything I have deduced about the service has been pulled publically from the Microsoft Graph API, so you can do it too! But starting off in the web portal, when navigating to the Conditional Access blade, the new filter features expose this potential “Staged rollout” feature in plain text.
Of course, nothing is returned when applying this filter, but this is to be expected. The great thing about any new feature in the admin portal is that they function through Microsoft Graph behind the scenes. Thanks to this fact, we can see its call to Microsoft Graph using our browser developer tools.
Here is the full request URL made by the admin portal:
https://graph.microsoft.com/beta/identity/conditionalAccess/policies?$count=true&$select=id,displayName,state,createdDateTime,modifiedDateTime,templateId&$filter=(state%20eq%20%27partiallyEnabled%27)
To turn this into a useable request, I have simplified the URI and provided an example below using the Microsoft Graph PowerShell SDK.
Connect-MgGraph -Scope Policy.Read.All
Invoke-MgGraphRequest -Method GET `
-Uri "/beta/identity/conditionalAccess/policies?`$filter=(state eq 'partiallyEnabled')" Of course, at this point I want to learn more about this service, so what other information can I explore with Microsoft Graph? Well, first of all, I want to see if I can enable this setting on an existing Conditional Access policy, I know the state is called ‘particallyEnabled’ on the back end, so I can use this to send a PATCH request to Microsoft Graph.
Connect-MgGraph -Scopes Policy.ReadWrite.ConditionalAccess
$params = @{
state = "PartiallyEnabled"
}
Update-MgBetaIdentityConditionalAccessPolicy `
-ConditionalAccessPolicyId "4681e562-2331-4e17-b313-a925a212b43d" `
-BodyParameter $params This however failed with a generic error message, until I ran the same command with the -Debug parameter which returned something more meaningful. “1211: ‘PartiallyEnabled’ state requires PartialEnablementStrategy to be set.“
Naturally, the next thing to try is to include the PartialEnablementStrategy property in the body of the request, however, I can only guess the format of the schema for this property.
$params = @{
state = "PartiallyEnabled"
PartialEnablementStrategy = "Enabled"
}
Update-MgBetaIdentityConditionalAccessPolicy `
-ConditionalAccessPolicyId "4681e562-2331-4e17-b313-a925a212b43d" `
-BodyParameter $params Unfortunately, my attempt only failed with incorrect schema errors… However, while I wait for an official response from Microsoft’s Entra product team, I have one more trick up my sleeve. When you create or update a Conditional Access policy, a ‘Validation’ request is sent to Microsoft Graph containing the full schema.
To save copying and pasting a huge amount of JSON code, you can see from the highlighted area above that the only item of interest related to this in the validation request is the partialEnablementTargetRegions which remains null.
So what have we learnt so far about the Conditional Access Staged rollout options? Well only a little:
- Microsoft has implemented a new filtering state named ‘Staged rollout’.
- Microsoft Graph stores this value as ‘partiallyEnabled’
- Setting a policy for Staged rollout requires the ‘PartialEnablementStrategy’ property set, but we are not sure what the value should be.
- The validation of the ‘partialEnablementTargetRegions’ indicated that staged rollout options could be set via geographical region or even defined by Conditional Access locations.

