Forum Discussion

TherealKillerbe's avatar
TherealKillerbe
Brass Contributor
Feb 10, 2026

Adaptive Scope

I created an adaptive scope, in which i use CustomAttribute10 -eq "Leaver", to build the user scope.

The accounts are hybrid ad accounts wherefore we need to populate ExtensionAttribute10 with the string "Leaver".

the OnPrem Ad Account is updated accordingly

Set-aduser $User.DistinguishedName -add @{ExtensionAttribute10="Leaver"}

the extension attribute has been added to Entra-ID sync in which the attrute is sync to Entra-ID.

When i verify the synced account in Entra-ID i can verify that Custom attribute 10 is indeed synced to Entra-ID.

(get-mguser -Filter "DisplayName eq '$($AdUser.Name)')" -Property OnPremisesExtensionAttributes | select -ExpandProperty OnPremisesExtensionAttributes).ExtensionAttribute10
Leaver

This is my adaptive Scope

get-adaptivescope | select FilterConditions

FilterConditions
----------------
{"Conditions":[{"Value":"Leaver","Operator":"Equals","Name":"CustomAttribute10"}],"Conjunction":"And"}

I have created the adaptive scope about a week ago, so it should be poppulated. However when i check my scope, it is still empty.

What did i miss?

 

1 Reply

  • VasilMichev's avatar
    VasilMichev
    MVP
    Feb 10, 2026

    Are those mail/mailbox enabled users? When talking about CustomAttributeXX, the documentation refers to the set of Exchange attributes, which in turn means that only objects recognized by Exchange can be used with such. If this is a "pure" user object, without any footprint in ExO, you will not be able to use CustomAttributeXX for this purpose, even if its showing as "populated" under OnPremisesExtensionAttributes.

    Other than that, make sure the user is properly licensed, as adaptive scopes do enforce licensing requirements