Microsoft Foundry fine-tuning (Azure OpenAI) vs Unsloth

Microsoft Foundry fine-tuning (Azure OpenAI)

SFT, DPO and RFT on GPT-4.1 and o4-mini through the OpenAI-shaped /openai/v1 API. No weight export; checkpoints copy only between Azure resources.

Unsloth

The Apache-2.0 core runs on customer hardware and keeps model weights there. Users supply and pay for the GPU.

Microsoft Foundry fine-tuning (Azure OpenAI)

1. Point the OpenAI SDK at https://<resource>.openai.azure.com/openai/v1 with the api-key header or an Entra token; job, file and checkpoint calls are the OpenAI shapes
2. Read prices from the Azure Retail Prices API (meters named like 'gpt-4.1 FT Training global'), not the pricing page, which needs a browser
3. Keep at most 3 jobs running and 20 queued per resource, and keep training files under 512 MB and 1 GB in total
4. Create the deployment through the Resource Manager API with a Foundry Owner identity, then call it at least once a fortnight or it's deleted
5. Query the Models API for deprecationDate before choosing a base model

Unsloth

1. Install with uv pip install unsloth --torch-backend=auto on a CUDA machine; the desktop app is for people
2. Start from the notebook for the model family in unslothai/notebooks; it sets LoRA targets and the chat template
3. Save the LoRA adapter while iterating and merge to 16-bit or GGUF only when you ship
4. If Studio must be reachable by other agents, pass --disable-tools and keep it on 127.0.0.1 behind a tunnel
5. Pin the exact unsloth version; releases land several times a week and don't flag breaking changes