{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/", "slug": "dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance", "url": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/" }, "title": "Check the exceptions before starting self-service VM maintenance", "summary": "When should an operator avoid proactively starting an Azure planned-maintenance redeploy?", "format": { "slug": "checklist", "name": "Checklist" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "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-10T00:30:45+00:00", "modified_at": "2026-09-10T00:35:07+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 275, "potentially_affected": "Operators considering self-service maintenance during an Azure VM planned-maintenance wave.", "dse_recommendation": "Review the VM's lifecycle and temporary-disk dependencies before choosing Start now.", "primary_source": { "name": "Maintenance notifications - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications", "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 says self-service maintenance is not available for every VM and directs operators to the Start now status to determine availability. It does not recommend this approach for availability-set deployments. Its contraindications include frequent shutdown or resizing, short-lived VMs due for deletion, and workloads that need to retain substantial local ephemeral-disk state. Existing Scheduled Events integration for proactive failover or graceful shutdown is another listed reason to avoid self-service maintenance. Frequent shutdown or resizing can revert maintenance status and produce additional maintenance impact. Microsoft Learn.

\n

Applicability

\n

Consider this decision only when the VM is affected by a current planned-maintenance wave and a self-service option is offered. Identify availability-set membership, shutdown automation, resize frequency, expected retirement, local-state dependencies, and existing event-driven failover or shutdown coordination. Keep a host-scope Maintenance Configuration distinct from this proactive maintenance action.

\n

DSE recommendation

\n

Review the VM’s lifecycle and temporary-disk dependencies before choosing Start now. Have the application owner approve the reason for taking control of timing and the expected recovery sequence. If a listed contraindication applies, review the documented scheduled-maintenance behavior instead of initiating redeployment just to clear a portal notice. Preserve the VM’s current maintenance state with the decision.

\n

Verification

\n

For an approved self-service action, inspect its result and validate the application’s recovery before processing the next dependent machine. Record whether the state remains completed after later lifecycle changes. If the operation is deferred, retain the applicable scheduled window and the owner responsible for readiness. Treat a new maintenance notice as a fresh state to investigate, not proof that the previous operator failed to perform the action.

\n

Official references

\n

Microsoft Learn: Handling planned maintenance notifications. Source reviewed September 9, 2026.

", "content_text": "Source facts\nMicrosoft says self-service maintenance is not available for every VM and directs operators to the Start now status to determine availability. It does not recommend this approach for availability-set deployments. Its contraindications include frequent shutdown or resizing, short-lived VMs due for deletion, and workloads that need to retain substantial local ephemeral-disk state. Existing Scheduled Events integration for proactive failover or graceful shutdown is another listed reason to avoid self-service maintenance. Frequent shutdown or resizing can revert maintenance status and produce additional maintenance impact. Microsoft Learn.\nApplicability\nConsider this decision only when the VM is affected by a current planned-maintenance wave and a self-service option is offered. Identify availability-set membership, shutdown automation, resize frequency, expected retirement, local-state dependencies, and existing event-driven failover or shutdown coordination. Keep a host-scope Maintenance Configuration distinct from this proactive maintenance action.\nDSE recommendation\nReview the VM’s lifecycle and temporary-disk dependencies before choosing Start now. Have the application owner approve the reason for taking control of timing and the expected recovery sequence. If a listed contraindication applies, review the documented scheduled-maintenance behavior instead of initiating redeployment just to clear a portal notice. Preserve the VM’s current maintenance state with the decision.\nVerification\nFor an approved self-service action, inspect its result and validate the application’s recovery before processing the next dependent machine. Record whether the state remains completed after later lifecycle changes. If the operation is deferred, retain the applicable scheduled window and the owner responsible for readiness. Treat a new maintenance notice as a fresh state to investigate, not proof that the previous operator failed to perform the action.\nOfficial references\nMicrosoft Learn: Handling planned maintenance notifications. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nMicrosoft says self-service maintenance is not available for every VM and directs operators to the Start now status to determine availability. It does not recommend this approach for availability-set deployments. Its contraindications include frequent shutdown or resizing, short-lived VMs due for deletion, and workloads that need to retain substantial local ephemeral-disk state. Existing Scheduled Events integration for proactive failover or graceful shutdown is another listed reason to avoid self-service maintenance. Frequent shutdown or resizing can revert maintenance status and produce additional maintenance impact. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications).\n\n## Applicability\n\nConsider this decision only when the VM is affected by a current planned-maintenance wave and a self-service option is offered. Identify availability-set membership, shutdown automation, resize frequency, expected retirement, local-state dependencies, and existing event-driven failover or shutdown coordination. Keep a host-scope Maintenance Configuration distinct from this proactive maintenance action.\n\n## DSE recommendation\n\nReview the VM’s lifecycle and temporary-disk dependencies before choosing Start now. Have the application owner approve the reason for taking control of timing and the expected recovery sequence. If a listed contraindication applies, review the documented scheduled-maintenance behavior instead of initiating redeployment just to clear a portal notice. Preserve the VM’s current maintenance state with the decision.\n\n## Verification\n\nFor an approved self-service action, inspect its result and validate the application’s recovery before processing the next dependent machine. Record whether the state remains completed after later lifecycle changes. If the operation is deferred, retain the applicable scheduled window and the owner responsible for readiness. Treat a new maintenance notice as a fresh state to investigate, not proof that the previous operator failed to perform the action.\n\n## Official references\n\n[Microsoft Learn: Handling planned maintenance notifications](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications). Source reviewed September 9, 2026." }, "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-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/", "url": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Check the exceptions before starting self-service VM maintenance", "item": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/", "url": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/", "headline": "Check the exceptions before starting self-service VM maintenance", "description": "When should an operator avoid proactively starting an Azure planned-maintenance redeploy?", "abstract": "When should an operator avoid proactively starting an Azure planned-maintenance redeploy?", "articleBody": "Source facts\nMicrosoft says self-service maintenance is not available for every VM and directs operators to the Start now status to determine availability. It does not recommend this approach for availability-set deployments. Its contraindications include frequent shutdown or resizing, short-lived VMs due for deletion, and workloads that need to retain substantial local ephemeral-disk state. Existing Scheduled Events integration for proactive failover or graceful shutdown is another listed reason to avoid self-service maintenance. Frequent shutdown or resizing can revert maintenance status and produce additional maintenance impact. Microsoft Learn.\nApplicability\nConsider this decision only when the VM is affected by a current planned-maintenance wave and a self-service option is offered. Identify availability-set membership, shutdown automation, resize frequency, expected retirement, local-state dependencies, and existing event-driven failover or shutdown coordination. Keep a host-scope Maintenance Configuration distinct from this proactive maintenance action.\nDSE recommendation\nReview the VM’s lifecycle and temporary-disk dependencies before choosing Start now. Have the application owner approve the reason for taking control of timing and the expected recovery sequence. If a listed contraindication applies, review the documented scheduled-maintenance behavior instead of initiating redeployment just to clear a portal notice. Preserve the VM’s current maintenance state with the decision.\nVerification\nFor an approved self-service action, inspect its result and validate the application’s recovery before processing the next dependent machine. Record whether the state remains completed after later lifecycle changes. If the operation is deferred, retain the applicable scheduled window and the owner responsible for readiness. Treat a new maintenance notice as a fresh state to investigate, not proof that the previous operator failed to perform the action.\nOfficial references\nMicrosoft Learn: Handling planned maintenance notifications. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:30:45+00:00", "dateModified": "2026-09-10T00:35:07+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/" }, "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-20260909-071-check-the-exceptions-before-starting-self-service-vm-maintenance/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Check the exceptions before starting self-service VM maintenance" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Checklist", "Information priority" ], "genre": "Checklist", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 275, "timeRequired": "PT2M", "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": "Maintenance notifications - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications" } } ] } }