Link Order is the position assigned to a GPO within a site, domain, or OU link list. It determines precedence when more than one GPO targets the same scope. A lower number means higher priority, so the policy with the smallest Link Order is processed last and takes effect when settings conflict.
How Link Order works in Group Policy precedence
Link Order is the sequence number assigned to a Group Policy Object when it is linked to a site, domain, or organizational unit. It is not the same thing as the GPO’s internal settings, scope, or enforcement state. Instead, it helps determine which linked policy wins when multiple GPOs affect the same target and configure the same setting.
In practice, Link Order matters because Group Policy processing is cumulative but not always conflict-free. If two linked GPOs set the same value, the GPO with the higher precedence is the one that ultimately controls the result. That makes link position a governance mechanism as much as an administrative convenience.
Why the smallest Link Order has the highest precedence
Group Policy link lists are evaluated from the lowest-numbered link order to the highest-numbered one, with the smallest number treated as the strongest position. As a result, the policy linked with Link Order 1 is processed last and usually overrides conflicting settings from lower-priority links.
This is often counterintuitive because “1” looks like the first item, but in precedence terms it is the final word. The important point is that the link order expresses conflict resolution, not just display order. If the same GPO is linked in multiple places, or if multiple GPOs target the same scope, the link order is part of the decision path that decides the effective configuration.
Where Link Order matters across site, domain, and OU targeting
Link Order becomes most visible when administrators layer policies across different scopes, such as a baseline domain policy, a site-specific policy, and a more specific OU policy. The outcome depends on where the GPO is linked and how conflicting settings interact, not simply on which policy exists.
That is why Link Order is closely tied to policy design. A carefully structured policy stack can separate baseline configuration from exceptions, but a poorly managed stack can create unintended overrides that are difficult to diagnose. The more overlapping the policy set, the more important it is to understand which link is winning and why.
How administrators interpret Link Order during troubleshooting
When a setting does not behave as expected, Link Order is one of the first things to inspect because it can explain why a different GPO took effect. The visible configuration in Group Policy tools may look correct, yet the actual result on the endpoint can reflect a different linked policy with stronger precedence.
For that reason, troubleshooting should treat Link Order as part of the effective-policy model, not as a cosmetic detail. Administrators often need to trace the full chain of linked GPOs, scope, inheritance, and conflict resolution before they can explain the final applied setting.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-6 — Least Privilege | Link order helps enforce the intended access and configuration precedence. |
| CM-2 — Baseline Configuration | Link order determines which baseline or exception GPO ultimately shapes system configuration. | |
| CM-6 — Configuration Settings | The term governs which configuration settings are actually applied when GPOs conflict. | |
| Recommendation — Review effective policy precedence to preserve least-privilege outcomes. Define and maintain approved GPO baselines with documented precedence. Verify that linked GPO precedence produces the intended configuration settings. | ||
Practitioner Guidance
Governance implication: Treat Link Order as a control-plane decision, not a housekeeping field. Policy owners should be able to explain which GPO is intended to win at each scope and why that precedence is safe for the affected systems.
What to watch for: Unexpected settings changes, inconsistent application across OUs, and “mystery overrides” usually indicate that a stronger linked GPO is taking precedence over the policy you expected to apply.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org