Restore the prior quantity when a capacity-reservation increase fails
What state should an operator restore after Azure cannot satisfy an increase to an existing capacity reservation?
Read the playbookDSE security knowledge hubSecurity knowledge,
Security knowledge,
without the noise.
Page 42 of the DSE Security Knowledge Hub, with source-backed guidance, checklists, explainers, and playbooks.
DSE-authoredOfficial sourcesReviewed guidance
Search the library DSE post stream
2,626 articlesGuidance and analysis from DSE
Verify capacity-reservation disassociation separately from VM deallocation
Does stopping and deallocating a VM remove its capacity-reservation association?
Read the guide
Treat proximity-placement intent as a compatibility constraint, not reserved capacity
What does a proximity placement group's VM-size intent establish before deployment, and what remains unguaranteed?
Read the explainer
Size an MPI transport experiment by connection count, not node count alone
What should be calculated before applying Azure HPC guidance for smaller versus larger MPI jobs?
Read the guide
Budget Azure Compute API traffic at both resource and subscription scope
Why can a VM automation job receive throttling even when no individual machine appears unusually busy?
Read the guide
List excluded data before approving an Azure VM restore-point plan
Which disks and mounted data remain outside a proposed Azure VM restore point?
Read the checklist
Check VM watch's selected authentication method before rotating an Event Hubs credential
Why might changing an Event Hubs connection string not change the authentication VM watch actually uses?
Read the guide
Treat VM watch's outbound-disabled attribute as a test-eligibility declaration
Does setting OutboundConnectivityDisabled in VM watch enforce a network restriction?
Read the guide
Measure combined workload demand before choosing a constrained-vCPU Azure size
What capacity tradeoff needs testing when an Azure VM keeps its memory and I/O profile but exposes fewer vCPUs?
Read the guide
Require a separate completion signal for cloud-init custom-data work
Why should an Azure VM's ready state not be the only acceptance signal for custom-data provisioning?
Read the guide