# Include Arc machines explicitly in the built-in Windows time-zone audit

> Review the example policy's machine-population parameter along with its expected time zone.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-166-include-arc-machines-explicitly-in-the-built-in-windows-time-zone-audit/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:32:14+00:00
- Modified: 2026-09-17T16:46:29+00:00
- Last reviewed by DSE: 2026-09-17
- Resource type: Guide
- DSE priority: Information
- Topics: Cybersecurity, IT
- Reading time: 1 minutes

## What you need to know

Review the example policy's machine-population parameter along with its expected time zone.

## Potentially affected

Use this review for that documented built-in audit policy, with an approved set of Windows machines. Identify which machines are Azure VMs and which are Arc-enabled. Establish the intended time-zone value from the organization's requirement rather than copying the documentation's example value.

## DSE recommendation

DSE recommends recording both the machine population and expected time zone in the assignment request.

## Article

## Source facts

Microsoft’s built-in Windows time-zone audit example instructs the operator to enable Include Arc connected servers when the environment includes Arc machines, and to select the desired time zone. It also calls for Machine Configuration prerequisites to be deployed before assignment. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/governance/machine-configuration/how-to/assign-built-in-policies).

## Applicability

Use this review for that documented built-in audit policy, with an approved set of Windows machines. Identify which machines are Azure VMs and which are Arc-enabled. Establish the intended time-zone value from the organization’s requirement rather than copying the documentation’s example value.

## DSE recommendation

DSE recommends recording both the machine population and expected time zone in the assignment request. Review the actual definition’s parameters and prerequisites before saving the assignment. Include a representative Arc machine in the pilot when Arc coverage is intended. Treat the audit as evidence collection, and handle any corrective machine change through a separate approved action.

## Verification

Read back the assignment parameters and compare them with the approved population. Inspect results for a representative Azure VM and, where in scope, an Arc machine. Confirm that each result belongs to the intended assignment and expected value. Investigate a missing result before counting the machine as assessed, and retain the parameter evidence with the pilot record.

## Official references

[Microsoft Learn: Discover And Assign Built In Machine Configuration Policies](https://learn.microsoft.com/en-us/azure/governance/machine-configuration/how-to/assign-built-in-policies).

## Primary reference

- Name: Discover And Assign Built In Machine Configuration Policies - Azure Machine Configuration | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/governance/machine-configuration/how-to/assign-built-in-policies
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Include Arc machines explicitly in the built-in Windows time-zone audit,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-166-include-arc-machines-explicitly-in-the-built-in-windows-time-zone-audit/
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.