Skip to content

Commit 0c7d2db

Browse files
committed
update networking doc cert ref
1 parent 15efe0e commit 0c7d2db

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/container-apps/networking.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -296,7 +296,7 @@ This feature is supported for both Consumption and Dedicated plans in workload p
296296

297297
#### Considerations
298298
- Private endpoints on Azure Container Apps only support inbound HTTP traffic. TCP traffic is not supported.
299-
- To use a private endpoint with a custom domain and an *Apex domain* as the *Hostname record type*, you must configure a private DNS zone with the same name as your public DNS. In the record set, configure your private endpoint's private IP address instead of the container app environment's IP address. When configuring your custom domain with CNAME, the setup is unchanged. For more information, see [Set up custom domain with existing certificate](custom-domains-certificates.md) or [Set up custom domains with free managed cretificate](custom-domains-managed-certificates.md).
299+
- To use a private endpoint with a custom domain and an *Apex domain* as the *Hostname record type*, you must configure a private DNS zone with the same name as your public DNS. In the record set, configure your private endpoint's private IP address instead of the container app environment's IP address. When configuring your custom domain with CNAME, the setup is unchanged. For more information, see [Set up custom domain with existing certificate](custom-domains-certificates.md).
300300
- Your private endpoint's VNet can be separate from the VNet integrated with your container app.
301301
- You can add a private endpoint to both new and existing workload profile environments.
302302

0 commit comments

Comments
 (0)