{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/", "slug": "dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails", "url": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/" }, "title": "Restore the prior quantity when a capacity-reservation increase fails", "summary": "What state should an operator restore after Azure cannot satisfy an increase to an existing capacity reservation?", "format": { "slug": "playbook", "name": "Playbook" }, "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:31:23+00:00", "modified_at": "2026-09-10T00:32:00+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 251, "potentially_affected": "Operators changing the quantity of an existing Azure capacity reservation.", "dse_recommendation": "Preserve the last successfully reserved quantity and use it as the explicit recovery target for an unsuccessful increase.", "primary_source": { "name": "Modify a capacity reservation in Azure - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-modify", "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 warns that an unsuccessful request for more reserved capacity can rarely leave an existing reservation in Failed state and unavailable until its previous quantity is restored. VMs already associated with that failed reservation continue operating normally. The documented recovery can obtain the successfully reserved amount from currentCapacity in the reservation’s instance view and update the requested quantity accordingly. Microsoft Learn.

\n

Applicability

\n

Use this response for a quantity increase on an existing reservation, not as a general remedy for every VM allocation error. Record the intended increase, previous successful amount, reservation identifier, and returned failure. Separate the reservation’s provisioning state from observations of its associated workloads.

\n

DSE recommendation

\n

Preserve the last successfully reserved quantity and use it as the explicit recovery target for an unsuccessful increase. Ask the capacity owner to approve restoring that amount before retrying a larger request. Keep the requested quantity, observed current capacity, and resulting state in one record. Assign any remaining growth requirement its own follow-up instead of interpreting restoration as delivery of the extra capacity.

\n

Verification

\n

After the approved correction, inspect the reservation’s quantity and state again. Compare the restored value with the preserved successful amount and reconcile the list of associated VMs. Have the workload owner check the relevant service separately, particularly if other changes occurred during the incident. Close the recovery only when the reservation-state discrepancy is resolved, and leave the unmet expansion request visible to its owner.

\n

Official references

\n

Microsoft Learn: Modify a capacity reservation in Azure. Source reviewed September 9, 2026.

", "content_text": "Source facts\nMicrosoft warns that an unsuccessful request for more reserved capacity can rarely leave an existing reservation in Failed state and unavailable until its previous quantity is restored. VMs already associated with that failed reservation continue operating normally. The documented recovery can obtain the successfully reserved amount from currentCapacity in the reservation’s instance view and update the requested quantity accordingly. Microsoft Learn.\nApplicability\nUse this response for a quantity increase on an existing reservation, not as a general remedy for every VM allocation error. Record the intended increase, previous successful amount, reservation identifier, and returned failure. Separate the reservation’s provisioning state from observations of its associated workloads.\nDSE recommendation\nPreserve the last successfully reserved quantity and use it as the explicit recovery target for an unsuccessful increase. Ask the capacity owner to approve restoring that amount before retrying a larger request. Keep the requested quantity, observed current capacity, and resulting state in one record. Assign any remaining growth requirement its own follow-up instead of interpreting restoration as delivery of the extra capacity.\nVerification\nAfter the approved correction, inspect the reservation’s quantity and state again. Compare the restored value with the preserved successful amount and reconcile the list of associated VMs. Have the workload owner check the relevant service separately, particularly if other changes occurred during the incident. Close the recovery only when the reservation-state discrepancy is resolved, and leave the unmet expansion request visible to its owner.\nOfficial references\nMicrosoft Learn: Modify a capacity reservation in Azure. Source reviewed September 9, 2026.", "content_markdown": "## Source facts\n\nMicrosoft warns that an unsuccessful request for more reserved capacity can rarely leave an existing reservation in Failed state and unavailable until its previous quantity is restored. VMs already associated with that failed reservation continue operating normally. The documented recovery can obtain the successfully reserved amount from currentCapacity in the reservation’s instance view and update the requested quantity accordingly. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-modify).\n\n## Applicability\n\nUse this response for a quantity increase on an existing reservation, not as a general remedy for every VM allocation error. Record the intended increase, previous successful amount, reservation identifier, and returned failure. Separate the reservation’s provisioning state from observations of its associated workloads.\n\n## DSE recommendation\n\nPreserve the last successfully reserved quantity and use it as the explicit recovery target for an unsuccessful increase. Ask the capacity owner to approve restoring that amount before retrying a larger request. Keep the requested quantity, observed current capacity, and resulting state in one record. Assign any remaining growth requirement its own follow-up instead of interpreting restoration as delivery of the extra capacity.\n\n## Verification\n\nAfter the approved correction, inspect the reservation’s quantity and state again. Compare the restored value with the preserved successful amount and reconcile the list of associated VMs. Have the workload owner check the relevant service separately, particularly if other changes occurred during the incident. Close the recovery only when the reservation-state discrepancy is resolved, and leave the unmet expansion request visible to its owner.\n\n## Official references\n\n[Microsoft Learn: Modify a capacity reservation in Azure](https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-modify). 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-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/", "url": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Restore the prior quantity when a capacity-reservation increase fails", "item": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/", "url": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/", "headline": "Restore the prior quantity when a capacity-reservation increase fails", "description": "What state should an operator restore after Azure cannot satisfy an increase to an existing capacity reservation?", "abstract": "What state should an operator restore after Azure cannot satisfy an increase to an existing capacity reservation?", "articleBody": "Source facts\nMicrosoft warns that an unsuccessful request for more reserved capacity can rarely leave an existing reservation in Failed state and unavailable until its previous quantity is restored. VMs already associated with that failed reservation continue operating normally. The documented recovery can obtain the successfully reserved amount from currentCapacity in the reservation’s instance view and update the requested quantity accordingly. Microsoft Learn.\nApplicability\nUse this response for a quantity increase on an existing reservation, not as a general remedy for every VM allocation error. Record the intended increase, previous successful amount, reservation identifier, and returned failure. Separate the reservation’s provisioning state from observations of its associated workloads.\nDSE recommendation\nPreserve the last successfully reserved quantity and use it as the explicit recovery target for an unsuccessful increase. Ask the capacity owner to approve restoring that amount before retrying a larger request. Keep the requested quantity, observed current capacity, and resulting state in one record. Assign any remaining growth requirement its own follow-up instead of interpreting restoration as delivery of the extra capacity.\nVerification\nAfter the approved correction, inspect the reservation’s quantity and state again. Compare the restored value with the preserved successful amount and reconcile the list of associated VMs. Have the workload owner check the relevant service separately, particularly if other changes occurred during the incident. Close the recovery only when the reservation-state discrepancy is resolved, and leave the unmet expansion request visible to its owner.\nOfficial references\nMicrosoft Learn: Modify a capacity reservation in Azure. Source reviewed September 9, 2026.", "datePublished": "2026-09-10T00:31:23+00:00", "dateModified": "2026-09-10T00:32:00+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/" }, "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-033-restore-the-prior-quantity-when-a-capacity-reservation-increase-fails/#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": "Restore the prior quantity when a capacity-reservation increase fails" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Playbook", "Information priority" ], "genre": "Playbook", "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": 251, "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": "Modify a capacity reservation in Azure - Azure Virtual Machines | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/azure/virtual-machines/capacity-reservation-modify" } } ] } }