{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/configure-gmsa-kerberos-delegation-without-delegation-tab/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/",
        "slug": "configure-gmsa-kerberos-delegation-without-delegation-tab",
        "url": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/configure-gmsa-kerberos-delegation-without-delegation-tab/"
        },
        "title": "Configure gMSA Kerberos delegation without relying on the missing tab",
        "summary": "Use Configuring Kerberos Delegation for Group Managed Service Accounts 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": "it",
                "name": "IT",
                "url": "https://update.dsesecurity.com/topic/it/"
            },
            {
                "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-27T12:14:37+00:00",
        "modified_at": "2026-08-27T12:58:58+00:00",
        "reviewed_on": "2026-08-26",
        "reading_minutes": 3,
        "word_count": 504,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Configuring Kerberos Delegation for Group Managed Service Accounts",
        "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": "Configuring Kerberos Delegation for Group Managed Service Accounts",
            "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/configure-kerberos-delegation-group-managed-service-accounts",
            "published_on": "2025-07-09",
            "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: Configure gMSA Kerberos delegation without relying on the missing tab. 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/group-managed-service-accounts/group-managed-service-accounts/configure-kerberos-delegation-group-managed-service-accounts\" target=\"_blank\" rel=\"noopener noreferrer\">Configuring Kerberos Delegation for Group Managed Service Accounts</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>The ADUC Delegation tab does not appear for standalone or group managed service accounts. The research record locates this support at <strong>Opening overview</strong>.</li>\n<li>Microsoft documents PowerShell and direct userAccountControl approaches for configuring the required delegation state. The research record locates this support at <strong>Sections: Use PowerShell commands; Manually update the userAccountControl value</strong>.</li>\n</ul>\n<p>Only the traced statements above are asserted as source facts. Apply the review to forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles after confirming that the source and deployed context match.</p>\n<h2>What the source does not establish</h2>\n<p>Use constrained delegation designs and verify SPNs before changing delegation attributes. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Opening overview</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Sections: Use PowerShell commands; Manually update the userAccountControl value</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?</li>\n<li>Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. Begin by recording scope and current state before deciding whether a change is warranted. 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>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Keep the source locations <strong>Opening overview</strong>; <strong>Sections: Use PowerShell commands; Manually update the userAccountControl value</strong> adjacent to the sanitized artifacts used for comparison. Prefer directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, with enough identity and timing data for an independent recheck.</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/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/configure-kerberos-delegation-group-managed-service-accounts\" target=\"_blank\" rel=\"noopener noreferrer\">Configuring Kerberos Delegation for Group Managed Service Accounts</a> — Microsoft</li>\n</ul>",
        "content_text": "Use this document to connect an official requirement or behavior to observable evidence: Configure gMSA Kerberos delegation without relying on the missing tab. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Configuring Kerberos Delegation for Group Managed Service Accounts from Microsoft supports the following bounded statements:\n\nThe ADUC Delegation tab does not appear for standalone or group managed service accounts. The research record locates this support at Opening overview.\nMicrosoft documents PowerShell and direct userAccountControl approaches for configuring the required delegation state. The research record locates this support at Sections: Use PowerShell commands; Manually update the userAccountControl value.\n\nOnly the traced statements above are asserted as source facts. Apply the review to forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles after confirming that the source and deployed context match.\nWhat the source does not establish\nUse constrained delegation designs and verify SPNs before changing delegation attributes. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Sections: Use PowerShell commands; Manually update the userAccountControl value, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?\nWhich condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. Begin by recording scope and current state before deciding whether a change is warranted. 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.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations Opening overview; Sections: Use PowerShell commands; Manually update the userAccountControl value adjacent to the sanitized artifacts used for comparison. Prefer directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, with enough identity and timing data for an independent recheck.\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\nConfiguring Kerberos Delegation for Group Managed Service Accounts — Microsoft",
        "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Configure gMSA Kerberos delegation without relying on the missing tab. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Configuring Kerberos Delegation for Group Managed Service Accounts](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/configure-kerberos-delegation-group-managed-service-accounts) from Microsoft supports the following bounded statements:\n\n- The ADUC Delegation tab does not appear for standalone or group managed service accounts. The research record locates this support at Opening overview.\n\n- Microsoft documents PowerShell and direct userAccountControl approaches for configuring the required delegation state. The research record locates this support at Sections: Use PowerShell commands; Manually update the userAccountControl value.\n\nOnly the traced statements above are asserted as source facts. Apply the review to forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles after confirming that the source and deployed context match.\n\n## What the source does not establish\n\nUse constrained delegation designs and verify SPNs before changing delegation attributes. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Sections: Use PowerShell commands; Manually update the userAccountControl value, which observable configuration, record, or test can confirm applicability here?\n\n- What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?\n\n- Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. Begin by recording scope and current state before deciding whether a change is warranted. 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\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.\n\n## Verification and evidence\n\nKeep the source locations Opening overview; Sections: Use PowerShell commands; Manually update the userAccountControl value adjacent to the sanitized artifacts used for comparison. Prefer directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, with enough identity and timing data for an independent recheck.\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- [Configuring Kerberos Delegation for Group Managed Service Accounts](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/configure-kerberos-delegation-group-managed-service-accounts) — 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/configure-gmsa-kerberos-delegation-without-delegation-tab/",
                "url": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-26"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Configure gMSA Kerberos delegation without relying on the missing tab",
                        "item": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/#article",
                "identifier": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/",
                "url": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/",
                "headline": "Configure gMSA Kerberos delegation without relying on the missing tab",
                "description": "Use Configuring Kerberos Delegation for Group Managed Service Accounts to review this narrow operational decision without extending the source beyond…",
                "abstract": "Use Configuring Kerberos Delegation for Group Managed Service Accounts 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: Configure gMSA Kerberos delegation without relying on the missing tab. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Configuring Kerberos Delegation for Group Managed Service Accounts from Microsoft supports the following bounded statements:\n\nThe ADUC Delegation tab does not appear for standalone or group managed service accounts. The research record locates this support at Opening overview.\nMicrosoft documents PowerShell and direct userAccountControl approaches for configuring the required delegation state. The research record locates this support at Sections: Use PowerShell commands; Manually update the userAccountControl value.\n\nOnly the traced statements above are asserted as source facts. Apply the review to forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles after confirming that the source and deployed context match.\nWhat the source does not establish\nUse constrained delegation designs and verify SPNs before changing delegation attributes. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Sections: Use PowerShell commands; Manually update the userAccountControl value, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope?\nWhich condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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. Begin by recording scope and current state before deciding whether a change is warranted. 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.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and sanitize protected material before retention.\nVerification and evidence\nKeep the source locations Opening overview; Sections: Use PowerShell commands; Manually update the userAccountControl value adjacent to the sanitized artifacts used for comparison. Prefer directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, with enough identity and timing data for an independent recheck.\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\nConfiguring Kerberos Delegation for Group Managed Service Accounts — Microsoft",
                "datePublished": "2026-08-27T12:14:37+00:00",
                "dateModified": "2026-08-27T12:58:58+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/configure-gmsa-kerberos-delegation-without-delegation-tab/"
                },
                "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/configure-gmsa-kerberos-delegation-without-delegation-tab/#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": "Configure gMSA Kerberos delegation without relying on the missing tab"
                },
                "articleSection": [
                    "IT",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "IT",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Guide",
                    "Advisory priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    },
                    {
                        "@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": 504,
                "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": "Configuring Kerberos Delegation for Group Managed Service Accounts",
                    "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/configure-kerberos-delegation-group-managed-service-accounts",
                    "datePublished": "2025-07-09"
                }
            }
        ]
    }
}