{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/",
        "slug": "new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks",
        "url": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/"
        },
        "title": "New-ADCentralAccessRule: create adcentral access rule with rollback checks",
        "summary": "Use New-ADCentralAccessRule to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "checklist",
            "name": "Checklist"
        },
        "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:04:09+00:00",
        "modified_at": "2026-08-27T17:18:34+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 562,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of New-ADCentralAccessRule",
        "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-ADCentralAccessRule",
            "url": "https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adcentralaccessrule?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>Treat this document as a focused evidence review: New-ADCentralAccessRule: create adcentral access rule with rollback checks. 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-adcentralaccessrule?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">New-ADCentralAccessRule</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At DESCRIPTION, Microsoft states: “The New-ADCentralAccessRule cmdlet creates a central access rule in Active Directory.” The research record locates this support at <strong>DESCRIPTION</strong>.</li>\n<li>At Example 1: Create a new named central access rule, Microsoft states: “This command creates a new central access rule named Finance Documents Rule.” The research record locates this support at <strong>Example 1: Create a new named central access rule</strong>.</li>\n</ul>\n<p>Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.</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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>DESCRIPTION</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Example 1: Create a new named central access rule</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>What inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?</li>\n<li>Which condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?</li>\n<li>What result would disprove the working assumption and return the issue to the owner?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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 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>Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials. Handle credentials, keys, recovery data, and personal information through approved secure channels.</p>\n<h2>Verification and evidence</h2>\n<p>Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations <strong>DESCRIPTION</strong>; <strong>Example 1: Create a new named central access rule</strong>. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.</p>\n<p>Label this evidence set <strong>DSE-20260827-197</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today&#8217;s observation is not a continuing guarantee.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adcentralaccessrule?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">New-ADCentralAccessRule</a> — Microsoft</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: New-ADCentralAccessRule: create adcentral access rule with rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official New-ADCentralAccessRule from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The New-ADCentralAccessRule cmdlet creates a central access rule in Active Directory.” The research record locates this support at DESCRIPTION.\nAt Example 1: Create a new named central access rule, Microsoft states: “This command creates a new central access rule named Finance Documents Rule.” The research record locates this support at Example 1: Create a new named central access rule.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Example 1: Create a new named central access rule, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?\nWhich condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE 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 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations DESCRIPTION; Example 1: Create a new named central access rule. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-197 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nNew-ADCentralAccessRule — Microsoft",
        "content_markdown": "Treat this document as a focused evidence review: New-ADCentralAccessRule: create adcentral access rule with rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [New-ADCentralAccessRule](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adcentralaccessrule?view=windowsserver2025-ps) from Microsoft supports the following bounded statements:\n\n- At DESCRIPTION, Microsoft states: “The New-ADCentralAccessRule cmdlet creates a central access rule in Active Directory.” The research record locates this support at DESCRIPTION.\n\n- At Example 1: Create a new named central access rule, Microsoft states: “This command creates a new central access rule named Finance Documents Rule.” The research record locates this support at Example 1: Create a new named central access rule.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Example 1: Create a new named central access rule, which observable configuration, record, or test can confirm applicability here?\n\n- What inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?\n\n- Which condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?\n\n- What result would disprove the working assumption and return the issue to the owner?\n\n## DSE recommendation:\n\nDSE 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 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\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations DESCRIPTION; Example 1: Create a new named central access rule. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\n\nLabel this evidence set DSE-20260827-197 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\n\n## Official references\n\n- [New-ADCentralAccessRule](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adcentralaccessrule?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-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "New-ADCentralAccessRule: create adcentral access rule with rollback checks",
                        "item": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/#article",
                "identifier": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/",
                "headline": "New-ADCentralAccessRule: create adcentral access rule with rollback checks",
                "description": "Use New-ADCentralAccessRule to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use New-ADCentralAccessRule to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: New-ADCentralAccessRule: create adcentral access rule with rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official New-ADCentralAccessRule from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The New-ADCentralAccessRule cmdlet creates a central access rule in Active Directory.” The research record locates this support at DESCRIPTION.\nAt Example 1: Create a new named central access rule, Microsoft states: “This command creates a new central access rule named Finance Documents Rule.” The research record locates this support at Example 1: Create a new named central access rule.\n\nDo not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Example 1: Create a new named central access rule, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?\nWhich condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE 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 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations DESCRIPTION; Example 1: Create a new named central access rule. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.\nLabel this evidence set DSE-20260827-197 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nClose the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.\nOfficial references\n\nNew-ADCentralAccessRule — Microsoft",
                "datePublished": "2026-08-27T17:04:09+00:00",
                "dateModified": "2026-08-27T17:18:34+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/new-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/"
                },
                "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-adcentralaccessrule-create-adcentral-access-rule-with-rollback-checks/#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-ADCentralAccessRule: create adcentral access rule with rollback checks"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Checklist",
                    "Advisory priority"
                ],
                "genre": "Checklist",
                "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": 562,
                "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-ADCentralAccessRule",
                    "url": "https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adcentralaccessrule?view=windowsserver2025-ps"
                }
            }
        ]
    }
}