{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/",
        "slug": "dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement",
        "url": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/"
        },
        "title": "Keep scheduled VM maintenance readiness active while requesting postponement",
        "summary": "DSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "featured": false,
        "image": {
            "theme": "managed-it",
            "label": "Managed IT operations",
            "alt": "A controlled technology lifecycle progressing from assessment to approved production.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/managed-it-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/managed-it-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "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:29+00:00",
        "modified_at": "2026-09-17T16:35:03+00:00",
        "reviewed_on": "2026-09-17",
        "reading_minutes": 2,
        "word_count": 238,
        "potentially_affected": "This guide applies when the owner of an Azure VM affected by planned maintenance cannot accommodate the published schedule and is considering a support request. It addresses the uncertainty of postponement rather than eligibility for starting self-service maintenance.",
        "dse_recommendation": "DSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan.",
        "primary_source": {
            "name": "Use the portal for maintenance notifications - Azure Virtual Machines | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications-portal",
            "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": "<h2>Source facts</h2>\n<p>Microsoft says scheduled maintenance usually cannot be delayed; support can make a best-effort attempt to postpone it. After the self-service window is missed, the portal still shows the window in which Azure will maintain the VM. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications-portal\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a></p>\n<h2>Applicability</h2>\n<p>This guide applies when the owner of an Azure VM affected by planned maintenance cannot accommodate the published schedule and is considering a support request. It addresses the uncertainty of postponement rather than eligibility for starting self-service maintenance.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan. Assign one owner to track the request and another to preserve application readiness for the published window. Record the affected VM identifiers, current scheduled window, support response and business constraint together. Continue the agreed readiness work while the request is unresolved, and avoid announcing an unconfirmed replacement schedule to dependent teams.</p>\n<h2>Verification</h2>\n<p>Before the published window, reconcile the latest portal information with the support response and the workload readiness plan. Record any confirmed schedule change explicitly and retain its source. If no change is confirmed, have the application owner state how the existing window will be handled. Close the request only after the actual maintenance outcome and application condition have been reviewed; a submitted support case alone does not establish a deferred event.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications-portal\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft: Use the portal for maintenance notifications &#8211; Azure Virtual Machines | Microsoft Learn</a></li>\n</ul>",
        "content_text": "Source facts\nMicrosoft says scheduled maintenance usually cannot be delayed; support can make a best-effort attempt to postpone it. After the self-service window is missed, the portal still shows the window in which Azure will maintain the VM. Microsoft Learn\nApplicability\nThis guide applies when the owner of an Azure VM affected by planned maintenance cannot accommodate the published schedule and is considering a support request. It addresses the uncertainty of postponement rather than eligibility for starting self-service maintenance.\nDSE recommendation\nDSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan. Assign one owner to track the request and another to preserve application readiness for the published window. Record the affected VM identifiers, current scheduled window, support response and business constraint together. Continue the agreed readiness work while the request is unresolved, and avoid announcing an unconfirmed replacement schedule to dependent teams.\nVerification\nBefore the published window, reconcile the latest portal information with the support response and the workload readiness plan. Record any confirmed schedule change explicitly and retain its source. If no change is confirmed, have the application owner state how the existing window will be handled. Close the request only after the actual maintenance outcome and application condition have been reviewed; a submitted support case alone does not establish a deferred event.\nOfficial references\n\nMicrosoft: Use the portal for maintenance notifications – Azure Virtual Machines | Microsoft Learn",
        "content_markdown": "## Source facts\n\nMicrosoft says scheduled maintenance usually cannot be delayed; support can make a best-effort attempt to postpone it. After the self-service window is missed, the portal still shows the window in which Azure will maintain the VM. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications-portal)\n\n## Applicability\n\nThis guide applies when the owner of an Azure VM affected by planned maintenance cannot accommodate the published schedule and is considering a support request. It addresses the uncertainty of postponement rather than eligibility for starting self-service maintenance.\n\n## DSE recommendation\n\nDSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan. Assign one owner to track the request and another to preserve application readiness for the published window. Record the affected VM identifiers, current scheduled window, support response and business constraint together. Continue the agreed readiness work while the request is unresolved, and avoid announcing an unconfirmed replacement schedule to dependent teams.\n\n## Verification\n\nBefore the published window, reconcile the latest portal information with the support response and the workload readiness plan. Record any confirmed schedule change explicitly and retain its source. If no change is confirmed, have the application owner state how the existing window will be handled. Close the request only after the actual maintenance outcome and application condition have been reviewed; a submitted support case alone does not establish a deferred event.\n\n## Official references\n\n- [Microsoft: Use the portal for maintenance notifications – Azure Virtual Machines | Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications-portal)"
    },
    "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-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-17"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Keep scheduled VM maintenance readiness active while requesting postponement",
                        "item": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/",
                "url": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/",
                "headline": "Keep scheduled VM maintenance readiness active while requesting postponement",
                "description": "DSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan.",
                "abstract": "DSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan.",
                "articleBody": "Source facts\nMicrosoft says scheduled maintenance usually cannot be delayed; support can make a best-effort attempt to postpone it. After the self-service window is missed, the portal still shows the window in which Azure will maintain the VM. Microsoft Learn\nApplicability\nThis guide applies when the owner of an Azure VM affected by planned maintenance cannot accommodate the published schedule and is considering a support request. It addresses the uncertainty of postponement rather than eligibility for starting self-service maintenance.\nDSE recommendation\nDSE recommends treating a postponement request as an open dependency until the current maintenance information supports a changed plan. Assign one owner to track the request and another to preserve application readiness for the published window. Record the affected VM identifiers, current scheduled window, support response and business constraint together. Continue the agreed readiness work while the request is unresolved, and avoid announcing an unconfirmed replacement schedule to dependent teams.\nVerification\nBefore the published window, reconcile the latest portal information with the support response and the workload readiness plan. Record any confirmed schedule change explicitly and retain its source. If no change is confirmed, have the application owner state how the existing window will be handled. Close the request only after the actual maintenance outcome and application condition have been reviewed; a submitted support case alone does not establish a deferred event.\nOfficial references\n\nMicrosoft: Use the portal for maintenance notifications – Azure Virtual Machines | Microsoft Learn",
                "datePublished": "2026-09-17T16:34:29+00:00",
                "dateModified": "2026-09-17T16:35:03+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260917-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/"
                },
                "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-031-keep-scheduled-vm-maintenance-readiness-active-while-requesting-postponement/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/managed-it-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Keep scheduled VM maintenance readiness active while requesting postponement"
                },
                "articleSection": [
                    "IT"
                ],
                "keywords": [
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "IT",
                        "url": "https://update.dsesecurity.com/topic/it/"
                    }
                ],
                "wordCount": 238,
                "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": "Use the portal for maintenance notifications - Azure Virtual Machines | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/maintenance-notifications-portal"
                }
            }
        ]
    }
}