![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(131.20000000000002, 20%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBB%3C/text%3E%3C/svg%3E)
Azure OpenAI Service
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 51%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKV%3C/text%3E%3C/svg%3E)
Hello Barry Briggs,
Welcome to Microsoft Q&A .Thank you for reaching out.
The observed issue is caused by version misalignment between a preview agent SDK and stable OpenAI SDKs. Aligning package versions or isolating preview functionality resolves the conflict in most cases. Preview SDKs require careful dependency management until general availability.
The package Azure.AI.Agents.Persistent v1.2.0‑beta.9 is a preview (beta) SDK that is part of the newer Azure AI Agents platform. Preview SDKs are validated against a specific set of dependency versions and do not always stay aligned with the latest stable releases of other SDKs.
At present, Azure.AI.Agents.Persistent v1.2.0‑beta.9 targets an earlier OpenAI SDK dependency, while many existing RAG applications use Azure.AI.OpenAI 2.2 or later. When both are referenced in the same application, the dependency versions do not align, which can result in build or runtime conflicts. This can appear as the application being blocked.
Please consider the following workarounds to resolve the issue
1.Align package versions
Please use matching SDK versions across the application to avoid dependency conflicts.
- Downgrade Azure.AI.OpenAI to the version expected by the Agents Persistent beta.
- Alternatively, use preview builds across the stack where dependencies are aligned.
2.Isolating the agent functionality
If existing RAG functionality depends on newer OpenAI SDK versions, then
- Consider separating agent‑based logic into a different project or service.
- Keep stable RAG workflows unchanged.
- Use Agents Persistent only where preview SDK alignment is possible.
References:
- How to migrate from Azure.AI.OpenAI 1.0 Beta to 2.0 (classic) - Microsoft Foundry (classic) | Microsoft Learn
- Azure AI Projects OpenAI client library for .NET - Azure for .NET Developers | Microsoft Learn
- What is Microsoft Foundry Agent Service? - Microsoft Foundry | Microsoft Learn
- Azure OpenAI in Microsoft Foundry Model Retirements - Microsoft Foundry | Microsoft Learn
Thank you!
Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.