{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/",
        "slug": "dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline",
        "url": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/"
        },
        "title": "Fit scale-set shutdown work inside the already-issued termination deadline",
        "summary": "Can a workload extend its termination delay after Azure has generated the delete event?",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "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:23:29+00:00",
        "modified_at": "2026-09-10T02:11:17+00:00",
        "reviewed_on": "2026-09-09",
        "reading_minutes": 2,
        "word_count": 255,
        "potentially_affected": "Non-Spot Azure scale-set instances with termination notifications enabled and Scheduled Events polling established.",
        "dse_recommendation": "Measure graceful shutdown against the configured delay before enabling the workflow, and treat an issued event's deadline as fixed.",
        "primary_source": {
            "name": "Terminate notification for Azure Virtual Machine Scale Set instances - Azure Virtual Machine Scale Sets | Microsoft Learn",
            "url": "https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification",
            "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>Scale-set termination notifications cover deletion, including autoscale scale-in, but not restart, reimage, redeploy, or stop/deallocate operations. They cannot be enabled for Spot instances. The configured delay is between five and fifteen minutes, and instances must receive the updated model. Once an event exists, its timeout cannot be extended: expiry permits the pending deletion to proceed. A completed workload may approve earlier, although other pending deletes can delay that early execution. <a href=\"https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn</a>.</p>\n<h2>Applicability</h2>\n<p>Use this decision for non-Spot instances whose notification configuration and Scheduled Events polling are already established. Identify the actual delete event and its deadline before starting shutdown work. Do not interpret an unrelated maintenance notification as this configurable termination-delay contract.</p>\n<h2>DSE recommendation</h2>\n<p>Measure graceful shutdown against the configured delay before enabling the workflow, and treat an issued event&#8217;s deadline as fixed. Ask the application owner to prioritize the minimum work needed to preserve an acceptable outcome. Define what to do if that work cannot finish in time. Do not rely on editing the scale-set model after notification as an extension of the current event.</p>\n<h2>Verification</h2>\n<p>Rehearse an approved deletion on a disposable instance and record notification receipt, shutdown completion, acknowledgement if used, and actual termination. Compare elapsed work with the configured deadline. Include a test where the application does not acknowledge early, so expiry behavior is understood. Retain unfinished shutdown work as a design failure requiring a different recovery approach, not as evidence that the platform promised more time.</p>\n<h2>Official references</h2>\n<p><a href=\"https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn: Scale-set termination notifications</a>. Source reviewed September 9, 2026.</p>",
        "content_text": "Source facts\nScale-set termination notifications cover deletion, including autoscale scale-in, but not restart, reimage, redeploy, or stop/deallocate operations. They cannot be enabled for Spot instances. The configured delay is between five and fifteen minutes, and instances must receive the updated model. Once an event exists, its timeout cannot be extended: expiry permits the pending deletion to proceed. A completed workload may approve earlier, although other pending deletes can delay that early execution. Microsoft Learn.\nApplicability\nUse this decision for non-Spot instances whose notification configuration and Scheduled Events polling are already established. Identify the actual delete event and its deadline before starting shutdown work. Do not interpret an unrelated maintenance notification as this configurable termination-delay contract.\nDSE recommendation\nMeasure graceful shutdown against the configured delay before enabling the workflow, and treat an issued event’s deadline as fixed. Ask the application owner to prioritize the minimum work needed to preserve an acceptable outcome. Define what to do if that work cannot finish in time. Do not rely on editing the scale-set model after notification as an extension of the current event.\nVerification\nRehearse an approved deletion on a disposable instance and record notification receipt, shutdown completion, acknowledgement if used, and actual termination. Compare elapsed work with the configured deadline. Include a test where the application does not acknowledge early, so expiry behavior is understood. Retain unfinished shutdown work as a design failure requiring a different recovery approach, not as evidence that the platform promised more time.\nOfficial references\nMicrosoft Learn: Scale-set termination notifications. Source reviewed September 9, 2026.",
        "content_markdown": "## Source facts\n\nScale-set termination notifications cover deletion, including autoscale scale-in, but not restart, reimage, redeploy, or stop/deallocate operations. They cannot be enabled for Spot instances. The configured delay is between five and fifteen minutes, and instances must receive the updated model. Once an event exists, its timeout cannot be extended: expiry permits the pending deletion to proceed. A completed workload may approve earlier, although other pending deletes can delay that early execution. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification).\n\n## Applicability\n\nUse this decision for non-Spot instances whose notification configuration and Scheduled Events polling are already established. Identify the actual delete event and its deadline before starting shutdown work. Do not interpret an unrelated maintenance notification as this configurable termination-delay contract.\n\n## DSE recommendation\n\nMeasure graceful shutdown against the configured delay before enabling the workflow, and treat an issued event’s deadline as fixed. Ask the application owner to prioritize the minimum work needed to preserve an acceptable outcome. Define what to do if that work cannot finish in time. Do not rely on editing the scale-set model after notification as an extension of the current event.\n\n## Verification\n\nRehearse an approved deletion on a disposable instance and record notification receipt, shutdown completion, acknowledgement if used, and actual termination. Compare elapsed work with the configured deadline. Include a test where the application does not acknowledge early, so expiry behavior is understood. Retain unfinished shutdown work as a design failure requiring a different recovery approach, not as evidence that the platform promised more time.\n\n## Official references\n\n[Microsoft Learn: Scale-set termination notifications](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification). 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-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-09-09"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Fit scale-set shutdown work inside the already-issued termination deadline",
                        "item": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/#article",
                "identifier": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/",
                "url": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/",
                "headline": "Fit scale-set shutdown work inside the already-issued termination deadline",
                "description": "Can a workload extend its termination delay after Azure has generated the delete event?",
                "abstract": "Can a workload extend its termination delay after Azure has generated the delete event?",
                "articleBody": "Source facts\nScale-set termination notifications cover deletion, including autoscale scale-in, but not restart, reimage, redeploy, or stop/deallocate operations. They cannot be enabled for Spot instances. The configured delay is between five and fifteen minutes, and instances must receive the updated model. Once an event exists, its timeout cannot be extended: expiry permits the pending deletion to proceed. A completed workload may approve earlier, although other pending deletes can delay that early execution. Microsoft Learn.\nApplicability\nUse this decision for non-Spot instances whose notification configuration and Scheduled Events polling are already established. Identify the actual delete event and its deadline before starting shutdown work. Do not interpret an unrelated maintenance notification as this configurable termination-delay contract.\nDSE recommendation\nMeasure graceful shutdown against the configured delay before enabling the workflow, and treat an issued event’s deadline as fixed. Ask the application owner to prioritize the minimum work needed to preserve an acceptable outcome. Define what to do if that work cannot finish in time. Do not rely on editing the scale-set model after notification as an extension of the current event.\nVerification\nRehearse an approved deletion on a disposable instance and record notification receipt, shutdown completion, acknowledgement if used, and actual termination. Compare elapsed work with the configured deadline. Include a test where the application does not acknowledge early, so expiry behavior is understood. Retain unfinished shutdown work as a design failure requiring a different recovery approach, not as evidence that the platform promised more time.\nOfficial references\nMicrosoft Learn: Scale-set termination notifications. Source reviewed September 9, 2026.",
                "datePublished": "2026-09-10T00:23:29+00:00",
                "dateModified": "2026-09-10T02:11:17+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/dse-20260909-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/"
                },
                "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-507-fit-scale-set-shutdown-work-inside-the-already-issued-termination-deadline/#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": "Fit scale-set shutdown work inside the already-issued termination deadline"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "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": 255,
                "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": "Terminate notification for Azure Virtual Machine Scale Set instances - Azure Virtual Machine Scale Sets | Microsoft Learn",
                    "url": "https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-terminate-notification"
                }
            }
        ]
    }
}