You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/scripts/terraform-secure-backend-frontend.md
+35-30Lines changed: 35 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,43 +4,45 @@ description: Learn how to use terraform provider for App Service to deploy two w
4
4
author: ericgre
5
5
ms.assetid: 3e5d1bbd-5581-40cc-8f65-bc74f1802156
6
6
ms.topic: sample
7
-
ms.date: 12/06/2022
7
+
ms.date: 03/30/2026
8
8
ms.author: ericg
9
9
ms.service: azure-app-service
10
10
ms.custom: devx-track-terraform
11
11
---
12
12
13
13
# Create two web apps connected securely with Private Endpoint and VNet integration
14
14
15
-
This article illustrates an example use of [Private Endpoint](../networking/private-endpoint.md) and regional [VNet integration](../overview-vnet-integration.md) to connect two web apps (frontend and backend) securely with the following terraform configuration:
16
-
- Deploy a VNet
17
-
- Create the first subnet for the integration
18
-
- Create the second subnet for the private endpoint, you have to set a specific parameter to disable network policies
19
-
- Deploy one App Service plan of type Basic, Standard, PremiumV2, PremiumV3, IsolatedV2, Functions Premium (sometimes referred to as the Elastic Premium plan), required for Private Endpoint feature
20
-
- Create the frontend web app with specific app settings to consume the private DNS zone, [more details](../overview-vnet-integration.md#azure-dns-private-zones)
21
-
- Connect the frontend web app to the integration subnet
22
-
- Create the backend web app
23
-
- Create the DNS private zone with the name of the private link zone for web app privatelink.azurewebsites.net
24
-
- Link this zone to the VNet
25
-
- Create the private endpoint for the backend web app in the endpoint subnet, and register DNS names (website and SCM) in the previously created DNS private zone
15
+
This article illustrates an example use of [Private Endpoint](../networking/private-endpoint.md) and regional [VNet integration](../overview-vnet-integration.md) to connect two web apps (frontend and backend) securely with the following Terraform configuration:
16
+
17
+
1. Deploy a VNet
18
+
1. Create the first subnet for the integration
19
+
1. Create the second subnet for the private endpoint, and disable subnet network policies for private endpoints (set `private_endpoint_network_policies_enabled = false`)
20
+
1. Deploy one App Service plan of type Basic, Standard, PremiumV2, PremiumV3, IsolatedV2, Functions Premium (sometimes referred to as the Elastic Premium plan), required for the Private Endpoint feature
21
+
1. Create the frontend web app with specific app settings to consume the private DNS zone. For more information, see [Azure DNS private zones](../overview-vnet-integration.md#azure-dns-private-zones).
22
+
1. Connect the frontend web app to the integration subnet
23
+
1. Create the backend web app
24
+
1. Create the DNS private zone with the name of the private link zone for web apps (`privatelink.azurewebsites.net`)
25
+
1. Link this zone to the VNet
26
+
1. Create the private endpoint for the backend web app in the endpoint subnet, and register DNS names (site and SCM) in the previously created DNS private zone
26
27
27
28
## How to use terraform in Azure
28
29
29
30
Browse to the [Azure documentation](/azure/developer/terraform/) to learn how to use terraform with Azure.
30
31
31
32
## The complete terraform file
32
33
33
-
To use this file, replace the placeholders _\<unique-frontend-app-name>_ and _\<unique-backend-app-name>_ (app name is used to form a unique DNS name worldwide).
34
+
To use this file, replace the placeholders _\<unique-frontend-app-name>_ and _\<unique-backend-app-name>_ (app name is used to form a unique DNS name worldwide).
0 commit comments