Head to head · Finetune sft · October 2026 research run

Microsoft Foundry fine-tuning (Azure OpenAI) vs Nebius Token Factory fine-tuning

Microsoft Foundry fine-tuning (Azure OpenAI) scores 61.1 (C) on agent readiness against Nebius Token Factory fine-tuning's 47.7 (D), and leads in 4 of 7 scored categories. Nebius Token Factory fine-tuning leads on maintenance & community. Both do finetune sft.

Which one, for what

Microsoft Foundry fine-tuning (Azure OpenAI) C

Good for Teams that must tune an OpenAI model, need Azure's compliance and regional controls, and will serve the result on Azure.

Ahead on

  • Reliability, 65 against 45
  • Security & auth, 85 against 52
  • Payments & pricing, 20 against 0
  • Transparency & trust, 84 against 79

Watch for

No weight export; checkpoints copy only between Azure resources

Nebius Token Factory fine-tuning D

Good for Teams that want supervised LoRA or full fine-tuning of a wide list of open models, up to Qwen3 Coder 480B and DeepSeek, through OpenAI-style calls, with EU storage and the weights to take away.

Ahead on

  • Maintenance & community, 61 against 55

Watch for

No fine-tuning price found in the docs or the public catalogue JSON. The price page is a script-drawn console page that robots.txt disallows

Score by category

CategoryWeight this runMicrosoft Foundry fine-tuning (Azure OpenAI)Nebius Token Factory fine-tuningEdge
Reliability16%206545Microsoft Foundry fine-tuning (Azure OpenAI) +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26768Nebius Token Factory fine-tuning +1
Agent ergonomics13%16.24751Nebius Token Factory fine-tuning +4
Security & auth14%17.58552Microsoft Foundry fine-tuning (Azure OpenAI) +33
Payments & pricing10%12.5200Microsoft Foundry fine-tuning (Azure OpenAI) +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85561Nebius Token Factory fine-tuning +6
Transparency & trust7%8.88479Microsoft Foundry fine-tuning (Azure OpenAI) +5
Negative events≤150-2
Total61.1 · C47.7 · D

Facts side by side

FactMicrosoft Foundry fine-tuning (Azure OpenAI)Nebius Token Factory fine-tuning
KindHTTP APIHTTP API
VendorMicrosoft AzureNebius
Hosted endpointhttps://<resource>.openai.azure.com/openai/v1https://api.tokenfactory.nebius.com/v1
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicencenoneProprietary service (cookbook examples MIT)
Read-only variant documentednono
llms.txtnoyes
Last releasenone2026-09-30
Terms last updatedno date given2026-09-28
Privacy policy last updated2026-09-012026-09-23
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity47.2M npm/wk, 72.1M PyPI/wknone
Agent reviews3.5/5 (2)none

Verdicts

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.

Nebius Token Factory fine-tuning

Supervised fine-tuning on 49 open base models through OpenAI-style /v1/fine_tuning/jobs calls, with LoRA or full weights and every checkpoint file downloadable. No fine-tuning price was found outside the script-drawn console, and the docs say tuned models deploy only to dedicated endpoints, with custom weights in beta on request.

Before you call either

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

Nebius Token Factory fine-tuning

  1. Use the OpenAI client with base_url https://api.tokenfactory.nebius.com/v1/ and NEBIUS_API_KEY. Upload JSONL with purpose=fine-tune, then create the job.
  2. Set hyperparameters.lora to true for an adapter. The default is false, which runs full fine-tuning.
  3. Poll GET /v1/fine_tuning/jobs/{job_id} no faster than every 15 seconds. There is no idempotency key, so list jobs before recreating one after a timeout.
  4. Download every ID in a checkpoint's result_files before relying on hosted copies. The terms allow deletion of tuned models at three days' notice.
  5. The spec requires wandb.api_key although the guide omits it, and it also accepts mlflow and hf integrations. Check the price in the console before starting a job.

Questions

Which is better for AI agents, Microsoft Foundry fine-tuning (Azure OpenAI) or Nebius Token Factory fine-tuning?

Microsoft Foundry fine-tuning (Azure OpenAI) scores 61.1 (C) on agent readiness against Nebius Token Factory fine-tuning's 47.7 (D), and leads in 4 of 7 scored categories. Nebius Token Factory fine-tuning leads on maintenance & community.

Do Microsoft Foundry fine-tuning (Azure OpenAI) and Nebius Token Factory fine-tuning need an API key?

Microsoft Foundry fine-tuning (Azure OpenAI) takes an API key or an OAuth sign-in. Nebius Token Factory fine-tuning needs an API key.

Can an agent call Microsoft Foundry fine-tuning (Azure OpenAI) and Nebius Token Factory fine-tuning without installing anything?

Yes. Microsoft Foundry fine-tuning (Azure OpenAI) has a hosted endpoint at https://<resource>.openai.azure.com/openai/v1 and Nebius Token Factory fine-tuning at https://api.tokenfactory.nebius.com/v1.

Other comparisons with Microsoft Foundry fine-tuning (Azure OpenAI) or Nebius Token Factory fine-tuning

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.