Posts tagged with "Migration"

Azure OpenAI On Your Data retired on 14 October 2026, and Microsoft says the replacement paths are not feature-equivalent: a Foundry IQ knowledge base on Azure AI Search, called directly or through Foundry Agent Service. The guide covers how to find affected data_sources calls, the GA-versus-preview API decision, the parameter mapping, the stricter per-user authorization model, the two-bill cost math, and Sweden Central capacity.

Moving Azure infrastructure from Terraform to Bicep is less about converting HCL files and more about replacing a state-file workflow with a deployment-based one. This field guide covers when migration pays off, inventorying tfstate, incremental coexistence patterns, the decompile tooling that exists, deployment stacks as the lifecycle answer, and the what-if validation and rollback discipline that keeps the cutover safe.

The Azure OpenAI Assistants API reached its retirement date on 26 August 2026, and the classic Foundry Agent Service it underpins retires 31 March 2027. A step-by-step migration guide to the new Foundry Agent Service on the Responses API: threads become conversations, runs become responses, assistants become versioned agents, and Microsoft's migration tool rewrites code but not stored state.

TypeScript 7.0 is a native Go port of the compiler, and Microsoft measured type-checking the VS Code codebase falling from 125.7 seconds to 10.6 seconds at default settings. A team still on 5.8 is two majors behind, so this is the staged route through 6.0, the changed defaults and removals that actually break builds, and who should wait for the 7.1 API.

Microsoft renamed Azure Cognitive Search to Azure AI Search in late 2023 and added substantial vector, semantic, and agentic-retrieval capabilities. Manufacturing teams running legacy Cognitive Search deployments need a structured migration plan — not a like-for-like upgrade, but a targeted modernisation of the features that matter most.