{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/keep-protected-machine-accounts-disabled-until-fixed/", "item": { "id": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/", "slug": "keep-protected-machine-accounts-disabled-until-fixed", "url": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed.md", "json": "https://update.dsesecurity.com/api/v1/posts/keep-protected-machine-accounts-disabled-until-fixed/" }, "title": "Keep protected machine accounts disabled until Microsoft resolves rotation", "summary": "Use Credential Guard protected machine accounts in Windows Server 2025 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": "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:39+00:00", "modified_at": "2026-08-27T12:58:58+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 491, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Credential Guard protected machine accounts in Windows Server 2025", "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": "Credential Guard protected machine accounts in Windows Server 2025", "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/delegated-managed-service-accounts/credential-guard-protected-machine-accounts", "published_on": "2025-04-11", "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": "

Treat this document as a focused evidence review: Keep protected machine accounts disabled until Microsoft resolves rotation. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official Credential Guard protected machine accounts in Windows Server 2025 from Microsoft supports the following bounded statements:

\n\n

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.

\n

What the source does not establish

\n

This is status-sensitive guidance; recheck the official page before any deployment decision. 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

Applicability questions

\n\n

DSE recommendation:

\n

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.

\n

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.

\n

Verification and evidence

\n

Keep the source locations Opening important notice; Opening overview 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

Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.

\n

Official references

\n", "content_text": "Treat this document as a focused evidence review: Keep protected machine accounts disabled until Microsoft resolves rotation. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Credential Guard protected machine accounts in Windows Server 2025 from Microsoft supports the following bounded statements:\n\nMicrosoft states that Credential Guard protected machine accounts are temporarily disabled because of a Kerberos machine-password rotation issue. The research record locates this support at Opening important notice.\nFAST and managed service accounts increasingly depend on machine-account identity. The research record locates this support at Opening overview.\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\nThis is status-sensitive guidance; recheck the official page before any deployment decision. 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 important notice, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Opening overview, 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.\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\nKeep the source locations Opening important notice; Opening overview 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.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nCredential Guard protected machine accounts in Windows Server 2025 — Microsoft", "content_markdown": "Treat this document as a focused evidence review: Keep protected machine accounts disabled until Microsoft resolves rotation. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Credential Guard protected machine accounts in Windows Server 2025](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/delegated-managed-service-accounts/credential-guard-protected-machine-accounts) from Microsoft supports the following bounded statements:\n\n- Microsoft states that Credential Guard protected machine accounts are temporarily disabled because of a Kerberos machine-password rotation issue. The research record locates this support at Opening important notice.\n\n- FAST and managed service accounts increasingly depend on machine-account identity. The research record locates this support at Opening overview.\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\nThis is status-sensitive guidance; recheck the official page before any deployment decision. 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 important notice, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Opening overview, 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\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\nKeep the source locations Opening important notice; Opening overview 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\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [Credential Guard protected machine accounts in Windows Server 2025](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/delegated-managed-service-accounts/credential-guard-protected-machine-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/keep-protected-machine-accounts-disabled-until-fixed/", "url": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Keep protected machine accounts disabled until Microsoft resolves rotation", "item": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/#article", "identifier": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/", "url": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/", "headline": "Keep protected machine accounts disabled until Microsoft resolves rotation", "description": "Use Credential Guard protected machine accounts in Windows Server 2025 to review this narrow operational decision without extending the source beyond…", "abstract": "Use Credential Guard protected machine accounts in Windows Server 2025 to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Treat this document as a focused evidence review: Keep protected machine accounts disabled until Microsoft resolves rotation. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Credential Guard protected machine accounts in Windows Server 2025 from Microsoft supports the following bounded statements:\n\nMicrosoft states that Credential Guard protected machine accounts are temporarily disabled because of a Kerberos machine-password rotation issue. The research record locates this support at Opening important notice.\nFAST and managed service accounts increasingly depend on machine-account identity. The research record locates this support at Opening overview.\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\nThis is status-sensitive guidance; recheck the official page before any deployment decision. 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 important notice, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Opening overview, 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.\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\nKeep the source locations Opening important notice; Opening overview 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.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nCredential Guard protected machine accounts in Windows Server 2025 — Microsoft", "datePublished": "2026-08-27T12:14:39+00:00", "dateModified": "2026-08-27T12:58:58+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/keep-protected-machine-accounts-disabled-until-fixed/" }, "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/keep-protected-machine-accounts-disabled-until-fixed/#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": "Keep protected machine accounts disabled until Microsoft resolves rotation" }, "articleSection": [ "IT", "Microsoft 365 & Identity", "Networks & Infrastructure" ], "keywords": [ "IT", "Microsoft 365 & Identity", "Networks & Infrastructure", "Checklist", "Advisory priority" ], "genre": "Checklist", "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": 491, "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": "Credential Guard protected machine accounts in Windows Server 2025", "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/delegated-managed-service-accounts/credential-guard-protected-machine-accounts", "datePublished": "2025-04-11" } } ] } }