Here's the solution:
when creating the Foundry or OpenAI Resource with Terraform, make sure to use the argument "custom_subdomain_name". It should be the same value as the "name" argument.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I am creating an Azure Search with an embedding skillset. The skillset requires a resource URL with openai.azure.com. However when I create an Azure OpenAI Resource, I get the following endpoint:
https://germanywestcentral.api.cognitive.microsoft.com/
This endpoint is NOT ACCEPTED in my embedding skillset! The endpoint I get when creating a Foundry resource was also not accepted!
The Azure OpenAI Resource I created should give me this endpoint:
https://(my open ai service name).openai.azure.com
I am creating my resources with Terraform. On one deployment, the correct endpoint was created for Azure OpenAI but on the next deployment I got the regional endpoint. This is totally inconsistent! Also, if we're supposed to use the "new" Foundry, then its endpoints should **** well be accepted by the skillsets!
Here's the solution:
when creating the Foundry or OpenAI Resource with Terraform, make sure to use the argument "custom_subdomain_name". It should be the same value as the "name" argument.
You're very welcome! I’m glad the information was helpful.
To summarize the resolution for others: when creating the Foundry or Azure OpenAI resource using Terraform, make sure to set the custom_subdomain_name argument and use the same value as the name argument. This ensures the correct *.openai.azure.com endpoint is created and resolves the issue.
If you need any further assistance or run into issues during cleanup or redeployment, please don’t hesitate to reach out. I’ll be happy to help.
Since I’ve converted comment into an answer, could you please take a moment to mark it as Accepted? This helps others in the community with the same question find the solution more easily.
Thank you!