Skip to content

Commit ec712c2

Browse files
Merge pull request #2677 from MicrosoftDocs/main
Auto Publish – main to live - 2025-11-26 18:00 UTC
2 parents 99c3a95 + ab82afa commit ec712c2

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
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

articles/virtual-machines/capacity-reservation-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ From this example accumulation of Minutes Not Available, here's the calculation
8181

8282
| Type | VM Series |
8383
| ----- | ----------- |
84-
| GPU-accelerated compute | ND-series <br> Hb-series <br> Hc-series |
84+
| GPU-accelerated compute | ND-series <br> NCads H100 v5-series <br> Hb-series <br> Hc-series |
8585
| Memory optimized | M series, v1 <br> Msv3 HM <br> Mdsv3 HM and Mdsv3 VHM |
8686

8787
- The following deployment types are supported:

0 commit comments

Comments
 (0)