Update Azure Model Router Evaluation - #179
Closed
codebyshibsankar wants to merge 1 commit into
Closed
codebyshibsankar wants to merge 1 commit into
codebyshibsankar wants to merge 1 commit into
Conversation
updated prediction files Updated Azure Model Router evaluation submission
codebyshibsankar
force-pushed
the
azure-model-router-aug26-submission
branch
from
August 12, 2026 19:38
42d9ccb to
ed3da0b
Compare
Author
|
/evaluate |
Router Evaluation ResultsRouter: RouterArena Metrics
Evaluation completed by RouterArena automated workflow |
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 Model Router (2025-08-12) — submission
Affiliation: Microsoft — Azure Model Router
Azure's built-in model router, available through the Azure AI Foundry platform. It automatically routes prompts across a pool of 27 models spanning 5 providers, all accessible through a single Azure OpenAI endpoint.
How it routes
As a trained language model, the router analyzes prompts in real time based on complexity, reasoning, task type, and other attributes. It does not store prompts and routes only to eligible models based on access and deployment types, honoring data-zone boundaries.
Supported Models
Routing Mode
With the latest version, if you choose a custom deployment, you can select a routing mode to optimize for quality or cost while maintaining a baseline level of performance. Setting a routing mode is optional; if you do not set one, your deployment defaults to Balanced mode.
Available routing modes:
Model Subset
You can specify which underlying models are included in routing decisions. This gives more control over cost, compliance, and performance characteristics.
Automatic Failover
Model router includes built-in automatic failover. When using the default deployment to route to all supported models, it transparently redirects requests to the next-most-appropriate model so transient issues with any single model do not disrupt the application. Failover is enabled by default.
Prompt Caching
Model router supports prompt caching because requests are processed by the underlying models that support it. When the router delegates a request to a model that supports prompt caching, cached tokens are used automatically with no extra configuration.
Files Changed
azure-model-router.jsonazure-model-router-may-26.json— 8,400 regular predictionsazure-model-router-robustness-may-26.json— 420 robustness routesuniversal_model_names.py— additive updates for newer model aliases and mappingsmodel_cost.json— additive pricing entries for newer modelsThis evaluation was done in cost mode with the full 27-model routing set.