MS Foundry Developer Migration Checklist

Microsoft Foundry recently implemented a variety of changes across various areas. To assist with these changes, a Developer Migration Checklist is provided below to help maneuver these changes.

 

1. Migrate to the Unified SDK 2.0

[] Replace all uses of the old azure-ai-agents package with azure-ai-projects 2.0.

[] Update code to use AIProjectClient for model inference, agents, evaluations, memory, and tracing.

[] Remove legacy preview flags and update any custom tool or MCP integrations.

[] Validate that all tool schemas and agent configurations work under the new client.

 

2. Move Agents to the Foundry Agent Service (GA)

[] Migrate existing agent deployments to the new Agent Service runtime.

[] Update agent code to use the OpenAI Responses compatible interface.

[] Reconfigure private networking, Entra RBAC, and tracing endpoints.

[] Test agent behavior in the updated Agent Playground and tracing tools.

 

3. Upgrade to the GPT 5.4 Model Family

[] Replace older GPT models with:

  [] GPT 5.4 for general workloads

  [] GPT 5.4 Pro for advanced reasoning

  [] GPT 5.4 Mini for routing, extraction, and classification

[] Review token budgets and latency expectations.

[] Update prompt templates that relied on older model behavior.

 

4. Adopt Evaluations and Continuous Monitoring

[] Replace custom evaluation scripts with built-in evaluators for coherence, relevance, groundedness, retrieval quality, and safety.

[] Enable continuous monitoring to sample production traffic.

[] Connect evaluation results to Azure Monitor dashboards.

[] Set up alerts for quality drift, safety issues, and retrieval degradation.

 

5. Update Safety and Guardrails

[] Enable the Task Adherence guardrail for all production agents.

[] Add tool call guardrails to prevent unsafe or unintended tool actions.

[] Integrate optional security layers such as Palo Alto Prisma AIRS and Zenity.

[] Review and update any custom safety logic.

 

6. Update Networking and Infrastructure

[] Update managed VNet configurations because outbound internet access is no longer enabled by default.

[] Validate private networking for agents, MCP servers, Azure AI Search, and Fabric data agents.

[] Update firewall rules and service endpoints as needed.

 

7. Prepare for Deprecations

[] Begin migration from PromptFlow to Microsoft Framework Workflows before January 2027.

[] Move Azure ML data connections to Fabric OneLake.

[] Audit pipelines that rely on deprecated endpoints or preview features.

 

8. Optional Enhancements

[] Evaluate Priority Processing for latency sensitive workloads.

[] Explore Voice Live for speech to speech agent interactions.

[] Test Phi 4 Reasoning Vision 15B for multimodal workflows.

[] Consider using Fireworks AI or NVIDIA Nemotron models if open model inference is needed.

 

You can view the full article at https://devblogs.microsoft.com/foundry/whats-new-in-microsoft-foundry-mar-2026/

Uploaded Image

Comments

Popular posts from this blog

.NET MAUI with Blazor vs. XAML

Jun '25 Tech Events