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

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.

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.