Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.
I see you are referring to the Azure Update : Default outbound access for VMs in Azure will be retired.
- The above announcement is for Virtual Machines
- Not for PaaS Services that are integrated into a VNET.
Default outbound access document is for Virtual Machines residing in a VNET.
For other PaaS Service, you should check their Networking requirements to understand how they provide inbound and outbound access.
In your case,
#1 Azure Container Apps
- I see Azure Container Apps supporting NAT gateway for Workload profiles Environment type
- And the advantage of this feature is to have a fixed, non changing "Outbound public IP" for your PaaS Service.
- If you don't have a NAT, still you will be able to make outbound connections but you will not have control over which IP would be used.
See : Azure Container Apps support for NAT Gateway
- You can also use Azure Firewall, but the intention here is to restrict/limit access to internet (control which sites should be reachable) rather than merely providing outbound IP.
#2 Azure Database for PostgreSQL
-
I don't see any documents claiming NAT Gateway support for a VNET Integrated Azure Database for PostgreSQL - Flexible Server
- Moreover, I don't think this DB service is capable of making outbound calls on it's own in the first place, unlike Azure Container Apps
- I am not an expert on PostgreSQL - Flexible Server but are you sure this service is making outbound internet calls currently?
- The entire document Networking overview for Azure Database for PostgreSQL - talks about connecting to the DB and I am afraid I don't see any line stating outbound connectivity
Kindly let us know if this helps or you need further assistance on this issue.
Thanks,
Kapil
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.