Skip to content

Commit 9eac258

Browse files
Update networking.md
1 parent 2fe9bd6 commit 9eac258

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/container-apps/networking.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -272,7 +272,7 @@ You can use NAT Gateway to simplify outbound connectivity for your outbound inte
272272

273273
When you configure a NAT Gateway on your subnet, the NAT Gateway provides a static public IP address for your environment. All outbound traffic from your container app is routed through the NAT Gateway's static public IP address.
274274

275-
### <a name="public-network-access"></a>Public network access (preview)
275+
### <a name="public-network-access"></a>Public network access
276276

277277
The public network access setting determines whether your container apps environment is accessible from the public Internet. Whether you can change this setting after creating your environment depends on the environment's virtual IP configuration. The following table shows valid values for public network access, depending on your environment's virtual IP configuration.
278278

@@ -285,7 +285,7 @@ In order to create private endpoints on your Azure Container App environment, pu
285285

286286
Azure networking policies are supported with the public network access flag.
287287

288-
### <a name="private-endpoint"></a>Private endpoint (preview)
288+
### <a name="private-endpoint"></a>Private endpoint
289289

290290
Azure private endpoint enables clients located in your private network to securely connect to your Azure Container Apps environment through Azure Private Link. A private link connection eliminates exposure to the public internet. Private endpoints use a private IP address in your Azure virtual network address space.
291291

0 commit comments

Comments
 (0)