{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/use-gmsa-only-for-sensor-v2-directory-reads/", "item": { "id": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/", "slug": "use-gmsa-only-for-sensor-v2-directory-reads", "url": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads.md", "json": "https://update.dsesecurity.com/api/v1/posts/use-gmsa-only-for-sensor-v2-directory-reads/" }, "title": "Use a gMSA only for Defender for Identity sensor v2 directory reads", "summary": "Use Configure a gMSA directory service account for Defender for Identity 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": "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/" } ], "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:13:29+00:00", "modified_at": "2026-08-27T13:01:31+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 519, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Configure a gMSA directory service account for Defender for Identity", "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": "Configure a gMSA directory service account for Defender for Identity", "url": "https://learn.microsoft.com/en-us/defender-for-identity/deploy/create-directory-service-account-gmsa", "published_on": "2026-08-03", "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: Use a gMSA only for Defender for Identity sensor v2 directory reads. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official Configure a gMSA directory service account for Defender for Identity from Microsoft supports the following bounded statements:

\n\n

These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health only where the source and recorded environment align.

\n

What the source does not establish

\n

This gMSA is not the remediation action account and should not be granted those permissions. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, and treat examples or options as conditional inputs rather than defaults.

\n

Applicability questions

\n\n

DSE recommendation:

\n

DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation.

\n

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.

\n

Verification and evidence

\n

Keep the source locations Opening overview; Version applicability paragraph adjacent to the sanitized artifacts used for comparison. Prefer sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, with enough identity and timing data for an independent recheck.

\n

Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.

\n

Official references

\n", "content_text": "Treat this document as a focused evidence review: Use a gMSA only for Defender for Identity sensor v2 directory reads. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Configure a gMSA directory service account for Defender for Identity from Microsoft supports the following bounded statements:\n\nThe documented gMSA is for sensor v2.x to read Active Directory data such as objects, changes, and entity information. The research record locates this support at Opening overview.\nSensor v3.x uses LocalSystem for Active Directory interactions and does not require a gMSA or other Directory Service Account. The research record locates this support at Version applicability paragraph.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health only where the source and recorded environment align.\nWhat the source does not establish\nThis gMSA is not the remediation action account and should not be granted those permissions. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, and treat examples or options as conditional inputs rather than defaults.\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 Version applicability paragraph, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nKeep the source locations Opening overview; Version applicability paragraph adjacent to the sanitized artifacts used for comparison. Prefer sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, with enough identity and timing data for an independent recheck.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nConfigure a gMSA directory service account for Defender for Identity — Microsoft", "content_markdown": "Treat this document as a focused evidence review: Use a gMSA only for Defender for Identity sensor v2 directory reads. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Configure a gMSA directory service account for Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/deploy/create-directory-service-account-gmsa) from Microsoft supports the following bounded statements:\n\n- The documented gMSA is for sensor v2.x to read Active Directory data such as objects, changes, and entity information. The research record locates this support at Opening overview.\n\n- Sensor v3.x uses LocalSystem for Active Directory interactions and does not require a gMSA or other Directory Service Account. The research record locates this support at Version applicability paragraph.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health only where the source and recorded environment align.\n\n## What the source does not establish\n\nThis gMSA is not the remediation action account and should not be granted those permissions. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, and treat examples or options as conditional inputs rather than defaults.\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 Version applicability paragraph, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health will be compared with the source, and why that instance?\n\n- How will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations?\n\n- Who approves the conclusion, exception, test window, and rollback threshold?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nKeep the source locations Opening overview; Version applicability paragraph adjacent to the sanitized artifacts used for comparison. Prefer sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, with enough identity and timing data for an independent recheck.\n\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\n\n## Official references\n\n- [Configure a gMSA directory service account for Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/deploy/create-directory-service-account-gmsa) — 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/use-gmsa-only-for-sensor-v2-directory-reads/", "url": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Use a gMSA only for Defender for Identity sensor v2 directory reads", "item": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/#article", "identifier": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/", "url": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/", "headline": "Use a gMSA only for Defender for Identity sensor v2 directory reads", "description": "Use Configure a gMSA directory service account for Defender for Identity to review this narrow operational decision without extending the source beyond…", "abstract": "Use Configure a gMSA directory service account for Defender for Identity to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Treat this document as a focused evidence review: Use a gMSA only for Defender for Identity sensor v2 directory reads. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Configure a gMSA directory service account for Defender for Identity from Microsoft supports the following bounded statements:\n\nThe documented gMSA is for sensor v2.x to read Active Directory data such as objects, changes, and entity information. The research record locates this support at Opening overview.\nSensor v3.x uses LocalSystem for Active Directory interactions and does not require a gMSA or other Directory Service Account. The research record locates this support at Version applicability paragraph.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health only where the source and recorded environment align.\nWhat the source does not establish\nThis gMSA is not the remediation action account and should not be granted those permissions. No current deployment state or change approval follows from the source alone. Validate Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, and treat examples or options as conditional inputs rather than defaults.\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 Version applicability paragraph, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health will be compared with the source, and why that instance?\nHow will the review distinguish a source mismatch from a failure in Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations?\nWho approves the conclusion, exception, test window, and rollback threshold?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Defender for Identity workspaces, sensors, directory-service accounts, action accounts, network paths, roles, and deployment health, observed and expected states, owner, and reason for deviation.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, certificates, domain-controller resources, network capture, cloud connectivity, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nKeep the source locations Opening overview; Version applicability paragraph adjacent to the sanitized artifacts used for comparison. Prefer sensor inventory, service and action-account permissions, health alerts, connectivity tests, portal state, and controlled detection tests, with enough identity and timing data for an independent recheck.\nRecord the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes.\nOfficial references\n\nConfigure a gMSA directory service account for Defender for Identity — Microsoft", "datePublished": "2026-08-27T12:13:29+00:00", "dateModified": "2026-08-27T13:01:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/use-gmsa-only-for-sensor-v2-directory-reads/" }, "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/use-gmsa-only-for-sensor-v2-directory-reads/#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": "Use a gMSA only for Defender for Identity sensor v2 directory reads" }, "articleSection": [ "Cybersecurity", "IT", "Microsoft 365 & Identity" ], "keywords": [ "Cybersecurity", "IT", "Microsoft 365 & Identity", "Checklist", "Advisory priority" ], "genre": "Checklist", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@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/" } ], "wordCount": 519, "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": "Configure a gMSA directory service account for Defender for Identity", "url": "https://learn.microsoft.com/en-us/defender-for-identity/deploy/create-directory-service-account-gmsa", "datePublished": "2026-08-03" } } ] } }