iTranslated by AI

The content below is an AI-generated translation. This is an experimental feature, and may contain errors. View original article
🌐

Azure Container Apps Ingress Patterns Part 3: External Environment with Private Endpoint

に公開
2026/01/20

Introduction

This article documents my experience building and testing Ingress configuration patterns in Azure Container Apps.

https://zenn.dev/georgeosddev/articles/azure-container-apps-ingress-architecture-patterns

In this article, I will focus on Pattern 3.

Configuration

I have omitted the components marked as "(Optional)" in the mermaid diagram above. For the environment created in the previous pattern (Pattern 2), I will disable Public Network Access and allow access only via a Private Endpoint.

https://zenn.dev/georgeosddev/articles/azure-container-apps-ingress-pattern-2

Disabling Public Network Access

aca-env-without-vnet

env-pna-disabled

First, I will verify the behavior with Public Network Access disabled, without attaching a PE.

A 403 response is returned.

$ curl -I https://aca-without-vnet.whitemoss-043fed62.japaneast.azurecontainerapps.io/
HTTP/2 403
content-type: text/html; charset=utf-8
content-length: 233
date: Fri, 09 Jan 2026 06:35:20 GMT

client-pna-disabled-403

The public network access on this managed environment is disabled. To connect to this managed environment, please use the Private Endpoint from inside your virtual network. To learn more https://aka.ms/PrivateEndpointTroubleshooting.

It is expected to receive a 403 error since no Private Endpoint is attached. Regardless of the Ingress.external setting of the App, public access to this Env results in the same response.

Note that since this status affects the Public Network Access of the Env, access within the Env using the .internal. FQDN and the <App Name> remains possible.

root@aca-without-vnet-2--0000003-558c795cc9-t9hhp:/# curl -I https://aca-without-vnet.internal.whitemoss-043fed62.japaneast.azurecontainerapps.io/
HTTP/2 200
server: nginx/1.28.1
date: Fri, 09 Jan 2026 06:43:59 GMT
content-type: text/html
content-length: 615
last-modified: Tue, 23 Dec 2025 18:40:33 GMT
etag: "694ae221-267"
accept-ranges: bytes

root@aca-without-vnet-2--0000003-558c795cc9-t9hhp:/# curl -I http://aca-without-vnet
HTTP/1.1 200 OK
server: nginx/1.28.1
date: Fri, 09 Jan 2026 06:45:03 GMT
content-type: text/html
content-length: 615
last-modified: Tue, 23 Dec 2025 18:40:33 GMT
etag: "694ae221-267"
accept-ranges: bytes

Adding Private Endpoint

I will create a Private Endpoint.

Private Endpoint

Private DNS Zone

This Private Endpoint is placed in a user-owned subnet. This is because the Private Endpoint itself supports linking resources that reside in a different VNet than the Private Endpoint.

What is a private endpoint? - Azure Private Link | Microsoft Learn

Private Link resources can be deployed in a different region than the virtual network and private endpoint.

In this case, since the ACA Env itself does not use a custom VNet, I placed the Private Endpoint in a separately prepared VNet.

Access from clients that can access the Private Endpoint (clients inside the VNet)

I am using the target VNet and an App Service with VNet integration as the client environment. I will test this from the Kudu container.

Client in PE Vnet

As expected, it reaches the Env using the Private Endpoint IP address 10.0.0.4. For the app with ingress.external set to true (aca-without-vnet-2), it reaches the app (Nginx), while for the app with ingress.external set to false (aca-without-vnet), it returns 404 as before.

Access from clients that cannot access the Private Endpoint (clients outside the VNet)

The connection is no longer possible, rather than just returning 403.

Connection_closed

$ curl -v https://aca-without-vnet-2.whitemoss-043fed62.japaneast.azurecontainerapps.io
*   Trying 4.241.230.64:443...
* Connected to aca-without-vnet-2.whitemoss-043fed62.japaneast.azurecontainerapps.io (4.241.230.64) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.0 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, decode error (562):
* error:0A000126:SSL routines::unexpected eof while reading
* Closing connection 0
curl: (35) error:0A000126:SSL routines::unexpected eof while reading

It seems to be resolving to 4.241.230.64.

$ nslookup aca-without-vnet-2.whitemoss-043fed62.japaneast.azurecontainerapps.io
;; Got recursion not available from 172.17.240.1
Server:         172.17.240.1
Address:        172.17.240.1#53

Non-authoritative answer:
aca-without-vnet-2.whitemoss-043fed62.japaneast.azurecontainerapps.io   canonical name = whitemoss-043fed62.privatelink.japaneast.azurecontainerapps.io.
Name:   whitemoss-043fed62.privatelink.japaneast.azurecontainerapps.io
Address: 4.241.230.64

It is not exactly what I expected, but perhaps that is how it behaves.

When I delete the Private Endpoint, it resolves to 130.33.219.240 again, returning to the behavior observed when Disabling Public Network Access.

nslookup aca-without-vnet-2.whitemoss-043fed62.japaneast.azurecontainerapps.io
;; Got recursion not available from 172.17.240.1
Server:         172.17.240.1
Address:        172.17.240.1#53

Non-authoritative answer:
Name:   aca-without-vnet-2.whitemoss-043fed62.japaneast.azurecontainerapps.io
Address: 130.33.219.240

Integration with Azure Front Door

In this case, the client using the Private Endpoint existed within the same VNet where the Private Endpoint was placed. However, by integrating with Azure Front Door, it is also possible to connect via the path Internet -> Front Door -> PE -> Env.

Access Azure Container Apps using Azure Front Door | Microsoft Learn

Summary

When an Env itself uses a custom VNet, clients within that custom VNet can communicate with the Env privately, so there is no need to place a Private Endpoint in that VNet.

Use cases for Private Endpoints include:

  • Cases where you are not using a custom VNet, and you want to meet requirements that cannot be covered by IP restrictions.
  • Cases where you are using a custom VNet, but you want to communicate privately from a different VNet (without peering).
  • Integration with Front Door.

These seem to be the primary scenarios for using them.

completed

Discussion