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-foundry/openai/how-to/fine-tuning-deploy.md
+36-21Lines changed: 36 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -361,37 +361,52 @@ Azure OpenAI fine-tuning supports the following deployment types.
361
361
362
362
### Standard
363
363
364
-
[Standard deployments](./deployment-types.md#standard) provides a pay-per-call billing model, and the model available in each region as well as throughput may be limited.
365
-
366
-
| Models | Region |
367
-
|--|--|
368
-
|GPT-4o-finetune|East US2, North Central US, Sweden Central|
369
-
|gpt-4o-mini-2024-07-18|North Central US, Sweden Central|
370
-
|GPT-4-finetune|North Central US, Sweden Central|
371
-
|GPT-35-Turbo-finetune|East US2, North Central US, Sweden Central, Switzerland West|
372
-
|GPT-35-Turbo-1106-finetune|East US2, North Central US, Sweden Central, Switzerland West|
373
-
|GPT-35-Turbo-0125-finetune|East US2, North Central US, Sweden Central, Switzerland West|
364
+
[Standard deployments](./deployment-types.md#standard) provide a pay-per-token billing model with data residency confined to the deployed region.
365
+
366
+
| Models | East US2 | North Central US | Sweden Central | Switzerland West |
[Global standard](./deployment-types.md#global-standard) fine-tuned deployments offer [cost savings](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/), but custom model weights may temporarily be stored outside the geography of your Azure OpenAI resource.
378
380
379
-
| Models | Region |
380
-
|--|--|
381
-
|GPT-4.1-finetune|East US2, North Central US, and Sweden Central|
382
-
|GPT-4.1-mini-finetune|East US2, North Central US, and Sweden Central|
383
-
|GPT-4.1-nano-finetune|East US2, North Central US, and Sweden Central|
384
-
|GPT-4o-finetune|East US2, North Central US, and Sweden Central|
385
-
|GPT-4o-mini-finetune|East US2, North Central US, and Sweden Central|
381
+
Global standard deployments are available from all Azure OpenAI regions for the following models:
382
+
383
+
* o4-mini
384
+
* GPT-4.1
385
+
* GPT-4.1-mini
386
+
* GPT-4.1-nano
387
+
* GPT-4o
388
+
* GPT-4o-mini
386
389
387
390
:::image type="content" source="../media/fine-tuning/global-standard.png" alt-text="Screenshot of the global standard deployment user experience with a fine-tuned model." lightbox="../media/fine-tuning/global-standard.png":::
388
391
392
+
### Developer Tier
393
+
394
+
[Developer](./deployment-types.md#developer-for-fine-tuned-models) fine-tuned deployments offer a similar experience as [Global Standard](#global-standard) without an hourly hosting fee, but do not offer an availability SLA. Developer deployments are designed for model candidate evaluation and not for production use.
395
+
396
+
Developer deployments are available from all Azure OpenAI regions for the following models:
397
+
398
+
* GPT-4.1
399
+
* GPT-4.1-mini
400
+
* GPT-4.1-nano
401
+
402
+
389
403
### Provisioned Throughput
390
404
391
-
| Models | Region |
392
-
|--|--|
393
-
|GPT-4o-finetune|North Central US, Sweden Central|
394
-
|GPT-4o-mini-finetune|North Central US, Sweden Central|
[Provisioned throughput](./deployment-types.md#regional-provisioned) fine-tuned deployments offer [predictable performance](../concepts/provisioned-throughput.md) for latency-sensitive agents and applications. They use the same regional provisioned throughput (PTU) capacity as base models, so if you already have regional PTU quota you can deploy your fine-tuned model in support regions.
0 commit comments