Skip to content

Commit 1973c88

Browse files
Merge pull request #2666 from tferdou1/patch-41
single-VM (Update capacity reservation documentation)
2 parents da341af + d0de6b6 commit 1973c88

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/virtual-machines/capacity-reservation-associate-vm.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -583,6 +583,8 @@ Zonally deployed virtual machines can be converted to using an On Demand Capacit
583583

584584
After the quantity increase, you should see the CR in a fully allocated state with all the virtual machines allocated. See [View VM allocation with the Instance View](#view-vm-allocation-with-the-instance-view).
585585

586+
For information on using shared capacity reservation group, see [Secure existing zonal workloads using zero size reservation in Shared capacity Reservation Group](/azure/virtual-machines/capacity-reservation-group-share?tabs=api-1%2Capi-2%2Capi-3%2Capi-4%2Capi-5%2Capi-6%2Cportal-7#secure-existing-zonal-workloads-using-zero-size-reservation-in-shared-capacity-reservation-group).
587+
586588
## View VM allocation with the Instance View
587589

588590
After the `capacityReservationGroup` property is set, an association now exists between the VM and the group. Azure automatically finds the matching capacity reservation in the group and consumes a reserved slot. The capacity reservation's Instance View reflects the new VM in the `virtualMachinesAllocated` property:

0 commit comments

Comments
 (0)