Fix 404 errors in Azure OpenAI Graders by reverting to stable API version#45226
Draft
Fix 404 errors in Azure OpenAI Graders by reverting to stable API version#45226
Conversation
Co-authored-by: w-javed <7674577+w-javed@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix 404 Not Found error on evaluate() with Azure OpenAI Graders
Fix 404 errors in Azure OpenAI Graders by reverting to stable API version
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Azure OpenAI Graders fail with
404 Not Foundwhen callingevaluate()due to broken API specifications in2025-04-01-preview(see Azure/azure-rest-api-specs#33724). The spec mixes OpenAPI 3.0/3.1 standards and has orphaned references, causingevals.createendpoint failures.Changes
_constants.py: RevertDEFAULT_AOAI_API_VERSIONfrom2025-04-01-previewto2024-12-01-previewCHANGELOG.md: Document fix in 1.15.1 (Unreleased)Context
The grader forces API version internally via
aoai_grader.py:116, making this transparent to users. All existing tests and samples already validate against2024-12-01-preview. User-providedapi_versionin model configs (used for chat completions) remains unaffected.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
learn.microsoft.com/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)scanning-api.github.com/home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js(dns block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
This section details on the original issue you should resolve
<issue_title>[BUG] 404 Not Found on evaluate() with Azure OpenAI Graders - Possible Service/SDK Incompatibility</issue_title>
<issue_description>
Description
I am encountering a persistent 404 Not Found error when attempting to run the Azure OpenAI Graders workflow, both via the Python SDK and the Azure AI Foundry (Portal) GUI. This occurs even when using the official sample dataset and following the lab documentation.
1. Environment & Setup
Notebook Source:
scenarios/evaluate/Azure_OpenAI_Graders/Azure_OpenAI_Graders.ipynbPython Version: 3.10 (Miniconda)
Libraries:
azure-ai-evaluation,openai(latest)Region:
canadaeast<b dat...
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.