- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
Functionally, this is how Policy Targeting works in general (Not just for Remove Local Admin Users feature):
(Computers in this set) AND (AD/Entra ID computers and groups) AND (Users and groups)
In the formula above, we see that each is AND’ed together. Now, within each of the targeting options above, they functionally OR the specific objects within them respectively and we get:
(Computer1 OR Computer2 Or …) AND (Acme\comp1 OR Acme\comp2 OR …) AND (Acme\user1 OR Acme\user2 OR …)
The key thing to understand is that you OR the objects within the specific target option and then those target options are AND together after.
Similarly, in the 'Exclude from policy' section, each is OR’ed together.
Now, to get even deeper into how this all works from a design and workflow perspective:
Computers in this set is functionally processed first and dictates which endpoints (based on agentID(s) behind the scenes) the policy is delivered to from the SaaS. This means that, if you are not included within the Computers in this set targeting, then you as the endpoint/agent don’t have knowledge of or a copy of that policy. After the endpoint receives the policies, they will assess whether they are specified in or are members of a computer group specified in the AD/Entra ID computers and groups targeting. If the endpoint/agent successfully identifies that it’s a target of the the AD/Entra ID computers and groups targeting, whether by direct membership or is part of a group defined in that targeting, then the policy is applicable for use on the endpoint. After all that is handled, when a user runs a process and the agent assesses policies to figure out which matches to handle that process, the agent will evaluate the user against the Users andgroups targeting, specified in the policies. This whole workflow and logical process is what inevitably sums to the functional AND of the policy targeting options and the functional OR of the objects within each, respectively.
To Summarize;
The “Computers in this set” is working at service level, for include and exclude. It will be checked first, will send only to the relevant endpoints.
The “AD/Entra ID computers and groups” and “Users and groups” are checked in the agents after the policy is received.