Skip to content
Everruns Everruns

Microsoft MAI

Everruns runs agents on Microsoft MAI models (for example MAI-Code-1-Flash), which are served via Azure AI Foundry behind an OpenAI-compatible Chat Completions API. The MAI provider exists as its own driver mainly because of its authentication options.

What you get

Section titled “What you get”
  • OpenAI-compatible Chat Completions streaming through Azure AI Foundry.
  • Two authentication schemes — an Azure AI Foundry API key, or Microsoft Entra ID (OAuth) service-principal credentials with bearer tokens minted and refreshed automatically.
  • Model discovery against Foundry’s /models endpoint where available, with capabilities supplied by Everruns’ built-in Microsoft model profiles.

Configure in Everruns

Section titled “Configure in Everruns”
  1. Go to Settings → Providers and click Add provider.
  2. Choose Microsoft MAI.
  3. Set the base URL to your Azure AI Foundry resource (e.g. https://<resource>.services.ai.azure.com).
  4. Provide credentials using one of:
    • API key — your Azure AI Foundry resource key.
    • Entra ID (OAuth) — a client-credentials service principal (tenant_id, client_id, client_secret).
  5. Save.

Authentication is fail-closed: a stored credential is always required, and OAuth tokens are refreshed transparently for both chat execution and model sync.

Models

Section titled “Models”

Foundry’s /models listing is bare (ids only), so capabilities come from Everruns’ built-in Microsoft MAI model profiles, matched by id. Because Azure deployment names are operator-chosen, a deployment whose name does not match a known profile falls back to a minimal profile.

Section titled “Links”