Policy
Support compound authentication
Windows 11 25H2
Policy overview
Key metadata and intent for this policy.
Supported OS tags: Windows10, Windows10RT, Windows11, Windows8, Windows81, WindowsRT, WindowsRT81, WindowsServer2012, WindowsServer2012R2, WindowsServer2016
This policy setting controls configuring the device's Active Directory account for compound authentication. Support for providing compound authentication which is used for access control will require enough domain controllers in the resource account domains to support the requests. The Domain Administrator must configure the policy "Support Dynamic Access Control and Kerberos armoring" on all the domain controllers to support this policy. If you enable this policy setting, the device's Active Directory account will be configured for compound authentication by the following options: Never: Compound authentication is never provided for this computer account. Automatic: Compound authentication is provided for this computer account when one or more applications are configured for Dynamic Access Control. Always: Compound authentication is always provided for this computer account. If you disable this policy setting, Never will be used. If you do not configure this policy setting, Automatic will be used.
Registry values
How enabled and disabled states update the registry.
| Registry location | Type | Enabled value | Disabled value |
|---|---|---|---|
| HKLM\Software\Policies\Microsoft\Netlogon\Parameters\CompoundIdDisabled | REG_DWORD | 0 | 1 |
Policy elements
Inputs and configuration options exposed by this policy.
| Element | Type | Registry mapping | Constraints & behavior |
|---|---|---|---|
Support authorization with client device information: ID CompoundIdEnabled | enum | HKLM\Software\Policies\Microsoft\Netlogon\Parameters\CompoundIdEnabled Type REG_DWORD | Options: Never (0), Automatic (1), Always (2) |
Other policies in this category
Explore related policies at the same level.
- ComputerAllow retrieving the Azure AD Kerberos Ticket Granting Ticket during logonAt least Windows Server 2019, Windows 10 Version 2004
- ComputerAlways send compound authentication firstAt least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
- ComputerConfigure hash algorithms for certificate logonAt least Windows 11 Version 22H2
- ComputerDefine host name-to-Kerberos realm mappingsAt least Windows Vista
- ComputerDefine interoperable Kerberos V5 realm settingsAt least Windows Vista
- ComputerDisable revocation checking for the SSL certificate of KDC proxy serversAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerEnable Delegated Managed Service Account logonsAt least Windows 11 Version 24H2
- ComputerFail authentication requests when Kerberos armoring is not availableAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerKerberos client support for claims, compound authentication and Kerberos armoringAt least Windows Server 2012, Windows 8 or Windows RT
- ComputerRequire strict KDC validationAt least Windows Vista
- ComputerRequire strict target SPN match on remote procedure callsAt least Windows Server 2008 R2 or Windows 7
- ComputerSet maximum Kerberos SSPI context token buffer sizeAt least Windows Server 2003 operating systems or Windows XP Professional