Is Azure Open AI Private Link to Azure AI Search supported in infrastructure as code

Shabash, Boris 20 Reputation points
2024-06-07T21:45:26.16+00:00

I have an Azure Open AI resource as well as an Azure AI Search resources. I have followed the guidelines in "Disable public network access" and filled out the form required to have the private endpoint provisioned.

However, I am curious if once the private endpoint is provisioned, if it is supported as part of the Infrastructure as Code paradigm and if its allocation can be automated under a new setup, or if this process is required every time a new set of resources is created

Azure AI Search
Azure AI Search
An Azure search service with built-in artificial intelligence capabilities that enrich information to help identify and explore relevant content at scale.
797 questions
Azure OpenAI Service
Azure OpenAI Service
An Azure service that provides access to OpenAI’s GPT-3 models with enterprise capabilities.
2,430 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Gowtham CP 3,335 Reputation points
    2024-06-08T05:22:47.6366667+00:00

    Hello Shabash, Boris ,

    Thank you for reaching out on the Microsoft Q&A .

    While you can't fully automate the private connection between Azure OpenAI and Azure AI Search using infrastructure as code (IaC) yet, you can still streamline most of the setup. Here's how:

    1. Use Azure PowerShell or CLI scripts in your IaC pipelines to create private endpoint connections Azure documentation .
    2. Use Bicep or ARM templates to automate the provisioning of resources like the VNet, subnet, and AI Search service.
    3. After deployment, manually initiate the private endpoint connection for Azure OpenAI through the Azure portal.

    This approach reduces manual work, even though it isn't fully automated.

    I hope this helps! If you have any further questions, feel free to ask.

    If the information is useful, please accept the answer and upvote it to assist other community members.

    0 comments No comments