Provider key onboarding probe

Azure OpenAI | key onboarding readiness

Azure OpenAI key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 0 covered models, global route, sample models Azure OpenAI, then verifies with read-only probes.

Provider

Azure OpenAI

global route

Model coverage

0

Azure OpenAI

Probe dimension

key onboarding readiness

onboarding-readiness

Onboarding signal

limited model coverage, confirm provider identity first

azure-openai

Read-only probes

1

current_key

Sample metrics

10

key_valid / requests_total / runtime_model / runtime_model_allowed

Ten capabilities

6

operational actions / model permission matrix / limit matrix

Provider onboarding summary

Provider

Azure OpenAI

Probe dimension

onboarding-readiness

Model coverage

0

Read-only check. Detection data burns after 5 minutes.

Why this probe matters

Azure OpenAI key onboarding readiness decides whether a key can move from identification into inventory, pricing, routing, and launch. TestKey starts with 0 covered models, global route, sample models Azure OpenAI, then verifies with read-only probes.

Provider: Azure OpenAI
Model coverage: 0
Probe dimension: key onboarding readiness

How to prove it

Read-only check. Detection data burns after 5 minutes.

Identify the real provider first, then verify key onboarding readiness; do not treat OpenAI-compatible as real OpenAI by default.
Use 0 covered models as candidates, then read /models, balance, error bodies, and limit headers.
limited model coverage, confirm provider identity first

Next action

Azure OpenAI key onboarding readiness should become an action: add provider config, fill pricing, import inventory, set route, add monitoring, or send to human review.

Read-only check. Detection data burns after 5 minutes.
Onboarding signal: limited model coverage, confirm provider identity first
Model coverage: Azure OpenAI

Ten key capability anchors

Azure OpenAI has 1 read-only account probes configured, currently supporting operational actions / model permission matrix / limit matrix / continuous monitoring / key identity / capability matrix. These anchors feed the real TestKey detection path, not just admin display.

Read-only probes: current_key, used to prove provider identity, models, balance, or subscription state.
Sampleable metrics: key_valid / requests_total / runtime_model / runtime_model_allowed / requests_limit / bucket_start / bucket_end / token_type / ....
Ten-capability anchors: operational actions / model permission matrix / limit matrix / continuous monitoring / key identity.

Open key check

Read-only check. Detection data burns after 5 minutes.