{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/schedule-identity-reports-without-treating-them-as-real-time-detection/", "item": { "id": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/", "slug": "schedule-identity-reports-without-treating-them-as-real-time-detection", "url": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection.md", "json": "https://update.dsesecurity.com/api/v1/posts/schedule-identity-reports-without-treating-them-as-real-time-detection/" }, "title": "Schedule identity reports without treating them as real-time detection", "summary": "Use Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) to review this narrow operational decision without extending the source beyond its stated scope.", "format": { "slug": "briefing", "name": "Briefing" }, "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:50+00:00", "modified_at": "2026-08-27T13:04:09+00:00", "reviewed_on": "2026-08-26", "reading_minutes": 3, "word_count": 499, "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview)", "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": "Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview)", "url": "https://learn.microsoft.com/en-us/defender-for-identity/reports", "published_on": "2026-07-02", "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 resolve one bounded operational decision: Schedule identity reports without treating them as real-time detection. Only the official source and traced locations below supply facts. Confirm applicability before acting.

\n

Source fact:

\n

The official Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) from Microsoft supports the following bounded statements:

\n\n

The source support ends with the statements listed above. Use them to examine identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions in the applicable environment, not to imply a wider guarantee.

\n

What the source does not establish

\n

The reporting feature is marked Preview; scheduled summaries do not replace alert monitoring, source logs, incident records, or exposure remediation. 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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

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, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.

\n

Verification and evidence

\n

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening overview; Opening overview. Favor sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, linked to stable identifiers, time, and operator.

\n

Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.

\n

Official references

\n", "content_text": "Use this document to resolve one bounded operational decision: Schedule identity reports without treating them as real-time detection. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) from Microsoft supports the following bounded statements:\n\nDefender for Identity reports can be generated on demand or configured for periodic email delivery. The research record locates this support at Opening overview.\nAvailable report subjects include system activity summaries, sensitive-group changes, and passwords exposed in cleartext. The research record locates this support at Opening overview.\n\nThe source support ends with the statements listed above. Use them to examine identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe reporting feature is marked Preview; scheduled summaries do not replace alert monitoring, source logs, incident records, or exposure remediation. 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 overview, 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?\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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\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, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening overview; Opening overview. Favor sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, linked to stable identifiers, time, and operator.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nDownload and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) — Microsoft", "content_markdown": "Use this document to resolve one bounded operational decision: Schedule identity reports without treating them as real-time detection. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview)](https://learn.microsoft.com/en-us/defender-for-identity/reports) from Microsoft supports the following bounded statements:\n\n- Defender for Identity reports can be generated on demand or configured for periodic email delivery. The research record locates this support at Opening overview.\n\n- Available report subjects include system activity summaries, sensitive-group changes, and passwords exposed in cleartext. The research record locates this support at Opening overview.\n\nThe source support ends with the statements listed above. Use them to examine identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions in the applicable environment, not to imply a wider guarantee.\n\n## What the source does not establish\n\nThe reporting feature is marked Preview; scheduled summaries do not replace alert monitoring, source logs, incident records, or exposure remediation. 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 overview, 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- 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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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\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, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening overview; Opening overview. Favor sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, linked to stable identifiers, time, and operator.\n\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\n\n## Official references\n\n- [Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview)](https://learn.microsoft.com/en-us/defender-for-identity/reports) — 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/schedule-identity-reports-without-treating-them-as-real-time-detection/", "url": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-08-26" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Schedule identity reports without treating them as real-time detection", "item": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/#article", "identifier": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/", "url": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/", "headline": "Schedule identity reports without treating them as real-time detection", "description": "Use Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) to review this narrow operational decision without…", "abstract": "Use Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) to review this narrow operational decision without extending the source beyond its stated scope.", "articleBody": "Use this document to resolve one bounded operational decision: Schedule identity reports without treating them as real-time detection. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) from Microsoft supports the following bounded statements:\n\nDefender for Identity reports can be generated on demand or configured for periodic email delivery. The research record locates this support at Opening overview.\nAvailable report subjects include system activity summaries, sensitive-group changes, and passwords exposed in cleartext. The research record locates this support at Opening overview.\n\nThe source support ends with the statements listed above. Use them to examine identity detections, contributing events, entities, alert logic, tuning, exclusions, investigation, and response decisions in the applicable environment, not to imply a wider guarantee.\nWhat the source does not establish\nThe reporting feature is marked Preview; scheduled summaries do not replace alert monitoring, source logs, incident records, or exposure remediation. 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 overview, 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?\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. Make the source, asset scope, owner, and expected outcome explicit in the review record. 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.\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, sensor health, time, network visibility, cloud analytics, endpoint evidence, and security operations, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nEvidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Opening overview; Opening overview. Favor sanitized alerts, source events, entity timelines, tuning conditions, exclusion scope, analyst findings, and response outcomes, linked to stable identifiers, time, and operator.\nPreserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent.\nOfficial references\n\nDownload and schedule Defender for Identity reports in Microsoft Defender XDR (Preview) — Microsoft", "datePublished": "2026-08-27T12:12:50+00:00", "dateModified": "2026-08-27T13:04:09+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/schedule-identity-reports-without-treating-them-as-real-time-detection/" }, "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/schedule-identity-reports-without-treating-them-as-real-time-detection/#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": "Schedule identity reports without treating them as real-time detection" }, "articleSection": [ "Cybersecurity", "IT", "Microsoft 365 & Identity" ], "keywords": [ "Cybersecurity", "IT", "Microsoft 365 & Identity", "Briefing", "Advisory priority" ], "genre": "Briefing", "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": 499, "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": "Download and schedule Defender for Identity reports in Microsoft Defender XDR (Preview)", "url": "https://learn.microsoft.com/en-us/defender-for-identity/reports", "datePublished": "2026-07-02" } } ] } }