# Scope Creating a Site Link Bridge Design in observed AD/DNS state > Use Creating a Site Link Bridge Design to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/scope-creating-a-site-link-bridge-design-in-observed-ad-dns-state/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:06:15+00:00 - Modified: 2026-08-27T17:11:09+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Briefing - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Creating a Site Link Bridge Design to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Creating a Site Link Bridge Design ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to resolve one bounded operational decision: Scope Creating a Site Link Bridge Design in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Creating a Site Link Bridge Design](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/Creating-a-Site-Link-Bridge-Design) from Microsoft supports the following bounded statements: - At Introduction below H1, Microsoft states: “A site link bridge connects two or more site links and enables transitivity between site links.” The research record locates this support at Introduction below H1. - At Introduction below H1, Microsoft states: “Each site link in a bridge must have a site in common with another site link in the bridge.” The research record locates this support at Introduction below H1. Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles and the conditions the source actually describes. ## What the source does not establish The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. 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 Introduction below H1, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - Within forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, which versions, roles, and configuration states define the review population? - Could Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity invalidate the test, hide a failure, or change applicability? - Who owns the decision, and which observation requires stopping, escalation, or rollback? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Use a two-person review for the source interpretation and the resulting operational decision. 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. Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity, while excluding secrets and sensitive personal or topology data from ordinary tickets. ## Verification and evidence Tie each conclusion back to Introduction below H1; Introduction below H1 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. Label this evidence set DSE-20260827-071 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [Creating a Site Link Bridge Design](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/Creating-a-Site-Link-Bridge-Design) — Microsoft ## Primary reference - Name: Creating a Site Link Bridge Design - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/Creating-a-Site-Link-Bridge-Design - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Scope Creating a Site Link Bridge Design in observed AD/DNS state,” DSE Security, https://update.dsesecurity.com/updates/scope-creating-a-site-link-bridge-design-in-observed-ad-dns-state/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.