# Timestamp planned-maintenance CSV exports before using them as an Azure change inventory

> Treat an exported impacted-resource list as a snapshot of the export time.

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-17T16:34:13+00:00
- Modified: 2026-09-17T16:35:04+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

Treat an exported impacted-resource list as a snapshot of the export time.

## Potentially affected

Apply this review when a team uses a CSV to prepare maintenance work or notify resource owners. Record the subscription selection, export time and event identifiers. The snapshot should not be treated as a continuously updated list or a complete copy of all API fields.

## DSE recommendation

DSE recommends attaching the export timestamp and scope to the worksheet shared with change owners.

## Article

## Source facts

Microsoft describes the planned-maintenance CSV as a static snapshot of the active events in the Service Health planned-maintenance view. It includes event properties and additional event detail, but only a subset of the event information available through the Service Health API. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/service-health/impacted-resources-planned-maintenance).

## Applicability

Apply this review when a team uses a CSV to prepare maintenance work or notify resource owners. Record the subscription selection, export time and event identifiers. The snapshot should not be treated as a continuously updated list or a complete copy of all API fields.

## DSE recommendation

DSE recommends attaching the export timestamp and scope to the worksheet shared with change owners. Assign someone to recheck the relevant live events before decisions that depend on the list. Keep local notes distinct from source fields, and record which event each proposed action addresses. Preserve the earlier export when comparing changes over time.

## Verification

Compare a fresh view or permitted API response with the exported event identifiers before the planned work. Reconcile added, removed or revised event details explicitly. Check that owners can distinguish the original snapshot from later annotations. Retain the comparison time and unresolved differences so the change record shows exactly which source state informed the decision.

## Official references

[Microsoft Learn: Impacted Resources from Azure planned maintenance events](https://learn.microsoft.com/en-us/azure/service-health/impacted-resources-planned-maintenance).

## Primary reference

- Name: Impacted Resources from Azure planned maintenance events - Azure Service Health | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/service-health/impacted-resources-planned-maintenance
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Timestamp planned-maintenance CSV exports before using them as an Azure change inventory,” DSE Security, https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/
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.