v1.18.24 shipped one quietly significant change for enterprise users: Azure providers can sign in with Microsoft Entra ID through the Azure CLI, instead of requiring an API key.
What changed
Previously, using Azure-hosted models meant provisioning and pasting an API key. Now the Azure provider in OpenCode authenticates via the Azure CLI’s signed-in identity — the same credential surface your infrastructure tooling already uses.
The next day’s v1.18.25 followed up with a fix: Azure CLI sign-in now works without requiring Bun, so the flow isn’t coupled to your runtime.
Who benefits
- Enterprise teams where API keys are rotated centrally and pasting keys into tools is a policy violation
- Cloud workstation setups where the Azure CLI is already authenticated as part of the image
- Anyone who has hit the Azure GPT-5.5+ reasoning failures fixed in v1.18.12 and wants a cleaner auth path while retesting
How to use it
Update to v1.18.25 or later, make sure az is signed in (az login), then connect the Azure provider — authentication goes through your Azure CLI identity instead of an API key. Full provider setup lives in the providers documentation.
The authoritative change list is in the v1.18.24 and v1.18.25 release notes.