{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/link-fragmented-user-accounts-with-evidence-of-common-identity/", "item": { "id": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/", "slug": "link-fragmented-user-accounts-with-evidence-of-common-identity", "url": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity.md", "json": "https://update.dsesecurity.com/api/v1/posts/link-fragmented-user-accounts-with-evidence-of-common-identity/" }, "title": "Link fragmented user accounts only with evidence of common identity", "summary": "Use Manage related identities and accounts in Microsoft Defender for Identity 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": "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:12:52+00:00", "modified_at": "2026-08-27T13:04:09+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 Manage related identities and accounts in Microsoft 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": "Manage related identities and accounts in Microsoft Defender for Identity", "url": "https://learn.microsoft.com/en-us/defender-for-identity/manage-related-identities-accounts", "published_on": "2026-07-23", "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": "

Use this document to connect an official requirement or behavior to observable evidence: Link fragmented user accounts only with evidence of common identity. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official Manage related identities and accounts in Microsoft Defender for Identity from Microsoft supports the following bounded statements:

\n\n

Keep the evidence boundary at these traced claims. They support a review of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions; they do not support conclusions outside the source’s stated conditions.

\n

What the source does not establish

\n

A manual link is an analyst assertion, not authoritative proof that two accounts have the same owner; preserve review and rollback evidence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.

\n

Applicability questions

\n\n

DSE recommendation:

\n

DSE recommends using the cited source as the evidence anchor for this decision. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.

\n

For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.

\n

Verification and evidence

\n

Tie each conclusion back to Opening fragmentation overview; Manual correlation overview and to observable material such as sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes. Preserve provenance and stable identifiers without copying secrets into the evidence set.

\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": "Use this document to connect an official requirement or behavior to observable evidence: Link fragmented user accounts only with evidence of common identity. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Manage related identities and accounts in Microsoft Defender for Identity from Microsoft supports the following bounded statements:\n\nOne person can have personal, privileged, legacy, cloud, or orphaned accounts across Active Directory, Entra ID, and non-Microsoft identity providers. The research record locates this support at Opening fragmentation overview.\nMicrosoft supports manually linking or unlinking related accounts to address fragmented identity views. The research record locates this support at Manual correlation overview.\n\nKeep the evidence boundary at these traced claims. They support a review of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nA manual link is an analyst assertion, not authoritative proof that two accounts have the same owner; preserve review and rollback evidence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Opening fragmentation overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Manual correlation overview, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions 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, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nTie each conclusion back to Opening fragmentation overview; Manual correlation overview and to observable material such as sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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\nManage related identities and accounts in Microsoft Defender for Identity — Microsoft", "content_markdown": "Use this document to connect an official requirement or behavior to observable evidence: Link fragmented user accounts only with evidence of common identity. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Manage related identities and accounts in Microsoft Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/manage-related-identities-accounts) from Microsoft supports the following bounded statements:\n\n- One person can have personal, privileged, legacy, cloud, or orphaned accounts across Active Directory, Entra ID, and non-Microsoft identity providers. The research record locates this support at Opening fragmentation overview.\n\n- Microsoft supports manually linking or unlinking related accounts to address fragmented identity views. The research record locates this support at Manual correlation overview.\n\nKeep the evidence boundary at these traced claims. They support a review of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions; they do not support conclusions outside the source’s stated conditions.\n\n## What the source does not establish\n\nA manual link is an analyst assertion, not authoritative proof that two accounts have the same owner; preserve review and rollback evidence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at Opening fragmentation overview, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Manual correlation overview, which observable configuration, record, or test can confirm applicability here?\n\n- Which deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions 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, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.\n\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\n\n## Verification and evidence\n\nTie each conclusion back to Opening fragmentation overview; Manual correlation overview and to observable material such as sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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- [Manage related identities and accounts in Microsoft Defender for Identity](https://learn.microsoft.com/en-us/defender-for-identity/manage-related-identities-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/link-fragmented-user-accounts-with-evidence-of-common-identity/", "url": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Link fragmented user accounts only with evidence of common identity", "item": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/#article", "identifier": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/", "url": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/", "headline": "Link fragmented user accounts only with evidence of common identity", "description": "Use Manage related identities and accounts in Microsoft Defender for Identity to review this narrow operational decision without extending the source…", "abstract": "Use Manage related identities and accounts in Microsoft Defender for Identity 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: Link fragmented user accounts only with evidence of common identity. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Manage related identities and accounts in Microsoft Defender for Identity from Microsoft supports the following bounded statements:\n\nOne person can have personal, privileged, legacy, cloud, or orphaned accounts across Active Directory, Entra ID, and non-Microsoft identity providers. The research record locates this support at Opening fragmentation overview.\nMicrosoft supports manually linking or unlinking related accounts to address fragmented identity views. The research record locates this support at Manual correlation overview.\n\nKeep the evidence boundary at these traced claims. They support a review of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions; they do not support conclusions outside the source’s stated conditions.\nWhat the source does not establish\nA manual link is an analyst assertion, not authoritative proof that two accounts have the same owner; preserve review and rollback evidence. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at Opening fragmentation overview, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Manual correlation overview, which observable configuration, record, or test can confirm applicability here?\nWhich deployed instance of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions 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, sensor health, time, network visibility, cloud analytics, endpoint evidence, 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. Anchor the review in the cited section and keep observation separate from interpretation. Record the source location, examined part of identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions, observed and expected states, owner, and reason for deviation.\nFor an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence.\nVerification and evidence\nTie each conclusion back to Opening fragmentation overview; Manual correlation overview and to observable material such as sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes. Preserve provenance and stable identifiers without copying secrets into the evidence set.\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\nManage related identities and accounts in Microsoft Defender for Identity — Microsoft", "datePublished": "2026-08-27T12:12:52+00:00", "dateModified": "2026-08-27T13:04:09+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/link-fragmented-user-accounts-with-evidence-of-common-identity/" }, "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/link-fragmented-user-accounts-with-evidence-of-common-identity/#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": "Link fragmented user accounts only with evidence of common identity" }, "articleSection": [ "Cybersecurity", "IT", "Microsoft 365 & Identity" ], "keywords": [ "Cybersecurity", "IT", "Microsoft 365 & Identity", "Guide", "Advisory priority" ], "genre": "Guide", "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": "Manage related identities and accounts in Microsoft Defender for Identity", "url": "https://learn.microsoft.com/en-us/defender-for-identity/manage-related-identities-accounts", "datePublished": "2026-07-23" } } ] } }