Azure OpenAI v1 API support for External Model Serving / Mosaic AI Gateway?

mbecker
New Contributor

Hi,

I’m setting up an external model serving endpoint for Azure OpenAI through Databricks Model Serving / Mosaic AI Gateway, and I’m trying to understand whether the newer (more than a year old at this point) Azure OpenAI v1 API is currently supported.

In the built-in OpenAI / Azure OpenAI provider configuration, Azure OpenAI mode still asks for:

  • OpenAI API base
  • OpenAI deployment name
  • OpenAI API version

That seems aligned with the older Azure OpenAI pattern, where requests use a dated API version such as 2025-04-01-preview.

However, Microsoft’s newer Azure OpenAI v1 API uses a base URL like:

https://<resource>.openai.azure.com/openai/v1/

and no longer requires a dated api-version parameter for the v1 API.

A few questions:

  1. Does the built-in Databricks Azure OpenAI external model provider support v1 as the OpenAI API version, or is that field expected to be a dated Azure API version only?
  2. If v1 is supported, what should the fields look like?
    • Should OpenAI API base be the resource root, like https://<resource>.openai.azure.com
    • or the v1 base, like https://<resource>.openai.azure.com/openai/v1?
  3. If the built-in Azure OpenAI provider does not support the new v1 URL shape, is the recommended workaround to use Custom Provider with a full endpoint URL such as:

https://<resource>.openai.azure.com/openai/v1/chat/completions

and API key authentication using the api-key header?

  1. Is there a roadmap to add first-class support for Azure OpenAI v1 in External Model Serving / Mosaic AI Gateway?
  2. Related: does External Model Serving currently support only Chat Completions-style endpoints, or is /openai/v1/responses support planned as well?

If anyone from Databricks or the community has a working example config for Azure OpenAI v1, either through the built-in Azure OpenAI provider or Custom Provider, I’d appreciate it.

Thanks!