{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/",
        "slug": "scope-redirect-users-and-computers-containers-in-observed-ad-dns-state",
        "url": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/"
        },
        "title": "Scope Redirect users and computers containers in observed AD/DNS state",
        "summary": "Use Redirect users and computers containers to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "briefing",
            "name": "Briefing"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-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:01:50+00:00",
        "modified_at": "2026-08-27T17:29:41+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 556,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Redirect users and computers containers",
        "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": "Redirect users and computers containers",
            "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/redirect-users-computers-containers",
            "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 resolve one bounded operational decision: Scope Redirect users and computers containers in observed AD/DNS state. 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/troubleshoot/windows-server/active-directory/redirect-users-computers-containers\" target=\"_blank\" rel=\"noopener noreferrer\">Redirect users and computers containers</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “You can use redirusr and redircmp to redirect user, computer, and group accounts that are created by earlier-version APIs.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Introduction below H1, Microsoft states: “So they are put in admin-specified organizational unit (OU) containers.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n</ul>\n<p>Keep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source&#8217;s stated conditions.</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. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?</li>\n<li>How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?</li>\n<li>Who approves the conclusion, exception, test window, and rollback threshold?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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>An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.</p>\n<h2>Verification and evidence</h2>\n<p>Tie each conclusion back to <strong>Introduction below H1</strong>; <strong>Introduction below H1</strong> and to observable material such as sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Preserve provenance and stable identifiers without copying secrets into the evidence set.</p>\n<p>Label this evidence set <strong>DSE-20260827-336</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/redirect-users-computers-containers\" target=\"_blank\" rel=\"noopener noreferrer\">Redirect users and computers containers</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to resolve one bounded operational decision: Scope Redirect users and computers containers in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Redirect users and computers containers from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “You can use redirusr and redircmp to redirect user, computer, and group accounts that are created by earlier-version APIs.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “So they are put in admin-specified organizational unit (OU) containers.” The research record locates this support at Introduction below H1.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nTie each conclusion back to Introduction below H1; Introduction below H1 and to observable material such as sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nLabel this evidence set DSE-20260827-336 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nRedirect users and computers containers — Microsoft",
        "content_markdown": "Use this document to resolve one bounded operational decision: Scope Redirect users and computers containers in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Redirect users and computers containers](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/redirect-users-computers-containers) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “You can use redirusr and redircmp to redirect user, computer, and group accounts that are created by earlier-version APIs.” The research record locates this support at Introduction below H1.\n\n- At Introduction below H1, Microsoft states: “So they are put in admin-specified organizational unit (OU) containers.” The research record locates this support at Introduction below H1.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\n\n## Verification and evidence\n\nTie each conclusion back to Introduction below H1; Introduction below H1 and to observable material such as sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Preserve provenance and stable identifiers without copying secrets into the evidence set.\n\nLabel this evidence set DSE-20260827-336 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [Redirect users and computers containers](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/redirect-users-computers-containers) — 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/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/",
                "url": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Scope Redirect users and computers containers in observed AD/DNS state",
                        "item": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/#article",
                "identifier": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/",
                "url": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/",
                "headline": "Scope Redirect users and computers containers in observed AD/DNS state",
                "description": "Use Redirect users and computers containers to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use Redirect users and computers containers to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Use this document to resolve one bounded operational decision: Scope Redirect users and computers containers in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Redirect users and computers containers from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “You can use redirusr and redircmp to redirect user, computer, and group accounts that are created by earlier-version APIs.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “So they are put in admin-specified organizational unit (OU) containers.” The research record locates this support at Introduction below H1.\n\nKeep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions.\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. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. 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.\nAn implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence.\nVerification and evidence\nTie each conclusion back to Introduction below H1; Introduction below H1 and to observable material such as sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Preserve provenance and stable identifiers without copying secrets into the evidence set.\nLabel this evidence set DSE-20260827-336 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nRedirect users and computers containers — Microsoft",
                "datePublished": "2026-08-27T17:01:50+00:00",
                "dateModified": "2026-08-27T17:29:41+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/"
                },
                "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/scope-redirect-users-and-computers-containers-in-observed-ad-dns-state/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Scope Redirect users and computers containers in observed AD/DNS state"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Briefing",
                    "Advisory priority"
                ],
                "genre": "Briefing",
                "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": 556,
                "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": "Redirect users and computers containers",
                    "url": "https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/redirect-users-computers-containers"
                }
            }
        ]
    }
}