{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/", "slug": "dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change", "url": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/" }, "title": "Timestamp planned-maintenance CSV exports before using them as an Azure change inventory", "summary": "Treat an exported impacted-resource list as a snapshot of the export time.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "video-evidence", "label": "Video evidence & analytics", "alt": "Multiple synchronized camera views converging into a verifiable evidence frame.", "card_url": "https://update.dsesecurity.com/assets/editorial/video-evidence-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/video-evidence-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/video-evidence-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/" } ], "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-09-17T16:34:13+00:00", "modified_at": "2026-09-17T16:35:04+00:00", "reviewed_on": "2026-09-17", "reading_minutes": 1, "word_count": 214, "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.", "primary_source": { "name": "Impacted Resources from Azure planned maintenance events - Azure Service Health | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/service-health/impacted-resources-planned-maintenance", "published_on": null, "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": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Impacted Resources from Azure planned maintenance events.

", "content_text": "Source facts\nMicrosoft 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.\nApplicability\nApply 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.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Impacted Resources from Azure planned maintenance events.", "content_markdown": "## Source facts\n\nMicrosoft 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).\n\n## Applicability\n\nApply 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.\n\n## DSE recommendation\n\nDSE 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.\n\n## Verification\n\nCompare 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.\n\n## Official references\n\n[Microsoft Learn: Impacted Resources from Azure planned maintenance events](https://learn.microsoft.com/en-us/azure/service-health/impacted-resources-planned-maintenance)." }, "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/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/", "url": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-17" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Timestamp planned-maintenance CSV exports before using them as an Azure change inventory", "item": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/", "url": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/", "headline": "Timestamp planned-maintenance CSV exports before using them as an Azure change inventory", "description": "Treat an exported impacted-resource list as a snapshot of the export time.", "abstract": "Treat an exported impacted-resource list as a snapshot of the export time.", "articleBody": "Source facts\nMicrosoft 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.\nApplicability\nApply 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.\nDSE recommendation\nDSE 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Impacted Resources from Azure planned maintenance events.", "datePublished": "2026-09-17T16:34:13+00:00", "dateModified": "2026-09-17T16:35:04+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/" }, "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/dse-20260917-047-timestamp-planned-maintenance-csv-exports-before-using-them-as-an-azure-change/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/video-evidence-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/video-evidence-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Timestamp planned-maintenance CSV exports before using them as an Azure change inventory" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 214, "timeRequired": "PT1M", "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": "Impacted Resources from Azure planned maintenance events - Azure Service Health | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/service-health/impacted-resources-planned-maintenance" } } ] } }