Azure Revered Instances - Applying reservation to single or multiple VMs
Azure Revered Instances - Applying reservation to single or multiple VMs.
Looks like someone in Azure product team really missed ball on this. Basic things like selecting a VM to apply reservation is not even properly setup or documented. This shows poor work effort provided by the group worked on it.
Chris Watson commented
This is great news, we've been waiting a while for this functionality.
Gerry McPhillips commented
Great to see some updates on how Reserved Instances are scoped, great job!
A lot of organisations have implemented Azure Management Groups to manage multiple Subscriptions, as recommended by Microsoft.
Therefore it would make sense to be able to use a Management Group to scope RI purchases also.
Grateful if this could be added as a feature request if not already.
We are in preview with this feature. Go to this URL to try it out: https://aka.ms/rgscopepreview
• The preview is open only to VM reservations.
• When scoped to a resource group, the reservation discount will apply only to usage on that resource group and not to any other usage. If you don’t have matching usage on the resource group, the reservation will be underutilized and result in wastage.
• You can always update the scope to a different resource group or change it to subscription / shared scope.
• When applying reservation discounts, the resource group discount is applied first, then single subscription reservation and then shared scope reservations.
• Capacity priority, if selected, is still at subscription level and not at resource group level.
1. Resource group name doesn’t show in exchange experience.
2. Resource group filter is not available in browse scope dropdown.
3. Save button will not be disabled during pending/similar states, it will be a no-op if someone presses it.
4. Save button does not disable after save.
5. Switching between Overview and Configuration shows cached data: Do Ctrl + F5 after you change reservation configuration.
Daniel Björk commented
Any update on this from Microsoft?
Martynas Vysniauskas commented
Yes, we have exact same problem, it is not possible to use reserved instances because of complexity to chargeback this service internally. Mapping reservations to a named VM(s)/tags would solve the problem.
Hey, thanks for the feedback.
The most granular scope for reservations currently is subscription.
Just to understand the scenario right - Do you have deployments from multiple cost centers on the same subscription and want to charge back the RI to the cost center that purchases the RI and apply RI only to VMs from this cost center?
We have this feature in the backlog but don't have a date yet.
Please feel free to reach out to me at yashar[@]microsoft[dot]com