{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/",
        "slug": "validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active",
        "url": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/"
        },
        "title": "Validate Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS evidence",
        "summary": "Use Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory 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:06:14+00:00",
        "modified_at": "2026-08-27T17:11:09+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 589,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory",
        "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": "Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory",
            "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/component-updates/Appendix-I--Creating-Management-Accounts-for-Protected-Accounts-and-Groups-in-Active-Directory",
            "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: Validate Appendix I &#8211; Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS 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/windows-server/identity/ad-ds/manage/component-updates/Appendix-I--Creating-Management-Accounts-for-Protected-Accounts-and-Groups-in-Active-Directory\" target=\"_blank\" rel=\"noopener noreferrer\">Appendix I &#8211; Creating Management Accounts for Protected Accounts and Groups in Active Directory</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “Some privileged identity management solutions require that the software&#8217;s service accounts are granted permanent membership in groups such as DA or Administrators in each domain in the forest.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Introduction below H1, Microsoft states: “However, it is technically not necessary for Privileged Identity Management (PIM) solutions to run their services in such highly privileged contexts.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n</ul>\n<p>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.</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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.</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>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?</li>\n<li>Could Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. 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.</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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.</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 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.</p>\n<p>Label this evidence set <strong>DSE-20260827-072</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/windows-server/identity/ad-ds/manage/component-updates/Appendix-I--Creating-Management-Accounts-for-Protected-Accounts-and-Groups-in-Active-Directory\" target=\"_blank\" rel=\"noopener noreferrer\">Appendix I &#8211; Creating Management Accounts for Protected Accounts and Groups in Active Directory</a> — Microsoft</li>\n</ul>",
        "content_text": "Treat this document as a focused evidence review: Validate Appendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Appendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “Some privileged identity management solutions require that the software’s service accounts are granted permanent membership in groups such as DA or Administrators in each domain in the forest.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “However, it is technically not necessary for Privileged Identity Management (PIM) solutions to run their services in such highly privileged contexts.” The research record locates this support at Introduction below H1.\n\nDo 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.\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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.\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?\nWithin forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, which versions, roles, and configuration states define the review population?\nCould Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie 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.\nLabel this evidence set DSE-20260827-072 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\nAppendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory — Microsoft",
        "content_markdown": "Treat this document as a focused evidence review: Validate Appendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Appendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/component-updates/Appendix-I--Creating-Management-Accounts-for-Protected-Accounts-and-Groups-in-Active-Directory) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “Some privileged identity management solutions require that the software’s service accounts are granted permanent membership in groups such as DA or Administrators in each domain in the forest.” The research record locates this support at Introduction below H1.\n\n- At Introduction below H1, Microsoft states: “However, it is technically not necessary for Privileged Identity Management (PIM) solutions to run their services in such highly privileged contexts.” The research record locates this support at Introduction below H1.\n\nDo 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.\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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.\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- 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?\n\n- Could Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. 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.\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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.\n\n## Verification and evidence\n\nTie 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.\n\nLabel this evidence set DSE-20260827-072 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- [Appendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/component-updates/Appendix-I--Creating-Management-Accounts-for-Protected-Accounts-and-Groups-in-Active-Directory) — 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/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/",
                "url": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Validate Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS evidence",
                        "item": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/#article",
                "identifier": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/",
                "url": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/",
                "headline": "Validate Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS evidence",
                "description": "Use Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory to review this narrow operational decision without…",
                "abstract": "Use Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Treat this document as a focused evidence review: Validate Appendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Appendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “Some privileged identity management solutions require that the software’s service accounts are granted permanent membership in groups such as DA or Administrators in each domain in the forest.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “However, it is technically not necessary for Privileged Identity Management (PIM) solutions to run their services in such highly privileged contexts.” The research record locates this support at Introduction below H1.\n\nDo 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.\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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity before translating the source into an operational decision.\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?\nWithin forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles, which versions, roles, and configuration states define the review population?\nCould Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. 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.\nDo not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity. Handle credentials, keys, recovery data, and personal information through approved secure channels.\nVerification and evidence\nTie 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.\nLabel this evidence set DSE-20260827-072 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\nAppendix I – Creating Management Accounts for Protected Accounts and Groups in Active Directory — Microsoft",
                "datePublished": "2026-08-27T17:06:14+00:00",
                "dateModified": "2026-08-27T17:11:09+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/"
                },
                "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/validate-appendix-i-creating-management-accounts-for-protected-accounts-and-groups-in-active/#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": "Validate Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory with AD/DNS evidence"
                },
                "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": 589,
                "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": "Appendix I - Creating Management Accounts for Protected Accounts and Groups in Active Directory",
                    "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/component-updates/Appendix-I--Creating-Management-Accounts-for-Protected-Accounts-and-Groups-in-Active-Directory"
                }
            }
        ]
    }
}