You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/ai-services/openai/concepts/provisioned-migration.md
+39-1Lines changed: 39 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,9 @@ This article is intended for existing users of the provisioned throughput offeri
33
33
|Self-service quota requests | Request quota increases without engaging the sales team – many can be autoapproved. |
34
34
|Default provisioned-managed quota in many regions | Get started quickly without having to first request quota. |
35
35
|Transparent information on real-time capacity availability + New deployment flow | Reduced negotiation around availability accelerates time-to-market. |
36
+
| Data zone provisioned deployments | Allows you to leverage Azure's global infrastructure to dynamically route traffic to the data center within the Microsoft defined data zone with the best availability for each request. For more information, see the [deployment types](../how-to/deployment-types.md#data-zone-provisioned) article. |
37
+
| Differentiated pricing | Greater flexibility and control of pricing and performance. In December 2024, we introduced differentiated hourly pricing across [global provisioned](../how-to/deployment-types.md#global-provisioned), [data zone provisioned](../how-to/deployment-types.md#data-zone-provisioned), and [provisioned](../how-to/deployment-types.md#provisioned) deployment types. For more information on the hourly price for each provisioned deployment type, see the [Pricing details](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) page. |
38
+
36
39
37
40
### New hourly/reservation commercial model
38
41
@@ -86,7 +89,20 @@ See the following links for more information. The guidance for reservations and
86
89
> [!NOTE]
87
90
> The following description of payment models doesn't apply to the older "Provisioned Classic (PTU-C)" offering. They only affect the Provisioned (also known as Provisioned Managed) offering. Provisioned Classic continues to be governed by the unchanged monthly commitment payment model.
88
91
89
-
Microsoft has introduced a new "Hourly/reservation" payment model for provisioned deployments. This is in addition to the current **Commitment** payment model, which will continue to be supported until end of life of the currently supported limited model list. Refer to the [supported models on **Commitment payment model**](./provisioned-migration.md#supported-models-on-commitment-payment-model) for the list of supported models on Commitment payment model.
92
+
Microsoft has introduced a new "Hourly/reservation" payment model for provisioned deployments. This is in addition to the current **Commitment** payment model, which will continue to be supported until end of life of the currently supported limited model list. Refer to the [supported models on **Commitment payment model**](./provisioned-migration.md#supported-models-on-commitment-payment-model) for the list of supported models on Commitment payment model. You also have the option to purchase Azure Reservations to support additional discounts.
93
+
94
+
### New Azure Reservations for global and data zone provisioned deployments
95
+
96
+
In addition to the updates for the hourly payment model, new [Azure Reservations](https://aka.ms/oai/docs/ptum-reservations) will be introduced specifically for global and data zone provisioned deployment types. With these new Azure Reservations, every provisioned deployment type will have a separate Azure Reservation that can be purchased to support additional discounts. The mapping between each provisioned deployment type and the associated Azure Reservation are as follows:
97
+
98
+
| Provisioned deployment type | Sku name in code | Azure Reservation product name |
99
+
|---|---|---|
100
+
| Global provisioned |`GlobalProvisionedManaged`| Provisioned Managed Global |
101
+
| Data zone provisioned |`DataZoneProvisionedManaged`| Provisioned Managed Data Zone |
> Azure Reservations for Azure OpenAI provisioned offers are not interchangeable across deployment types. The Azure Reservation purchased must match the provisioned deployment type. If the Azure Reservation purchased does not match the provisioned deployment type, the provisioned deployment will default to the hourly payment model until a matching Azure Reservation product is purchased. For more information, see the [Azure Reservations for Azure OpenAI Service provisioned guidance](https://aka.ms/oai/docs/ptum-reservations).
90
106
91
107
### Commitment payment model
92
108
@@ -383,3 +399,25 @@ The same approaches apply in moving the commitment and deployment within the reg
383
399
### View and edit an existing resource
384
400
385
401
In Azure AI Foundry, select **Management center** > **Quota** > **Provisioned** > **Manage commitments** and select a resource with an existing commitment to view/change it.
402
+
403
+
## Migrating existing deployments to global or data zone provisioned
404
+
Existing customers of provisioned deployments can choose to migrate to global or data zone provisioned deployments to benefit from the lower deployment minimums, granular scale increments, or differentiated pricing available for these deployment types. To learn more about how global and data zone provisioned deployments handle data processing across Azure geographies, see the Azure OpenAI deployment [data processing documentation](https://aka.ms/aoai/docs/data-processing-locations).
405
+
406
+
Two approaches are available for customers to migrate from provisioned deployments to global or data zone provisioned deployments.
407
+
408
+
### Zero downtime migration
409
+
The zero downtime migration approach allows customers to migrate their existing provisioned deployments to global or data zone provisioned deployments without interrupting the existing inference traffic on their deployment. This migration approach minimizes workload interruptions, but does require a customer to have multiple coexisting deployments while shifting traffic over. The process to migrate a provisioned deployment using the zero downtime migration approach is as follows:
410
+
- Create a new deployment using the global or data zone provisioned deployment types in the target Azure OpenAI resource.
411
+
- Transition traffic from the existing regional provisioned deployment type to the newly created global or data zone provisioned deployment until all traffic is offloaded from the existing regional provisioned deployment.
412
+
- Once traffic is migrated over to the new deployment, validate that there are no inference requests being processed on the previous provisioned deployment by ensuring the Azure OpenAI Requests metric does not show any API calls made within 5-10 minutes of the inference traffic being migrated over to the new deployment. For more information on this metric, [see the Monitor Azure OpenAI documentation](https://aka.ms/aoai/docs/monitor-azure-openai).
413
+
- Once you confirm that no inference calls have been made, delete the regional provisioned deployment.
414
+
415
+
### Migration with downtime
416
+
The migration with downtime approach involves migrating existing provisioned deployments to global or data zone provisioned deployments while stopping any existing inference traffic on the original provisioned deployment. This migration approach does not require coexistence of multiple deployments to support but does require workload interruption to complete. The process to migrate a provisioned deployment using the migration with downtime approach is as follows:
417
+
- Validate that there are no inference requests being processed on the previous provisioned deployment by ensuring the Azure OpenAI Requests metric does not show any API calls made within the last 5-10 minutes. For more information on this metric, [see the Monitor Azure OpenAI documentation](https://aka.ms/aoai/docs/monitor-azure-openai).
418
+
- Once you confirm that no inference calls have been made, delete the regional provisioned deployment.
419
+
- Create a new deployment using the global or data zone deployment types in the target Azure OpenAI resource.
420
+
- Once your new deployment has succeeded, you may resume inference traffic on the new global or data zone deployment.
421
+
422
+
## How do I migrate my existing Azure Reservation to the new Azure Reservation products?
423
+
Azure Reservations for Azure OpenAI Service provisioned offers are specific to the provisioned deployment type. If the Azure Reservation purchased does not match the provisioned deployment type, the deployment will default to the hourly payment model. If you choose to migrate to global or data zone provisioned deployments, you might need to purchase a new Azure Reservation for these deployments to support additional discounts. For more information on how to purchase a new Azure Reservation or make changes to an existing Azure Reservation, see the [Azure Reservations for Azure OpenAI Service Provisioned guidance](https://aka.ms/aoai/reservation-transition).
Copy file name to clipboardExpand all lines: articles/ai-services/openai/concepts/provisioned-reservation-update.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ This article is intended for existing users of the provisioned throughput offeri
22
22
23
23
## What's changing?
24
24
25
-
The changes below apply to the global provisioned, data zone provisioned, and provisioned deployment types.
25
+
The changes below apply to the [global provisioned](../how-to/deployment-types.md#global-provisioned), [data zone provisioned](../how-to/deployment-types.md#data-zone-provisioned), and [provisioned](../how-to/deployment-types.md#provisioned) deployment types.
26
26
27
27
> [!IMPORTANT]
28
28
> The changes in this article do not apply to the older *"Provisioned Classic (PTU-C)"* offering. They only affect the Provisioned (also known as the Provisioned Managed) offering.
@@ -32,6 +32,7 @@ Data zone provisioned deployments are available in the same Azure OpenAI resourc
32
32
33
33
For more information, see the [deployment types guide](https://aka.ms/aoai/docs/deployment-types).
34
34
35
+
35
36
### New hourly pricing for global and data zone provisioned deployments
36
37
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/pricing/details/cognitive-services/openai-service/).
0 commit comments