End-to-end toolkit for migrating Azure OpenAI / Azure AI Foundry models — from inventory through rollout. Discover what you have, plan the move, change the code, prove it works, and roll out safely.
Topics: azure-openai · azure-ai-foundry · model-migration · llm-evaluation · gpt-5 · mcp · copilot-skills
⚠️ Staging repo. This is a consolidation of multiple existing migration assets being prepared for promotion toAzure-Samples. Attribution and source-asset details live inCREDITS.md; the rollout plan lives indocs/internal/.
You own (or build for) an application running on Azure OpenAI or an Azure AI Foundry model and you need to move to a newer model — for cost, capability, retirement pressure, or all three. Start at 01 · Discover and walk the journey end to end.
You're a CSA / CSAM / GBB running a migration motion with a customer. Use the same journey, but you have a few extras:
- The inventory + retirement urgency pattern in 01 · Discover plus the availability tracker in 02 · Plan cover most pre-engagement diligence.
- The opinionated migration packs (e.g., 4o → 5.1, Chat Completions → Responses API) in 03 · Migrate code work as drop-in customer assets.
- The customer pitch deck in presentation/ is ready to brand and send.
- For internal-only tooling (PTU sizing, MSX/CRM context, blast-radius scoring), use the private internal companion repo. This public repo is its open counterpart — and what you should hand to the customer.
| Step | Section | What it answers |
|---|---|---|
| 1 | 01 · Discover | What models do I have deployed, where, how heavily are they used, and which are retiring? |
| 2 | 02 · Plan | Given my inventory, which migrations matter most, what do I migrate to, and is the target model actually available where I need it? |
| 3 | 03 · Migrate code | What exactly changes in my code — parameters, API surface, SDK — and what can be automated? |
| 4 | 04 · Evaluate | Does the migrated app behave at least as well as the original on my real workloads? |
| 5 | 05 · Roll out | How do I cut over safely with canary, observability, and a tested rollback? |
Supporting:
- tools/ — repo-wide tooling (web UI for side-by-side comparison).
- presentation/ — stakeholder-ready collateral.
- docs/internal/ — planning record (consolidation plan, source asset catalog).
See CONTRIBUTING.md. Attribution for upstream content is tracked in CREDITS.md.
This project has adopted the Microsoft Open Source Code of Conduct. See CODE_OF_CONDUCT.md.
Report security issues via the process in SECURITY.md — not via public GitHub Issues.
This is a sample / reference implementation, not covered by Microsoft Support. See SUPPORT.md.
MIT.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.