# Scope Support boundary for high accuracy time in observed AD/DNS state > Use Support boundary for high accuracy time to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/scope-support-boundary-for-high-accuracy-time-in-observed-ad-dns-state/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:00:35+00:00 - Modified: 2026-08-27T17:37:18+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Briefing - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Support boundary for high accuracy time to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Support boundary for high accuracy time ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to resolve one bounded operational decision: Scope Support boundary for high accuracy time in observed AD/DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Support boundary for high accuracy time](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/support-boundary-high-accuracy-time) from Microsoft supports the following bounded statements: - At Introduction below H1, Microsoft states: “This article describes the support boundaries for the Windows Time service (W32Time) in environments that require highly accurate and stable system time.” The research record locates this support at Introduction below H1. - At Introduction below H1, Microsoft states: “_Applies to:_ Windows Server (All supported versions) including Azure Stack HCI, Windows client (All supported versions).” The research record locates this support at Introduction below H1. Keep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions. ## What the source does not establish The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, and treat examples or options as conditional inputs rather than defaults. ## Applicability questions - For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - Which owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions? - What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation? - Which success, stop, and escalation criteria are written before testing begins? ## DSE recommendation: 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 Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation. If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention. ## Verification and evidence Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Introduction below H1; Introduction below H1. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator. Label this evidence set DSE-20260827-411 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. 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. ## Official references - [Support boundary for high accuracy time](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/support-boundary-high-accuracy-time) — Microsoft ## Primary reference - Name: Support boundary for high accuracy time - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/support-boundary-high-accuracy-time - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Scope Support boundary for high accuracy time in observed AD/DNS state,” DSE Security, https://update.dsesecurity.com/updates/scope-support-boundary-for-high-accuracy-time-in-observed-ad-dns-state/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.