feat(azure-open-ai): update model YAMLs [bot]

[models-bot]

Auto-generated by poc-agent for provider azure-open-ai.

---

Note

Low Risk
Single-field metadata change in a provider model catalog with no runtime or API logic touched.

Overview
Sets isDeprecated: true on the Azure Open AI model definition for gpt-4o-mini-2024-07-18, aligning its catalog metadata with other deprecated entries in this provider. Pricing, limits, features, and status: active are unchanged in this diff; only the deprecation flag is added.

^{Reviewed by Cursor Bugbot for commit b3ac918. Bugbot is set up for automated code reviews on this repo. Configure here.}

[github-actions]

/test-models

[harshiv-26]

Gateway test results

• Total: 0
• Passed: 0
• Failed: 0
• Validation failed: 0
• Errored: 0
• Skipped: 0
• Success rate: 0.0%

Provider	Model	Scenarios

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b3ac918. Configure here.}

[cursor]

Contradictory deprecation metadata

Medium Severity

isDeprecated: true was added while status remains active and retirementDate is still in the future (2026-10-01). That contradicts lifecycle encoding elsewhere: deprecated models set both isDeprecated and status: deprecated, and peer models with the same retirement date (gpt-4o-mini, gpt-4o, gpt-4o-2024-11-20) stay active without isDeprecated. Consumers that filter on isDeprecated will wrongly exclude a still-active model.

 

^{Reviewed by Cursor Bugbot for commit b3ac918. Configure here.}