{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/", "slug": "dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale", "url": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/" }, "title": "Recheck Spot recovery ownership when enabling scale-set autoscale", "summary": "Will Spot Try & restore keep maintaining the target count after autoscale is enabled?", "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:04+00:00", "modified_at": "2026-09-10T02:11:18+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 239, "potentially_affected": "Azure Spot VM scale sets whose owners are changing between Try & restore and autoscale-driven capacity management.", "dse_recommendation": "Assign one explicit recovery expectation to the scale set's selected capacity-control configuration.", "primary_source": { "name": "Create a scale set that uses Azure Spot Virtual Machines - Azure Virtual Machine Scale Sets | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/use-spot", "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

Spot Try & restore attempts to recover capacity-evicted instances in a scale set to maintain its target instance count. The feature is disabled when the scale set uses Autoscale; autoscale rules then drive the number of VMs. Microsoft also cautions that autoscaling can attempt to replace evicted Spot capacity but does not guarantee successful allocation. Microsoft Learn.

\n

Applicability

\n

Use this check when adding autoscale to an existing Spot workload or explaining why the previously expected restore mechanism is not acting. Confirm the current controller and eviction policy before attributing a reduced instance count to a failed repair.

\n

DSE recommendation

\n

Assign one explicit recovery expectation to the scale set’s selected capacity-control configuration. Have the workload owner state what should happen after capacity loss and compare that expectation with the actual autoscale rules. Review whether the workload can tolerate a period below its desired population. Keep allocation uncertainty in the operating plan rather than promising that either mechanism restores capacity immediately.

\n

Verification

\n

Use an authorized eviction simulation on a disposable instance and observe the selected mechanism’s response. Track the target count, actual instances and any unsuccessful replacement attempt. Verify application work completion separately from the population count. After changing autoscale configuration, revisit the recovery record so responders do not rely on a Try & restore setting that is inactive under the new configuration.

\n

Official references

\n

Microsoft Learn: Azure Spot Virtual Machines for Virtual Machine Scale Sets. Source reviewed September 9, 2026.

", "content_text": "Source facts\nSpot Try & restore attempts to recover capacity-evicted instances in a scale set to maintain its target instance count. The feature is disabled when the scale set uses Autoscale; autoscale rules then drive the number of VMs. Microsoft also cautions that autoscaling can attempt to replace evicted Spot capacity but does not guarantee successful allocation. Microsoft Learn.\nApplicability\nUse this check when adding autoscale to an existing Spot workload or explaining why the previously expected restore mechanism is not acting. Confirm the current controller and eviction policy before attributing a reduced instance count to a failed repair.\nDSE recommendation\nAssign one explicit recovery expectation to the scale set’s selected capacity-control configuration. Have the workload owner state what should happen after capacity loss and compare that expectation with the actual autoscale rules. Review whether the workload can tolerate a period below its desired population. Keep allocation uncertainty in the operating plan rather than promising that either mechanism restores capacity immediately.\nVerification\nUse an authorized eviction simulation on a disposable instance and observe the selected mechanism’s response. Track the target count, actual instances and any unsuccessful replacement attempt. Verify application work completion separately from the population count. After changing autoscale configuration, revisit the recovery record so responders do not rely on a Try & restore setting that is inactive under the new configuration.\nOfficial references\nMicrosoft Learn: Azure Spot Virtual Machines for Virtual Machine Scale Sets. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nSpot Try & restore attempts to recover capacity-evicted instances in a scale set to maintain its target instance count. The feature is disabled when the scale set uses Autoscale; autoscale rules then drive the number of VMs. Microsoft also cautions that autoscaling can attempt to replace evicted Spot capacity but does not guarantee successful allocation. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/use-spot).\n\n## Applicability\n\nUse this check when adding autoscale to an existing Spot workload or explaining why the previously expected restore mechanism is not acting. Confirm the current controller and eviction policy before attributing a reduced instance count to a failed repair.\n\n## DSE recommendation\n\nAssign one explicit recovery expectation to the scale set’s selected capacity-control configuration. Have the workload owner state what should happen after capacity loss and compare that expectation with the actual autoscale rules. Review whether the workload can tolerate a period below its desired population. Keep allocation uncertainty in the operating plan rather than promising that either mechanism restores capacity immediately.\n\n## Verification\n\nUse an authorized eviction simulation on a disposable instance and observe the selected mechanism’s response. Track the target count, actual instances and any unsuccessful replacement attempt. Verify application work completion separately from the population count. After changing autoscale configuration, revisit the recovery record so responders do not rely on a Try & restore setting that is inactive under the new configuration.\n\n## Official references\n\n[Microsoft Learn: Azure Spot Virtual Machines for Virtual Machine Scale Sets](https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/use-spot). 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-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/", "url": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Recheck Spot recovery ownership when enabling scale-set autoscale", "item": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/", "url": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/", "headline": "Recheck Spot recovery ownership when enabling scale-set autoscale", "description": "Will Spot Try & restore keep maintaining the target count after autoscale is enabled?", "abstract": "Will Spot Try & restore keep maintaining the target count after autoscale is enabled?", "articleBody": "Source facts\nSpot Try & restore attempts to recover capacity-evicted instances in a scale set to maintain its target instance count. The feature is disabled when the scale set uses Autoscale; autoscale rules then drive the number of VMs. Microsoft also cautions that autoscaling can attempt to replace evicted Spot capacity but does not guarantee successful allocation. Microsoft Learn.\nApplicability\nUse this check when adding autoscale to an existing Spot workload or explaining why the previously expected restore mechanism is not acting. Confirm the current controller and eviction policy before attributing a reduced instance count to a failed repair.\nDSE recommendation\nAssign one explicit recovery expectation to the scale set’s selected capacity-control configuration. Have the workload owner state what should happen after capacity loss and compare that expectation with the actual autoscale rules. Review whether the workload can tolerate a period below its desired population. Keep allocation uncertainty in the operating plan rather than promising that either mechanism restores capacity immediately.\nVerification\nUse an authorized eviction simulation on a disposable instance and observe the selected mechanism’s response. Track the target count, actual instances and any unsuccessful replacement attempt. Verify application work completion separately from the population count. After changing autoscale configuration, revisit the recovery record so responders do not rely on a Try & restore setting that is inactive under the new configuration.\nOfficial references\nMicrosoft Learn: Azure Spot Virtual Machines for Virtual Machine Scale Sets. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:23:04+00:00", "dateModified": "2026-09-10T02:11:18+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/" }, "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-532-recheck-spot-recovery-ownership-when-enabling-scale-set-autoscale/#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": "Recheck Spot recovery ownership when enabling scale-set autoscale" }, "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": 239, "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": "Create a scale set that uses Azure Spot Virtual Machines - Azure Virtual Machine Scale Sets | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/use-spot" } } ] } }