AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

finetuning

Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--finetuning at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 18

references/platform-gotchas.md

Platform Gotchas — Top 10

  1. OSS models require "trainingType": "globalStandard" in the request body — undocumented, and all OSS FT jobs fail without it.

  2. Model catalog fine_tune flag is wrong for OSS models — API returns fine_tune = false for all OSS models despite being FT-supported. Hardcode the supported list.

  3. Older SDK versions may fail on /v1/ project endpoints — client.files.create() throws "API version not supported" with older openai package versions. Upgrade to openai>=1.0 and use the /v1/ project endpoint (preferred). If you must use an older SDK, fall back to REST API with the non-project /openai/ endpoint.

  4. ARM "Succeeded" doesn't mean deployment is ready — provisioningState: Succeeded but data plane returns DeploymentNotReady indefinitely. Delete and recreate the deployment, then wait ~5 minutes.

  5. OSS FT deployments may fail with InternalServerError — use the correct provider-specific model.format (e.g., "Mistral AI" not "OpenAI") and try capacity=100.

  6. OSS FT inference hits "Failed to load LoRA" intermittently — deploy with capacity ≥ 100, use 8+ retries with exponential backoff, and wait 2+ minutes after deployment before first call.

  7. ARM REST and az cognitiveservices use different format strings for OSS models — ARM uses provider names ("Microsoft", "Meta"), CLI uses "OpenAI-OSS" for all OSS. Mixing them produces HTTP 500.

  8. Content safety false positives on entity extraction data — PII-dense data (medical records, legal docs, resumes) can trigger "Hate/Fairness" blocks at deployment time. Remove problematic document types.

  9. FT deployments at capacity=1 are severely rate-limited (~1 RPM) — evaluating 10 samples takes ~10 minutes. Use capacity ≥ 100 for eval workloads and exponential backoff.

  10. Wrong resource endpoint is a silent killer — jobs submitted to the wrong Foundry resource succeed via API but don't appear in the portal. Always verify the endpoint matches your Foundry project.