Microsoft has just announced public preview availability of sharing Capacity Reservation Groups across multiple subscriptions. It was previously possible to deploy virtual machines (VMs) in a CRP within the same subscription only, but now they can be shared with other subscriptions.
This option will make managing configurations easier. Some of the things that will be easier to adjust include resource reuse, centralized capacity management, and more cost-effective scale-out and separating security and capacity concerns.
As a bit of background for those not aware, capacity reservations for Azure Virtual Machines allow you to deploy and manage the compute capacity required to run Azure Virtual Machines. With the recent update, admins can reserve compute capacity for a VM size and hold that reservation for any length of time in any public Azure region or availability zone, while supporting most VM series. Microsoft says you can create and cancel an on-demand capacity reservation at any time without committing.
If you plan to share reserved capacity, you will need at least two subscriptions. First, you’ll need the Provider subscription which is responsible for creating and hosting the CRG. Second, you’ll need a Consumer subscription which grants access to a CRG to deploy VMs with the Capacity Reservation Service Level Agreement (SLA).
Right now, there are a few limitations to be aware of. First, there’s the fact that Portal support is not yet available, though, API and other Azure clients are available. Second and finally, re-provisioning of VMSS VMs using a share CRG is not supported during a zone outage.
You can check out the following link if you want to get started https://aka.ms/computereservationsharing, alternatively you can learn more by checking the documentation and sample code.
Source: Microsoft