Choose AD group scope from the resource and trust boundary

Use this document to connect an official requirement or behavior to observable evidence: Choose AD group scope from the resource and trust boundary. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official Active Directory Security Groups from Microsoft supports the following bounded statements:

• AD security groups are authorization principals distinct from distribution groups. The research record locates this support at Sections: Security groups; Distribution groups.
• Group scope controls where a group can be granted permissions and which principals it can contain. The research record locates this support at Section: Group scope.

The source support ends with the statements listed above. Use them to examine forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles in the applicable environment, not to imply a wider guarantee.

What the source does not establish

Model nesting and trust paths before changing group scope or membership. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.

Applicability questions

• For source statement 1 at Sections: Security groups; Distribution groups, which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section: Group scope, which observable configuration, record, or test can confirm applicability here?
• What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?
• Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity must be healthy before evidence is trustworthy?
• What result would disprove the working assumption and return the issue to the owner?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Make the source, asset scope, owner, and expected outcome explicit in the review record. Record the source location, examined part of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, observed and expected states, owner, and reason for deviation.

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

Verification and evidence

Tie each conclusion back to Sections: Security groups; Distribution groups; Section: Group scope and to observable material such as directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests. Preserve provenance and stable identifiers without copying secrets into the evidence set.

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

Official references

• Active Directory Security Groups — Microsoft