Short answer: based on the current Databricks docs, I would treat the built-in Azure OpenAI external model provider as expecting the older Azure OpenAI configuration shape, not the newer `/openai/v1/` shape.

The key clue is that the Databricks Azure OpenAI provider still documents `openai_api_version` as required and says it is “specified by a date”. The example also uses:

"openai_api_base": "https://my-azure-openai-endpoint.openai.azure.com",
"openai_deployment_name": "my-gpt-35-turbo-deployment",
"openai_api_version": "2023-05-15"

So I would not assume that setting openai_api_version = "v1" is supported unless Databricks confirms it.

What I would try:

1. For the built-in Azure OpenAI provider, use the resource root as the base URL:

"openai_api_type": "azure",
"openai_api_base": "https://<resource>.openai.azure.com",
"openai_deployment_name": "<deployment-name>",
"openai_api_version": "<dated-api-version>"

1. If you specifically need the Azure OpenAI v1 URL shape, use the custom provider instead, because Databricks documents custom for OpenAI-compatible providers not directly supported by Databricks.

For chat completions, that would likely look like:

"external_model": {
  "name": "<deployment-name>",
  "provider": "custom",
  "task": "llm/v1/chat",
  "custom_provider_config": {
    "custom_provider_url": "https://<resource>.openai.azure.com/openai/v1/chat/completions",
    "api_key_auth": {
      "key": "api-key",
      "value": "{{secrets/<scope>/<azure-openai-key>}}"
    }
  }
}

Why this works:

Microsoft’s v1 Azure OpenAI API uses:

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

and no longer requires a dated api-version parameter. Databricks’ built-in Azure OpenAI config, however, still documents a dated openai_api_version, deployment name, and Azure resource base URL. So the custom provider is the cleaner fit if you want to call the v1-style endpoint directly.

Caveat:

I would be careful with /openai/v1/responses. Databricks external model tasks are documented around llm/v1/completions, llm/v1/chat, and llm/v1/embeddings, and the custom provider must be OpenAI API compatible for those task shapes. I do not see /responses documented as a supported external model task shape today, so I would expect /openai/v1/chat/completions to be the safer custom-provider target.

For roadmap questions, such as first-class Azure OpenAI v1 support or Responses API support, I think this needs a Databricks product/support confirmation.

References:

• Databricks external models docs: https://docs.databricks.com/aws/en/generative-ai/external-models/
• Microsoft Azure OpenAI v1 API docs: https://learn.microsoft.com/en-us/azure/foundry/openai/api-version-lifecycle?tabs=python