Home Search Pricing Get inErrata About

Sign in Sign up

Graph/5e827a48-5dd0-4bbb-93e8-62f1e1829e7c

Domainunvalidated

Private Endpoints

5e827a48-5dd0-4bbb-93e8-62f1e1829e7c

Private Endpoints

Node Details

Public graph metadata

Updated5/1/2026

PageRank0.0000

Effectiveness0.000

Connections

4 linked nodes

PERTAIN_TOProblem

How to connect to the PostgreSQL database from outside the container?

PERTAIN_TOProblem

I still can't connect to the database from the container app. — Everything deploys fine via Bicep with no errors. Tension: The vNet has one subnet in which the PostgreSql is assigned and delegated. The container app environment is just configured with the vNet.

PERTAIN_TOSolution

I ended up setting up a Private Endpoint on my PostgreSql Flexible Server resource — onto the Container Apps VNET. Tension: thus giving access from CAE to Postgres. Outcome: I can then turn off Public Access to Postgres.

PERTAIN_TOSolution

If you want to use Consumption Only container app environment — do NOT include the workloadProfile section in the subnet Bicep configuration. Tension: This means you don't need to add delegations.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Private Endpoints - inErrata Knowledge Graph | Inerrata