Deployment and Fine-Tuning Issues with Phi-4 on Serverless API #119
Replies: 7 comments 5 replies
-
I can deploy and finetune Phi 4 Mini with the same steps, and it worked. Don't know what happened with Phi 4. Thank you |
Beta Was this translation helpful? Give feedback.
-
adding @kinfey and @nitya from my team who work with Phi4 and Finetuning respectively - can we explore the issue above? @kinfey looks like the focus is fine tuning with Phi4 in Foundry |
Beta Was this translation helpful? Give feedback.
-
Yes, I can just fine-tune phi 4 mini
…On Mon, Aug 4, 2025 at 5:35 PM Kinfey ***@***.***> wrote:
I think just Phi-4-mini can be fine tuning in Azure AI Foundry
—
Reply to this email directly, view it on GitHub
<#119 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJYP3L42F2CFUPQ4BSMGBTD3L4ZNXAVCNFSM6AAAAACDA4DTHKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGOJYGY4TSNQ>
.
You are receiving this because you authored the thread.Message ID:
<azure-ai-foundry/discussions/repo-discussions/119/comments/13986996@
github.com>
|
Beta Was this translation helpful? Give feedback.
-
@mrzaizai2k use hub resource , I think it can ft ![]() ![]() |
Beta Was this translation helpful? Give feedback.
-
This is new, I now can deploy Phi 4 on Chrome browser, but still can not finetune it |
Beta Was this translation helpful? Give feedback.
-
But I still need to finetune Phi 4, I still have problem with task type. pls |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Unlike the Phi-4 Mini model, the Phi-4 fine-tuning interface does not provide an option to select the task type
This is when finetuning with Phi 4
This is when finetuning with Phi 4 Mini
When accessing the Phi-4 model via the Fine-Tune tab without applying catalog filters, the Serverless API option is not visible. But in Model Catalog tab, it said we can finetune via Serverless. This inconsistency may cause confusion for users expecting uniform access across different navigation paths.
When using Model Catalog tab

I check in detail, and we don't have any problem with region (Eastus2) and quota, I have hub-project based. I check all the documents and see no related issues
When using Fine tuning tab

Beta Was this translation helpful? Give feedback.
All reactions