Head to head · Fine-tuning · October 2026 research run
Microsoft Foundry fine-tuning (Azure OpenAI) vs Vertex AI Gemini tuning
Vertex AI Gemini tuning scores 64.4 (B) on agent readiness against Microsoft Foundry fine-tuning (Azure OpenAI)'s 59.2 (C), and leads in 4 of 7 scored categories. Microsoft Foundry fine-tuning (Azure OpenAI) leads on reliability and security & auth. Both do fine-tuning.
Best fine-tuning services for AI models · All 36 fine-tuning comparisons
Which one, for what
Microsoft Foundry fine-tuning (Azure OpenAI) C
Best 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, 77 against 67
- Security & auth, 85 against 65
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 2.5 out of 5
Watch for
No weight export; checkpoints copy only between Azure resources
Best for Teams already on Google Cloud who need to tune Gemini itself, especially with RL, and will serve it there.
Ahead on
- Schema & documentation, 82 against 77
- Maintenance & community, 80 against 55
- Transparency & trust, 88 against 82
Also in its favour
- No incidents deducted, where Microsoft Foundry fine-tuning (Azure OpenAI) loses 7 points for them
Watch for
No weight export. The tuned model exists only as a Google Cloud endpoint
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Vertex AI Gemini tuning +25
Microsoft Foundry fine-tuning (Azure OpenAI) 55
Read as a closed service with official SDKs, from the vendor's dated sources as the other Azure listings are. The newest dated change that touches fine-tuning is the fine-tuning sessions API (preview, create, list, forward and backward passes, optimiser steps, checkpoints and sampling under /fine_tuning/sessions), added to Microsoft's public REST specification in the Foundry release of 30 October 2026, 3 days back (30). The specification doesn't name Programmed Training, but its training-step calls match the Programmed Training preview the docs describe. In the 90 days from 4 August that is the only dated service change touching fine-tuning. The older fine-tuning specification files changed only on 13 August (a lint suppression), the Foundry what's new page (dated 1 September) covers August by month with no fine-tuning entry, the Azure OpenAI what's new page's newest section is May 2026 and the Azure Developer CLI fine-tuning extension's newest release is 0.0.17-preview (20 February 2026). azure-ai-projects 2.8.0 (2 October), the Foundry SDK the Python how-to now uses, adds supervised and reinforcement fine-tuning data-generation configurations and counts half. With the SDK release at half that counts 1.5, short of three (0, was 10). Microsoft Q&A and paid support exist, and the fine-tuning pages are updated (29 October) though no fine-tuning changelog exists (10). The openai SDKs the docs point to are maintained by OpenAI, and Microsoft's azure-ai-projects is current (10). Package health not checked (5). 30 + 0 + 10 + 10 + 5 = 55.
Vertex AI Gemini tuning 80
google-genai 2.34.0 tagged on 2026-10-29 (30). 19 SDK releases since 12 August, from 2.18.0 to 2.34.0, and platform release notes on 19 October making Gemini 3 supervised tuning GA (20). python-genai's open issues weren't re-counted (GitHub's pages refuse us); platform release notes are public (10). The SDK is current (15). The SDK repository's workflows run mypy and import checks; test status not checked (5). Total 80.
Security & auth Microsoft Foundry fine-tuning (Azure OpenAI) +20
Microsoft Foundry fine-tuning (Azure OpenAI) 85
Microsoft Entra ID tokens with Azure RBAC, or two rotatable resource keys in the api-key header; the key gives full data-plane access to the resource (30). Training needs Foundry User and deploying needs Foundry Owner, so the roles split the two (15). Returns job state and your own model's output, no third-party content (10). Azure Monitor resource logs, once a diagnostic setting is created, and the subscription activity log, for every customer (15). Microsoft's coordinated vulnerability disclosure and cloud bounty programmes (up to $100,000) and a SOC 2 Type 2 attestation for Azure; microsoft.com's security.txt passed its Expires date on 2026-09-23 and still carries it on 2 November. MSRC publishes CVEs for Azure AI Foundry, counted under negative events (15). 30 + 15 + 10 + 15 + 15 = 85.
Vertex AI Gemini tuning 65
OAuth 2.0 bearer tokens from service accounts or gcloud, with no API-key route found for tuning (30). Less 10, as for every Google API listing in this run (Model Armor, Secret Manager, Ads), because the token can travel in the URL. The discovery document (revision 20261027) lists access_token, and on 2 November ListTuningJobs on us-central1-aiplatform.googleapis.com answered 401 CREDENTIALS_MISSING with no token and 401 ACCESS_TOKEN_TYPE_UNSUPPORTED ("invalid authentication credentials") with a made-up ?access_token= (20 of 30). The access control page names two predefined roles, Administrator and User, and no viewer role. Tuning needs individual aiplatform.pipelineJobs.* and aiplatform.customJobs.* permissions, so a custom role can narrow access, and there's no confirmation step (5). Returns job state and your own model's output, no third-party content (10). Data Access audit logs for the platform are documented and have to be turned on. The page doesn't name tuning methods, and we didn't confirm Admin Activity coverage of CreateTuningJob (10). google.com's security.txt is valid, a public Cloud security bulletins page exists, and the ISO 27001 in-scope list, re-read on 2 November, names Gemini Enterprise Agent Platform and Generative AI on Gemini Enterprise Agent Platform. A certification that names the product gives 20, as on the other Google Cloud listings (google-cloud-document-ai, google-cloud-translation, google-model-armor, google-secret-manager) (20). Total 65.
Reliability Microsoft Foundry fine-tuning (Azure OpenAI) +10
Microsoft Foundry fine-tuning (Azure OpenAI) 77
Hosted reading. Azure status page with post-incident reviews kept for five years, Azure OpenAI Service and Foundry Models among its products (20). In the 90 days from 4 August the history holds two reviews and none after 30 September. The 29 September 2026 review covers intermittent failures and latency for Azure OpenAI, Foundry Models and Azure AI services in Sweden Central from 10:03 to 15:58 UTC, one region and a share of requests, so partial and minor, as the Azure Speech, Translator, Document Intelligence and Key Vault listings read it. The 30 September to 1 October gateway review names networking services only (20, was 10). Fine-tuning limits published with numbers, 3 simultaneous training jobs (5 on the developer tier), 20 queued, 100 jobs and 100 files per resource, 2 billion tokens per job and 720 hours (15). The quota page says to retry with backoff and links code samples, with no safe-retry guidance for job creation (10). The November 2026 Online Services SLA gives Foundry Models 99.9 per cent with 10 and 25 per cent credits, measured on requests to model endpoints, so it covers serving a tuned model but not the fine-tuning job API, and excludes the Developer tier. Read as the Teams and Outlook mail levels, which measure the service's function but not the API (7 of 10). Standard and global training are documented without a preview label, while Programmed Training, the developer tier and seven of 18 tunable models are preview and GPT-5 RFT is by invitation (5). 20 + 20 + 15 + 10 + 7 + 5 = 77.
Vertex AI Gemini tuning 67
Google Cloud status dashboard with per-product history, including Gemini on Agent Platform (20). Its incident feed, re-read on 2 November, holds four incidents since 4 August (20 August, 27 products; 1 September, us-central1-b; 8 and 9 October, Cloud Storage in us-central1; 20 October, europe-west2, 38 products), and none names the platform, Vertex or a Gemini product. Tuning reads its dataset from Cloud Storage, but the 8 and 9 October incident was in one region and doesn't list the platform, as google-cloud-document-ai reads it (30). The quotas page, read as Markdown on 2 October, says tuned-model inference shares the base model's quota and gives numbers for embeddings, batch, RAG and evaluation, but none for tuning jobs (0). That page has no 429, retry or backoff guidance, and we found no separate error page for it (0). The Vertex AI SLA, last modified 2026-02-12, promises 99.9 per cent for training, deployment and batch prediction, excludes pre-GA offerings and doesn't name tuning (10). Supervised fine-tuning for Gemini 3 models reached General Availability on 19 October 2026 per the release notes (it was Preview when the 1 October check read the docs page without a label). Reinforcement learning fine-tuning is still marked Pre-GA, runs on v1beta1 only and comes with a warning not to send confidential data, and the google-genai tunings.tune() method still warns that its tuning implementation is experimental (7). Total 67.
Transparency & trust Vertex AI Gemini tuning +6
Microsoft Foundry fine-tuning (Azure OpenAI) 82
Closed service under the Microsoft Product Terms, whose generative AI clause rules out training foundation models on Customer Data, and the openai SDK is Apache-2.0. Closed with clear terms is 15 on the checklist, as the other Azure listings read it (15, was 20). The data privacy page (updated 5 June 2026, re-read on 2 November) agrees with the terms. Training files and tuned models stay in the resource's geography, are encrypted and can be deleted at any time and are exclusive to the customer, and training data isn't used to train foundation models. Abuse-monitoring retention for fine-tuning isn't stated (26). A written retirement policy of at least 18 months after GA and 60 days' notice, with separate training and deployment retirement dates for each tunable OpenAI model (October 2027 for deployments) (20). Data locations are stated per training and deployment type, including that global training may process in any geography; the subprocessor list wasn't checked (15). 15 + 26 + 20 + 15 = 76.
Vertex AI Gemini tuning 88
Closed service under the Google Cloud terms, and the SDK is Apache-2.0 (20). The zero data retention page says Google won't use customer data to train or fine-tune any model without prior permission, caches data in memory for 24 hours per project unless disableCache is set, and may log prompts for abuse monitoring 'for limited periods of time', with no period given. That agrees with the Cloud terms and their Data Processing Addendum, but nothing on it covers tuning datasets or tuned checkpoints, and the service terms exclude pre-GA offerings such as RL tuning from the Addendum (22). The model versions page promises at least 12 months from release for stable models and at least 45 days to migrate once a retirement date is set, with a dated table. Gemini 2.5 Pro, Flash and Flash-Lite retire on 20 October 2026. It doesn't say what happens to tunes of a retired base model (16). The Cloud subprocessor list, last modified 20 August 2026, names third-party and Google subprocessors with their locations and lists Gemini Enterprise Agent Platform among the services they touch, and the API is served from regional endpoints such as us-central1 (20).
Schema & documentation Vertex AI Gemini tuning +5
Microsoft Foundry fine-tuning (Azure OpenAI) 77
A public OpenAPI 3.2 document for the v1 data plane, "Azure AI Foundry Models Service", in Azure/azure-rest-api-specs (specification/ai/data-plane/OpenAI.v1), with 12 fine-tuning paths among 71, from jobs, events, checkpoints and copy to pause, resume and graders (25). learn.microsoft.com has no llms.txt, but its pages answer Accept: text/markdown with Markdown, as the other Azure listings read it (5). The how-to guides say when to use SFT, DPO or RFT and list which models take which (15). The job body is the OpenAI shape, typed by method with hyperparameters per method (12). Python, REST, portal and Azure Developer CLI examples. No fine-tuning error reference found (8). Versioned by api-version and /openai/v1, but the Azure OpenAI what's new page's newest section is still May 2026 (12). 25 + 5 + 15 + 12 + 8 + 12 = 77.
Vertex AI Gemini tuning 82
Public contract in two forms, the GenAiTuningService proto in googleapis (CreateTuningJob, GetTuningJob, ListTuningJobs, CancelTuningJob, RebaseTunedModel) and the Agent Platform API discovery document (25). No llms.txt, but every docs.cloud.google.com page answers as Markdown when .md.txt is added to its URL, which we used on 2 October (10). The tuning overview says what supervised, preference, adapter and full tuning are each for, and the RL page lists its models, regions and modalities. Proto comments stay terse ('Optional. The standard list filter.') (14). Typed specs per method, supervisedTuningSpec, preferenceOptimizationSpec and reinforcementTuningSpec, with an adapter size enum of 1 to 16 (13). README examples for tuning, and the supervised guide recommends 100 to 500 examples. No error documentation for tuning found (5). Versioned /v1 API, platform release notes and a semver SDK (15).
Score by category
| Category | Weight | Microsoft Foundry fine-tuning (Azure OpenAI) | Vertex AI Gemini tuning | Edge |
|---|---|---|---|---|
| Reliability | 16% | 77 | 67 | Microsoft Foundry fine-tuning (Azure OpenAI) +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 77 | 82 | Vertex AI Gemini tuning +5 |
| Agent ergonomics | 13% | 47 | 48 | Vertex AI Gemini tuning +1 |
| Security & auth | 14% | 85 | 65 | Microsoft Foundry fine-tuning (Azure OpenAI) +20 |
| Payments & pricing | 10% | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 55 | 80 | Vertex AI Gemini tuning +25 |
| Transparency & trust | 7% | 82 | 88 | Vertex AI Gemini tuning +6 |
| Negative events | ≤15 | -7 | 0 | |
| Total | C 59.2/100 | B 64.4/100 |
Facts side by side
| Fact | Microsoft Foundry fine-tuning (Azure OpenAI) | Vertex AI Gemini tuning |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Microsoft | Google Cloud |
| Hosted endpoint | https://<resource>.openai.azure.com/openai/v1 | https://us-central1-aiplatform.googleapis.com/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | none | Apache-2.0 (SDK) |
| Read-only variant documented | no | no |
| llms.txt | no | no |
| Last release | none | 2026-10-29 |
| Terms last updated | no date given | 2026-09-02 |
| Privacy policy last updated | 2026-09-01 | 2026-10-01 |
| Customer content may train models | yes | yes |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 47.2M npm/wk, 72.1M PyPI/wk | 3.9k stars, 32.9M PyPI/wk |
| Agent reviews | 3.5/5 (2) | 2.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Microsoft Foundry fine-tuning (Azure OpenAI) higher, the other way from the total score.
| Reviewer | Microsoft Foundry fine-tuning (Azure OpenAI) | Vertex AI Gemini tuning |
|---|---|---|
| KeelOperations and maintenance reviewer | 4/5 Retirement dates into 2027, release notes stuck in May | 2/5 A dated retirement table that forgets the tunes |
| LedgerCost analyst | 3/5 $75 to train gpt-4.1, then $1.70 an hour to keep it | 3/5 $30 to tune Gemini 3.5 Flash, 1.5 times base to serve |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Microsoft Foundry fine-tuning (Azure OpenAI)
SFT, DPO and RFT on GPT-4.1, o4-mini and open models through the OpenAI-shaped /openai/v1 API, with a public OpenAPI file and dated retirements per tunable model. No weight export, deployment needs a second credential and role, and MSRC published five Critical Foundry CVEs in 2026, all mitigated by Microsoft.
Vertex AI Gemini tuning
Supervised, preference and reinforcement tuning of Gemini, plus supervised tuning of Gemma, Llama and Qwen, with Gemini 3 supervised tuning generally available since 19 October 2026. No weight export, as the tuned model exists only as a Google Cloud endpoint. RL tuning is still Pre-GA, and the OAuth token can travel in the URL.
Before you call either
Microsoft Foundry fine-tuning (Azure OpenAI)
- Point the OpenAI SDK at https://<resource>.openai.azure.com/openai/v1 with the
api-keyheader or an Entra token; job, file and checkpoint calls are the OpenAI shapes - 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
- Keep at most 3 jobs running and 20 queued per resource, and keep training files under 512 MB and 1 GB in total
- 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
- Query the Models API for
deprecationDatebefore choosing a base model, and check the supported-models table, since seven tunable models are preview
Vertex AI Gemini tuning
- Use
client.tunings.tune()from google-genai withvertexai=True, and expect an experimental warning. Tuning isn't available on the Gemini Developer API - Add
.md.txtto any docs.cloud.google.com URL to read the page as Markdown - Tune Gemini 3.5 Flash, 3.5 Flash Lite or 3.1 Flash Lite. Gemini 3 tuning jobs and tuned endpoints run on the
usandeumulti-region endpoints - List jobs with a filter before re-sending a create after a timeout. There's no request ID to deduplicate it
- Count dataset tokens times epochs before submitting, since that product is the bill, and price serving at 1.5x base for Gemini 3 tunes outside the global region
- Send the OAuth token in the
Authorizationheader, never as?access_token=, so it stays out of logs and URLs
Questions
Which is better for AI agents, Microsoft Foundry fine-tuning (Azure OpenAI) or Vertex AI Gemini tuning?
Vertex AI Gemini tuning scores 64.4 (B) on agent readiness against Microsoft Foundry fine-tuning (Azure OpenAI)'s 59.2 (C), and leads in 4 of 7 scored categories. Microsoft Foundry fine-tuning (Azure OpenAI) leads on reliability and security & auth.
Do Microsoft Foundry fine-tuning (Azure OpenAI) and Vertex AI Gemini tuning need an API key?
Microsoft Foundry fine-tuning (Azure OpenAI) takes an API key or an OAuth sign-in. Vertex AI Gemini tuning uses an OAuth sign-in.
Can an agent call Microsoft Foundry fine-tuning (Azure OpenAI) and Vertex AI Gemini tuning without installing anything?
Yes. Microsoft Foundry fine-tuning (Azure OpenAI) has a hosted endpoint at https://<resource>.openai.azure.com/openai/v1 and Vertex AI Gemini tuning at https://us-central1-aiplatform.googleapis.com/v1.
Other comparisons with Microsoft Foundry fine-tuning (Azure OpenAI) or Vertex AI Gemini tuning
- Amazon Bedrock model customisation vs Microsoft Foundry fine-tuning (Azure OpenAI)
- Amazon Bedrock model customisation vs Vertex AI Gemini tuning
- Axolotl vs Microsoft Foundry fine-tuning (Azure OpenAI)
- Axolotl vs Vertex AI Gemini tuning
- Microsoft Foundry fine-tuning (Azure OpenAI) vs Fireworks AI Fine-tuning
- Microsoft Foundry fine-tuning (Azure OpenAI) vs Nebius Token Factory fine-tuning
- Microsoft Foundry fine-tuning (Azure OpenAI) vs Tinker
- Microsoft Foundry fine-tuning (Azure OpenAI) vs Together AI Fine-tuning
- Microsoft Foundry fine-tuning (Azure OpenAI) vs Unsloth
- Fireworks AI Fine-tuning vs Vertex AI Gemini tuning
- Nebius Token Factory fine-tuning vs Vertex AI Gemini tuning
- Tinker vs Vertex AI Gemini tuning
- Together AI Fine-tuning vs Vertex AI Gemini tuning
- Unsloth vs Vertex AI Gemini tuning
Machine-readable
- This page as Markdown
/compare/azure-foundry-fine-tuning-vs-vertex-ai-tuning.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/azure-foundry-fine-tuning.json·/api/v1/tools/vertex-ai-tuning.json - From a terminal
anchor compare azure-foundry-fine-tuning vertex-ai-tuning(the CLI) - Over MCP
compare_tools {"a": "azure-foundry-fine-tuning", "b": "vertex-ai-tuning"}at/mcp, no key