An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
Hi Surendra,
This is often related to Private DNS resolution rather than the private endpoint itself. If you're using multiple private endpoints across regions, verify that the Foundry agent resolves the Azure AI Search FQDN to the correct regional private endpoint IP and that the required Private DNS Zones (for example, privatelink.search.windows.net) are linked to the VNet hosting the agent. Microsoft also recommends validating DNS resolution from within the VNet using nslookup.
Also, verify that the Azure AI Search resource has its own private endpoint, as this isn't created automatically with Azure AI Foundry deployments, and ensure NSGs, UDRs, and firewall rules allow connectivity between the agent and the Search service. If DNS and networking are configured correctly and the issue persists, capture the Request ID, enable diagnostic logs, and open a Microsoft support case. This will help determine whether the problem is related to a service-side issue with multi-region private endpoint routing.
Please "Accept the answer" if this information helped you. This will help us and others in the community as well.