The ability to share Capacity Reservation Groups (CRGs) with subscriptions is now in Public Preview.
Previously, customers could deploy VMs in a Capacity Reservation Group within the same subscription only. On-demand Capacity Reservation Group (CRG) can now be shared with other subscriptions. Using this option can make it easier to manage some common configuration needs like resource reuse, centralized capacity management, more cost-effective scale-out and separating security and capacity concerns.
For example, for resource reuse scenario, customers cannot use a Disaster Recovery Capacity Reservation Group for development testing purposes across subscriptions today. With the sharing feature, customers will be able to repurpose the Capacity Reservation Group for non-production workloads.
User Experience:
Sharing reserved capacity requires at least two subscriptions:
- Provider subscription – the subscription that creates and hosts the Capacity Reservation Group and member Capacity Reservations.
- Consumer subscription - another subscription that is granted access to the reserved capacity, obtaining the ability to deploy virtual machines (VMs) with the Capacity Reservation Service Level Agreement (SLA).
The deployed VMs must match one of the Capacity Reservations in the Capacity Reservation groups on SKU, location, and availability zone if applicable.
Example:
In this example, Subscription A is the Provider and Subscription B is the Consumer subscription.
- Step 1: Share CRG X
- A rights administrator in Subscription B must grant User “A” CRG “share” permissions.
- User “A” (CRG owner) must then update the “sharing profile” of CRG X to include Subscription B. A given Capacity Reservation Group can be shared with up to 100 consumer subscriptions
- Step 2: grant user access to CRG X
- A rights administrator in Subscription A must grant User “B” (VM owner) read and deploy rights to CRG X in Subscription A.
- Once complete, User B can deploy VMs by setting the “capacityReservationGroup” property on Virtual Machines or Virtual Machine Scale Sets.
Public Preview limitations:
- Portal support is not available; API and other Azure clients are available.
- Re-provisioning of VMSS VMs using a shared Capacity Reservation Group is not supported during a zone outage.
Resources to get started: https://aka.ms/computereservationsharing.
Additionally, you can read the on demand capacity reservation documentation that includes sample code.
Background:
On-demand capacity reservations for Azure Virtual Machines let you deploy and manage the compute capacity required to run Azure Virtual Machines. This new feature enables your IT organization to reserve compute capacity for a VM size. The reservation can be for any length of time in any public Azure region or availability zone and supports most VM series. You can create and cancel an on-demand capacity reservation at any time; no commitment is required.
The ability for you to access compute capacity–with SLA guarantees–ahead of actual VM deployments is particularly important to ensure the availability of business-critical applications running on Azure. On-demand capacity reservations can be combined with Azure Reserved VM Instances (RIs) to significantly reduce costs.
Read the blog (link to tech community blog for Public Preview of specialty SKUs) for more details. You can also watch this video or read the documentation
Microsoft