BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Hugin//Provider deadline board//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALNAME:Hugin — Microsoft deadlines X-WR-CALDESC:Published end dates from Microsoft tracked by Hugin. This subs cription contains only Microsoft dates\; it does not imply any unpublished or inferred term. X-PUBLISHED-TTL:PT12H REFRESH-INTERVAL;VALUE=DURATION:PT12H BEGIN:VEVENT UID:azure-openai-sora-2-retirement@hugin.studio DTSTAMP:20261106T183351Z SEQUENCE:306 DTSTART;VALUE=DATE:20261015 DTEND;VALUE=DATE:20261016 SUMMARY:⚑ Microsoft: Azure OpenAI retires sora-2 (version 2025-12-08) — three weeks after OpenAI shut down its own Sora 2 API DESCRIPTION:Azure OpenAI retires sora-2 (version 2025-12-08) — three week s after OpenAI shut down its own Sora 2 API\n\nNOTHING TO MOVE TO: Microso ft's retirement schedule shows '—' in the Replacement column for sora-2 version 2025-12-08\, and its lifecycle page says that when no replacement exists 'customers get 30 days notice before the model retires and inferenc e returns 410 Gone.' OpenAI names no replacement on its side either.\n\nBE FORE THIS DATE: Azure customers with a sora-2 (2025-12-08) deployment: dec ide what replaces it before October 15. There is no named replacement on A zure\, and OpenAI's own Sora 2 API closed on September 24\, so this is a v endor decision\, not a redeploy.\n\nCaveat: A Preview-stage 'not sooner th an' date\, not a committed shutdown. The schedule lists this sora-2 versio n as Preview\, and Microsoft's lifecycle page says Preview models 'launch with a "not sooner than" retirement date (typically 90 days out)\, but are sometimes extended beyond that initial window\, until a suitable replacem ent preview or GA model version is available.' The same page answers 'Can I get an exception to extend a model's retirement date?' with 'No.' — th at is about a customer asking\, not about Microsoft moving its own Preview date. Microsoft's schedule (page dated September 21\, updated September 2 3)\, not an observation: this desk cannot test Azure deployments. The same table lists an earlier sora-2 version\, 2025-10-06\, with a July 15 retir ement date and this version as its replacement.\n\nAuthoritative document (Microsoft Foundry model retirement schedule): https://learn.microsoft.com /en-us/azure/foundry/openai/concepts/model-retirement-schedule\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=Microsoft\nOnly dates a provider has published about its own product appear here. URL:https://hugin.studio/deadlines?provider=Microsoft CATEGORIES:Microsoft\,retirement TRANSP:TRANSPARENT STATUS:CONFIRMED END:VEVENT BEGIN:VEVENT UID:microsoft-foundry-kimi-k2-7-code-retirement@hugin.studio DTSTAMP:20261106T183351Z SEQUENCE:273 DTSTART;VALUE=DATE:20261003 DTEND;VALUE=DATE:20261004 SUMMARY:⚑ Microsoft: Moonshot AI's Kimi-K2.7-Code\, a Preview model Azure sells\, retires from Microsoft Foundry — the day after GitHub Copilot d rops the same model DESCRIPTION:Moonshot AI's Kimi-K2.7-Code\, a Preview model Azure sells\, re tires from Microsoft Foundry — the day after GitHub Copilot drops the sa me model\n\nNOTHING TO MOVE TO: Microsoft's retirement schedule shows '— ' in the Replacement column for Kimi-K2.7-Code. GitHub's Copilot notice su ggests Kimi K3 for the same model on October 2\, but that is GitHub's reco mmendation for its own tool\, not Microsoft's for Foundry.\n\nBEFORE THIS DATE: Foundry customers with a Kimi-K2.7-Code deployment: choose and test a replacement before October 3\; the schedule names none.\n\nCaveat: A Pre view-stage 'not sooner than' date that Microsoft's lifecycle page says is 'sometimes extended beyond that initial window'. The Copilot removal on Oc tober 2 is a separate row\; Moonshot AI's own API is not covered here.\n\n Authoritative document (Microsoft Foundry model retirement schedule): http s://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retireme nt-schedule\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=M icrosoft\nOnly dates a provider has published about its own product appear here. URL:https://hugin.studio/deadlines?provider=Microsoft CATEGORIES:Microsoft\,retirement TRANSP:TRANSPARENT STATUS:CONFIRMED END:VEVENT BEGIN:VEVENT UID:microsoft-foundry-mai-image-2-5-retirement@hugin.studio DTSTAMP:20261106T183351Z SEQUENCE:271 DTSTART;VALUE=DATE:20261001 DTEND;VALUE=DATE:20261002 SUMMARY:⚑ Microsoft: Microsoft retires its own image models MAI-Image-2.5 \, MAI-Image-2.5-Flash and MAI-Image-2.5-Pro from Foundry DESCRIPTION:Microsoft retires its own image models MAI-Image-2.5\, MAI-Imag e-2.5-Flash and MAI-Image-2.5-Pro from Foundry\n\nNOTHING TO MOVE TO: The retirement schedule shows '—' in the Replacement column for all three\, although the same table lists MAI-Image-2.5 and MAI-Image-2.5-Flash as the replacements for MAI-Image-2 and MAI-Image-2e\, retired August 15. Micros oft's MAI image how-to page lists the Preview models MAI-Image-2.6 and MAI -Image-2.6-Flash without calling them replacements.\n\nBEFORE THIS DATE: F oundry customers on an MAI-Image-2.5 deployment: pick and test a replaceme nt before October 1. None is named\, and Microsoft's lifecycle page says a model retired with no replacement answers 410 Gone.\n\nCaveat: A Preview- stage 'not sooner than' date: all three are Preview models\, and Microsoft 's lifecycle page says Preview models 'launch with a "not sooner than" ret irement date (typically 90 days out)\, but are sometimes extended beyond t hat initial window'. This desk cannot test Foundry deployments or see the 30-day notice the policy promises when no replacement exists.\n\nAuthorita tive document (Microsoft Foundry model retirement schedule): https://learn .microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedu le\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=Microsoft\ nOnly dates a provider has published about its own product appear here. URL:https://hugin.studio/deadlines?provider=Microsoft CATEGORIES:Microsoft\,retirement TRANSP:TRANSPARENT STATUS:CONFIRMED END:VEVENT END:VCALENDAR