{
  "slug": "azure-foundry-models-cohere-embed-v3-multilingual-1-retirement",
  "title": "Microsoft Foundry Models: Cohere-embed-v3-multilingual version 1 retirement",
  "summary": "Retirement date for Cohere-embed-v3-multilingual version 1 in Microsoft's retirement schedule for Foundry Models: 15 Feb 2027. Microsoft's lifecycle policy for Foundry Models says that a retired model is removed from service and that all inference requests return 410 Gone.",
  "cloud": "azure",
  "service": "Microsoft Foundry Models",
  "service_slug": "foundry-models",
  "category": "feature",
  "type": "retirement",
  "announced_date": null,
  "effective_date": "2027-02-15",
  "effective_precision": "day",
  "impact": "Microsoft lists Cohere-embed-v3-multilingual version 1 under \"Cohere\" in the section \"Foundry Models from partners and community\" in its retirement schedule for Foundry Models. The date in the \"Retirement date\" cell of this row is 15 Feb 2027.\n\n- Lifecycle cell of this row in the schedule: GA.\n- Microsoft's lifecycle policy for Foundry Models describes the Retired stage in these words: \"Removed from service. All inference requests return 410 Gone.\"\n- The policy says that for Global Standard, Data Zone Standard, and Standard deployment types, Microsoft manages automatic upgrades when a model version is retired. The policy also says that provisioned deployments are not upgraded automatically. It says both in general, not about Cohere-embed-v3-multilingual version 1 by name.\n- The schedule says its Replacement column identifies Microsoft's recommended replacement and, where supported, the target for automatic upgrades at retirement.\n- Replacement cell of this row in the schedule: Cohere-embed-v5-fast, Cohere-embed-v5-pro.\n- Under the table of this row, the schedule adds: \"Cohere-embed-v3-english and Cohere-embed-v3-multilingual are deprecated on November 15, 2026.\"",
  "migration_path": "1. Microsoft says you do not need to wait for a replacement to be listed before evaluating or manually migrating to another compatible model.\n2. Microsoft says to evaluate available models using your application and data, comparing quality, latency, and cost.\n3. Microsoft's lifecycle policy says to confirm API compatibility, feature support, deployment-type and regional availability, capacity, and quota before you migrate.\n4. The policy says: \"Provisioned customers must manually migrate to the replacement model.\"",
  "replacement": "Cohere-embed-v5-fast, Cohere-embed-v5-pro",
  "affected_versions": [
    "1"
  ],
  "source_url": "https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule",
  "extra_source_urls": [
    "https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirements"
  ],
  "vendor_ref": "Cohere-embed-v3-multilingual@1",
  "last_checked_at": "2026-11-20T04:36:15.258Z",
  "created_at": "2026-11-15T15:10:27.919Z",
  "updated_at": "2026-11-15T15:10:27.919Z",
  "url": "https://eolwatch.dev/items/azure-foundry-models-cohere-embed-v3-multilingual-1-retirement",
  "short_url": "https://eolwatch.dev/i/j2",
  "markdown_url": "https://eolwatch.dev/items/azure-foundry-models-cohere-embed-v3-multilingual-1-retirement.md",
  "json_url": "https://eolwatch.dev/items/azure-foundry-models-cohere-embed-v3-multilingual-1-retirement.json",
  "estate_check": null,
  "source_note": null
}
