Skip to content

Commit ab82afa

Browse files
Merge pull request #2676 from tferdou1/patch-45
Update instructions for capacity reservation quantity increase
2 parents f59b8f1 + 3fe70eb commit ab82afa

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-machines/capacity-reservation-group-share.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -501,7 +501,7 @@ Zonally deployed virtual machines or virtual machine scale sets from Consumer su
501501

502502
2. Associate existing running zonal virtual machine or virtual machine scale set from the Consumer subscription to the shared capacity reservation group. Set the Virtual Machine or Virtual Machine Scale Set (VMSS) capacityReservationGroup property to the desired shared Capacity Reservation Group. When complete, each target capacity reservation will be overallocated.
503503

504-
3. Increase the reserved quantity of each capacity reservation (CR) to match the allocated Virtual Machine (VM) count. This step requires additional quota and capacity on the Provider subscription to accomodate the workloads from the Consumer subscription. See [Using a shared Capacity Reservation Group](#using-a-shared-capacity-reservation-group). For more information on how to update the reserved count, see [Capacity reservation modify](/azure/virtual-machines/capacity-reservation-modify?tabs=api1%2Capi2%2Capi3#update-the-number-of-instances-reserved)
504+
3. Increase the reserved quantity of each capacity reservation (CR) to match the allocated Virtual Machine (VM) count. If sufficient quota is not available, this step requires additional quota on the Provider subscription to accomodate the workloads from the Consumer subscription. See [Using a shared Capacity Reservation Group](#using-a-shared-capacity-reservation-group). For more information on how to update the reserved count, see [Capacity reservation modify](/azure/virtual-machines/capacity-reservation-modify?tabs=api1%2Capi2%2Capi3#update-the-number-of-instances-reserved)
505505

506506
After the quantity increase, you should see the CR in a fully allocated state with all the virtual machines or virtual machine scale sets allocated. See [View VM allocation with the Instance View](/azure/virtual-machines/capacity-reservation-associate-vm?tabs=api1%2Capi2%2Capi3#view-vm-allocation-with-the-instance-view).
507507

0 commit comments

Comments
 (0)