Merge pull request #286259 from KimForss/main

Add NAT Gateway variables

Author: prmerger-automator[bot]

articles/sap/automation/configure-workload-zone.md

@@ -4,7 +4,7 @@ description: Overview of the SAP workload zone configuration process within SAP
 author: kimforss
 ms.author: kimforss
 ms.reviewer: kimforss
-ms.date: 3/5/2024
+ms.date: 3/9/2024
 ms.topic: conceptual
 ms.service: sap-on-azure
 ms.subservice: sap-automation
@@ -277,6 +277,20 @@ ANF_service_level         = "Ultra"
 > | `use_custom_dns_a_registration`	    | Use an existing private DNS zone.                                        | Optional |
 
 
+### NAT support
+
+> [!div class="mx-tdCol2BreakAll "]
+> | Variable                              | Description                                                              | Type     |
+> | ------------------------------------- | ------------------------------------------------------------------------ | -------- |
+> | `deploy_nat_gateway`                  | If set, deploys a NAT gateway.                                           | Optional |
+> | `nat_gateway_name`                  	| The name of the NAT Gateway.                                             | Optional |
+> | `nat_gateway_arm_id`                  | The Azure resource identifier of the NAT Gateway.                        | Optional |
+> | `nat_gateway_public_ip_zones`	        | The zones for the NAT Gateway public IP address                          | Optional |
+> | `nat_gateway_public_ip_arm_id`        | TThe Azure resource identifier for the NAT Gateway public IP address     | Optional |
+> | `nat_gateway_idle_timeout_in_minutes`	| The idle timeout in minutes for the NAT Gateway (default=4)              | Optional |
+> | `nat_gateway_public_ip_tags`	        | Tags for the public IP resource                                          | Optional |
+
+
 ## Other parameters
 
 > [!div class="mx-tdCol2BreakAll "]

articles/sap/automation/plan-deployment.md

@@ -128,6 +128,7 @@ Before you design your workload zone layout, consider the following questions:
 * How many workload zones does your scenario require (development, quality assurance, and production)?
 * Are you deploying into new virtual networks or are you using existing virtual networks?
 * What storage type do you need for the shared storage (Azure Files NFS or Azure NetApp Files)?
+* Are you going to deploy NAT Gateway for outbound internet connectivity?
 
 The default naming convention for workload zones is `[ENVIRONMENT]-[REGIONCODE]-[NETWORK]-INFRASTRUCTURE`. For example, `DEV-WEEU-SAP01-INFRASTRUCTURE` is for a development environment hosted in the West Europe region by using the SAP01 virtual network. `PRD-WEEU-SAP02-INFRASTRUCTURE` is for a production environment hosted in the West Europe region by using the SAP02 virtual network.