Skip to content

Commit acdd843

Browse files
Merge pull request #539 from jesweare/patch-1
Add URL specification requirements for sending requests to the private endpoint
2 parents c38ddea + 0915cbd commit acdd843

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/ai-services/cognitive-services-virtual-networks.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -537,6 +537,9 @@ When you create a private endpoint, specify the Azure AI services resource that
537537
> [!NOTE]
538538
> Azure OpenAI in Azure AI Foundry Models uses a different private DNS zone and public DNS zone forwarder than other Azure AI services. For the correct zone and forwarder names, see [Azure services DNS zone configuration](/azure/private-link/private-endpoint-dns#azure-services-dns-zone-configuration).
539539
540+
> [!WARNING]
541+
> Requests from clients to the private endpoint need to specify the [custom subdomain](/azure/ai-services/cognitive-services-custom-subdomains) of your Azure AI services resource as the endpoint base URL.
542+
540543
Clients on a virtual network that use the private endpoint use the same connection string for the Azure AI services resource as clients connecting to the public endpoint. The exception is the Speech service, which requires a separate endpoint. For more information, see [Use private endpoints with the Speech service](#use-private-endpoints-with-the-speech-service) in this article. DNS resolution automatically routes the connections from the virtual network to the Azure AI services resource over a private link.
541544
542545
By default, Azure creates a [private DNS zone](/azure/dns/private-dns-overview) attached to the virtual network with the necessary updates for the private endpoints. If you use your own DNS server, you might need to make more changes to your DNS configuration. For updates that might be required for private endpoints, see [Apply DNS changes for private endpoints](#apply-dns-changes-for-private-endpoints) in this article.

0 commit comments

Comments
 (0)