Automatic approval review fails on Microsoft Foundry/Azure OpenAI because codex-auto-review is not deployable

What version of the Codex App are you using (From "About Codex" dialog)?

Version 26.506.31421 (2620)

What subscription do you have?

API key via Microsoft Foundry / Azure OpenAI-compatible endpoint.

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

Automatic approval review fails when Codex is configured to use a Microsoft Foundry / Azure OpenAI endpoint, then the action is rejected as high risk.

Observed local error, with the Azure resource name redacted:

Automatic approval review failed: unexpected status 404 Not Found: The API deployment for this resource does not exist. If you created the deployment within the last 5 minutes, please wait a moment and try again., url: https://[redacted-resource].openai.azure.com/openai/v1/responses

This looks like the Foundry/Azure equivalent of #19420. In that issue, codex-auto-review was missing for OpenAI API key users and a maintainer commented that it was fixed for API key users. However, the same automatic approval reviewer path still appears to fail for Microsoft Foundry / Azure OpenAI users.

The current Codex model catalog includes the hidden model:

{
  "slug": "codex-auto-review",
  "display_name": "Codex Auto Review",
  "description": "Automatic approval review model for Codex.",
  "visibility": "hide",
  "supported_in_api": true
}

For Azure/Foundry Responses API calls, the model parameter must refer to a deployed model/deployment name. Since codex-auto-review is not available/deployable in my Microsoft Foundry model catalog/resource, the automatic reviewer request appears to be sent to Azure with a model/deployment that does not exist. Regular Codex calls to explicitly deployed Azure/Foundry models work; the failure appears specific to the separate automatic approval review model.

What steps can reproduce the bug?

1. Configure Codex App to use an API key with a Microsoft Foundry / Azure OpenAI-compatible endpoint, for example an endpoint under https://<resource>.openai.azure.com/openai/v1/.
2. Use a deployed model for regular Codex requests.
3. Enable automatic approval review / the guardian automatic reviewer.
4. Trigger an action that requires automatic approval review, such as an apply_patch action that Codex classifies as high risk.
5. Observe that the automatic approval review request fails with Azure's "API deployment for this resource does not exist" 404, and Codex rejects the action.

What is the expected behavior?

Automatic approval review should either work for Microsoft Foundry / Azure OpenAI users or degrade to manual approval without treating the reviewer failure as an automatic high-risk denial.

Possible fixes:

• Route automatic approval review through the configured/deployed model or a configurable reviewer model when using Azure/Foundry.
• Expose a config override for the automatic approval review model.
• Mark codex-auto-review as unsupported for Azure/Foundry/custom OpenAI-compatible providers and fall back to normal manual approval.
• Document that automatic approval review requires a first-party OpenAI API key/model path if that is the intended limitation.

Additional information

Related issue: #19420 (codex-auto-review doesn't exist in the API), closed as fixed for OpenAI API key users on 2026-04-25.

Microsoft Foundry Responses API docs require a deployed Azure OpenAI model, and their examples say to replace the model value with the model deployment name. The Foundry model routing docs also state that the model parameter is the deployment name in most cases. That makes the current codex-auto-review routing incompatible unless Microsoft Foundry exposes/deploys that model slug or Codex uses a different reviewer model path for Azure/Foundry.