Skip to content

Commit d76f06f

Browse files
authored
Update and rename provisioned-reservation-update to provisioned-reservation-update.md
1 parent 95e6196 commit d76f06f

File tree

1 file changed

+1
-26
lines changed

1 file changed

+1
-26
lines changed

articles/ai-services/openai/concepts/provisioned-reservation-update renamed to articles/ai-services/openai/concepts/provisioned-reservation-update.md

Lines changed: 1 addition & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -23,12 +23,10 @@ For more information, see the [deployment types guide](https://aka.ms/aoai/docs/
2323
In August 2024, Microsoft announced that Provisioned deployments would move to a new [hourly payment model](./provisioned-migration.md) with the option to purchase Azure Reservations to support additional discounts. In December's provisioned update, we will be introducing differentiated hourly pricing across Global provisioned, Data zone provisioned, and provisioned deployment types. For more information on the hourly price for each Provisioned deployment type, see the [Pricing details page](https://azure.microsoft.com/en-us/pricing/details/cognitive-services/openai-service/).
2424

2525
### New Azure Reservations for Globl and Data zone provisioned deployments
26+
In addition to the updates for the hourly payment model, new Azure Reservations will be introduced specifically for
2627

2728
## Migrating existing deployments to Global or Data zone provisioned
2829

29-
Existing customers can choose to migrate their existing resources from the Commitment to the Hourly/Reservation payment model to benefit from the ability to deploy the latest models, or to consolidate discounting for diverse deployments under a single reservation.
30-
31-
Two approaches are available for customers to migrate resources using the Commitment model to the Hourly/Reservation model.
3230

3331
### Zero downtime migration
3432

@@ -37,27 +35,4 @@ Two approaches are available for customers to migrate resources using the Commit
3735
3836
### Migration with downtime
3937

40-
The managed migration approach involves the customer partnering with Microsoft to bulk-migrate all the PTU commitments in a subscription/region at the same time. It works like this:
41-
42-
1. The customer will engage their account team and request a managed migration. A migration owner from the Microsoft team will be assigned to assist the customer with migration.
43-
2. A date will be selected when all resources within each of the customers' subscriptions and regions containing current PTU commitments will be migrated from committed to hourly/reservation billing model. Multiple subscriptions and regions can be migrated on the same date.
44-
3. On the agreed-upon date:
45-
* The customer will purchase regional reservations to cover the committed PTUs that will be converted and pass the reservation information to their Microsoft migration contact.
46-
* Within 2-3 business days, all commitments will be proactively canceled and deployments previously under commitments will begin using the hourly/reservation payment model.
47-
* In the billing period after the one with the reservation purchase, the customer will receive a credit for the reservation purchase covering the portions of the commitments that were canceled, starting from the time of the reservation purchase.
48-
49-
Customers must reach out to their account teams to schedule a managed migration.
50-
51-
**Managed migration advantages:**
52-
53-
- Bulk migration of all commitments in an subscription/region is beneficial for customers with many commitments.
54-
- Seamless cost migration: No possibility of double-billing or extra hourly charges.
55-
56-
**Managed migration disadvantages:**
57-
58-
- All commitments in a subscription/region must be migrated at the same time.
59-
- Needing to coordinate a time for migration with the Microsoft team.
60-
61-
6238

63-
In Azure OpenAI Studio, select **Quota** > **Provisioned** > **Manage commitments** and select a resource with an existing commitment to view/change it.

0 commit comments

Comments
 (0)