First-party web_search_preview tool does not work with Azure OpenAI

[snoozy]

Description

Repro (run a couple times, it's flakey):

import { createAzure } from "@ai-sdk/azure";

export const azureAiReasoning = createAzure({
  resourceName: "<>",
  apiKey: <>,
  apiVersion: "preview",
});

const res = await generateText({
  model: providers.azureAiReasoning.responses("gpt-5.1-codex"),
  temperature: 1,
  tools: {
    web_search_preview: azureAiReasoning.tools.webSearchPreview({}),
  },
  providerOptions: {
    openai: {
      reasoningEffort: "high",
      maxCompletionTokens: 32_000,
    },
  },
  messages: [
    {
      role: "user",
      content:
        "Make a static website for today's stock news, use web search and make sure to use open_page",
    },
  ],
});

Triggers this error:

ZodError: [
      {
        "expected": "string",
        "code": "invalid_type",
        "path": [
          "output",
          9,
          "action",
          "url"
        ],
        "message": "Invalid input: expected string, received undefined"
      }
    ]

I believe this may be related to #9308

AI SDK Version

• "ai": "^5.0.100",
• "@ai-sdk/azure": "^2.0.75",
• "@ai-sdk/openai": "^2.0.73",

Code of Conduct

• I agree to follow this project's Code of Conduct

[tsuzaki430]

@snoozy

Thank you message!

One thing that looks a bit suspicious to me is this part:

apiVersion: "preview",

For the Azure OpenAI / Azure AI “v1”-compatible endpoint, if you leave apiVersion undefined, the SDK will default it to "v1". That’s the version we currently validate the Responses API + web_search_preview tool against.

Could you try either:

• removing the apiVersion field so it falls back to the default, or
• explicitly setting apiVersion: "v1"

and see if you can still reproduce the Zod error?

If it still happens with apiVersion: "v1", that would help narrow down whether this is an SDK-side schema issue or something specific to the "preview" API version.

[snoozy]

Hi @tsuzaki430 !

Yep, I tried both setting the apiVersion: "v1" and completely removing it as well. Both times I was able to reproduce the same Zod error.

[tsuzaki430]

@snoozy

Thank you for letting me know.
I tried it a little,
is it something like this?
I felt that the output structure was slightly different, possibly due to the different models.

 Error message: [
    {
      "expected": "string",
      "code": "invalid_type",
      "path": [
        "output",
        3,
        "action",
        "url"
      ],
      "message": "Invalid input: expected string, received undefined"
    }
  ]

If it's different, I'd appreciate it if you could let me know.

[snoozy]

Hi @tsuzaki430 - yep, that is the same error I am hitting! Basically, the action.url in the output array is null, when it is typed as non-null.

[tsuzaki430]

@snoozy

If you’d like, I can create a pull request and submit the fix — would that be alright?

[snoozy]

@tsuzaki430 yes that would be amazing, thank you!

[tsuzaki430]

Hello , @snoozy

• fix(openai): allow open_page action type url to be nullish #10646

It looks like this pull request addresses the error mentioned in this issue.
Please watch and wait this PR.😊

@ai-sdk/azure shares many common parts with @ai-sdk/open, and once this is merged, the same changes will be applied to @ai-sdk/azure as well.

Thank you.

[aayush-kapoor]

hi @snoozy @tsuzaki430, thanks for highlighting the PR. We're just waiting to confirm something and then we'll land that PR soon.

[tsuzaki430]

@aayush-kapoor

Hello,

When I met your this PR,I felt very happy!
Thank you for message and helpfull PR!

[aayush-kapoor]

marking this as closed since it's a duplicate of the issue #9308