{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/",
        "slug": "new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence",
        "url": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/"
        },
        "title": "New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence",
        "summary": "Use New-ADReplicationSiteLink to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "identity-cloud",
            "label": "Identity & cloud",
            "alt": "Governed cloud identity system with connected service and lifecycle nodes.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T17:05:27+00:00",
        "modified_at": "2026-08-27T17:14:54+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 551,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of New-ADReplicationSiteLink",
        "dse_recommendation": "Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.",
        "primary_source": {
            "name": "New-ADReplicationSiteLink",
            "url": "https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adreplicationsitelink?view=windowsserver2025-ps",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Use this document to connect an official requirement or behavior to observable evidence: New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adreplicationsitelink?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">New-ADReplicationSiteLink</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At SYNOPSIS, Microsoft states: “Creates a new Active Directory site link for in managing replication.” The research record locates this support at <strong>SYNOPSIS</strong>.</li>\n<li>At DESCRIPTION, Microsoft states: “The New-ADReplicationSiteLink cmdlet can be used to create a new Active Directory site link.” The research record locates this support at <strong>DESCRIPTION</strong>.</li>\n</ul>\n<p>The source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.</p>\n<h2>What the source does not establish</h2>\n<p>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. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>SYNOPSIS</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>DESCRIPTION</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Within Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, which versions, roles, and configuration states define the review population?</li>\n<li>Could Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials invalidate the test, hide a failure, or change applicability?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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 Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.</p>\n<p>For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.</p>\n<h2>Verification and evidence</h2>\n<p>A reviewer should be able to retrace the decision from <strong>SYNOPSIS</strong>; <strong>DESCRIPTION</strong> through sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Record what was collected, where, when, by whom, and which system or role it represents.</p>\n<p>Label this evidence set <strong>DSE-20260827-119</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adreplicationsitelink?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">New-ADReplicationSiteLink</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to connect an official requirement or behavior to observable evidence: New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official New-ADReplicationSiteLink from Microsoft supports the following bounded statements:\n\nAt SYNOPSIS, Microsoft states: “Creates a new Active Directory site link for in managing replication.” The research record locates this support at SYNOPSIS.\nAt DESCRIPTION, Microsoft states: “The New-ADReplicationSiteLink cmdlet can be used to create a new Active Directory site link.” The research record locates this support at DESCRIPTION.\n\nThe source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe 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. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at SYNOPSIS, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nWithin Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, which versions, roles, and configuration states define the review population?\nCould Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE 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 Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nA reviewer should be able to retrace the decision from SYNOPSIS; DESCRIPTION through sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Record what was collected, where, when, by whom, and which system or role it represents.\nLabel this evidence set DSE-20260827-119 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nNew-ADReplicationSiteLink — Microsoft",
        "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [New-ADReplicationSiteLink](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adreplicationsitelink?view=windowsserver2025-ps) from Microsoft supports the following bounded statements:\n\n- At SYNOPSIS, Microsoft states: “Creates a new Active Directory site link for in managing replication.” The research record locates this support at SYNOPSIS.\n\n- At DESCRIPTION, Microsoft states: “The New-ADReplicationSiteLink cmdlet can be used to create a new Active Directory site link.” The research record locates this support at DESCRIPTION.\n\nThe source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nThe 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. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\n\n## Applicability questions\n\n- For source statement 1 at SYNOPSIS, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\n\n- Within Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, which versions, roles, and configuration states define the review population?\n\n- Could Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials invalidate the test, hide a failure, or change applicability?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\n\n## DSE recommendation:\n\nDSE 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 Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\n\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\n\n## Verification and evidence\n\nA reviewer should be able to retrace the decision from SYNOPSIS; DESCRIPTION through sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Record what was collected, where, when, by whom, and which system or role it represents.\n\nLabel this evidence set DSE-20260827-119 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\n\n## Official references\n\n- [New-ADReplicationSiteLink](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adreplicationsitelink?view=windowsserver2025-ps) — Microsoft"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/",
                "url": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence",
                        "item": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/#article",
                "identifier": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/",
                "url": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/",
                "headline": "New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence",
                "description": "Use New-ADReplicationSiteLink to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use New-ADReplicationSiteLink to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to connect an official requirement or behavior to observable evidence: New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official New-ADReplicationSiteLink from Microsoft supports the following bounded statements:\n\nAt SYNOPSIS, Microsoft states: “Creates a new Active Directory site link for in managing replication.” The research record locates this support at SYNOPSIS.\nAt DESCRIPTION, Microsoft states: “The New-ADReplicationSiteLink cmdlet can be used to create a new Active Directory site link.” The research record locates this support at DESCRIPTION.\n\nThe source support ends with the statements listed above. Use them to examine Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe 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. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, ownership, and change authority instead of treating documented behavior as a deployment guarantee.\nApplicability questions\n\nFor source statement 1 at SYNOPSIS, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nWithin Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, which versions, roles, and configuration states define the review population?\nCould Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE 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 Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nA reviewer should be able to retrace the decision from SYNOPSIS; DESCRIPTION through sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Record what was collected, where, when, by whom, and which system or role it represents.\nLabel this evidence set DSE-20260827-119 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nNew-ADReplicationSiteLink — Microsoft",
                "datePublished": "2026-08-27T17:05:27+00:00",
                "dateModified": "2026-08-27T17:14:54+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/new-adreplicationsitelink-create-adreplication-site-link-with-before-and-after-evidence/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "New-ADReplicationSiteLink: create adreplication site link with before-and-after evidence"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 551,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "New-ADReplicationSiteLink",
                    "url": "https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adreplicationsitelink?view=windowsserver2025-ps"
                }
            }
        ]
    }
}