Skip to content

Commit 8de8d26

Browse files
Merge pull request #253035 from mittalpri/patch-58
Update manage-reserved-vm-instance.md
2 parents 5f238e6 + f3ddda9 commit 8de8d26

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/cost-management-billing/reservations/manage-reserved-vm-instance.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,10 @@ If you're a billing administrator, use following steps to view and manage all re
8585

8686
We don’t allow changing Billing subscription after a reservation is purchased. If you want to change the subscription, use the exchange process to set the right billing subscription for the reservation.
8787

88+
## Change billing frequency for an Azure Reservation
89+
90+
We don’t allow changing billing frequency after a reservation is purchased. If you want to change the billing frequency, use the exchange process to set the right billing frequency for the reservation or select a different billing frequency when setting up a renewal for an already purchased reservation.
91+
8892
## Split a single reservation into two reservations
8993

9094
After you buy more than one resource instance within a reservation, you may want to assign instances within that reservation to different subscriptions. By default, all instances have one scope - either single subscription, resource group or shared. Lets say, you bought a reservation for 10 VM instances and specified the scope to be subscription A. You now want to change the scope for seven VM instances to subscription A and the remaining three to subscription B. Splitting a reservation allows you todo that. After you split a reservation, the original ReservationID is canceled and two new reservations are created. Split doesn't impact the reservation order - there's no new commercial transaction with split and the new reservations have the same end date as the one that was split.

0 commit comments

Comments
 (0)