Merge pull request #288524 from cherylmc/SFI-10

SFI update

Author: denrea

articles/vpn-gateway/bgp-howto.md

@@ -5,7 +5,7 @@ description: Learn how to configure BGP for Azure VPN Gateway using the Azure po
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 04/20/2023
+ms.date: 10/16/2024
 ms.author: cherylmc 
 
 ---
@@ -125,7 +125,7 @@ Before proceeding, make sure you have enabled BGP for the VPN gateway.
 Configure a local network gateway with BGP settings.
 
 * For information and steps, see the [local network gateway](tutorial-site-to-site-portal.md#LocalNetworkGateway) section in the site-to-site connection article.
-* If you already have a local network gateway, you can modify it.To modify a local network gateway, go to the local network gateway resource **Configuration** page and make any necessary changes.
+* If you already have a local network gateway, you can modify it. To modify a local network gateway, go to the local network gateway resource **Configuration** page and make any necessary changes.
 
 1. When you create the local network gateway, for this exercise, use the following values:
 

articles/vpn-gateway/media/nat-howto/all-nat-rules.png

@@ -5,7 +5,7 @@ description: Learn how to configure NAT for Azure VPN Gateway.
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: how-to
-ms.date: 10/15/2024
+ms.date: 10/16/2024
 ms.author: cherylmc 
 
 ---
@@ -71,9 +71,9 @@ Before you create connections, you must create and save NAT rules on the VPN gat
 
 | Name     | Type   | Mode        | Internal    | External     | Connection          |
 | ---      | ---    | ---         | ---         | ---          | ---                 |
-| VNet     | Static | EgressSNAT  | 10.0.1.0/24 | 100.0.1.0/24 | Both connections    |
-| Branch1 | Static | IngressSNAT | 10.0.1.0/24 | 100.0.2.0/24 | Branch1 connection |
-| Branch2 | Static | IngressSNAT | 10.0.1.0/24 | 100.0.3.0/24 | Branch2 connection |
+| VNet     | Static | EgressSNAT  | 10.0.1.0/24 | 192.168.1.0/24 | Both connections    |
+| Branch1 | Static | IngressSNAT | 10.0.1.0/24 | 192.168.2.0/24| Branch1 connection |
+| Branch2 | Static | IngressSNAT | 10.0.1.0/24 | 192.168.3.0/24 | Branch2 connection |
 
 Use the following steps to create all the NAT rules on the VPN gateway. If you're using BGP, select **Enable** for the Enable Bgp Route Translation setting.
 

articles/vpn-gateway/media/nat-howto/disable-bgp.png

@@ -5,7 +5,7 @@ description: Learn about NAT (Network Address Translation) in Azure VPN to conne
 author: cherylmc
 ms.service: azure-vpn-gateway
 ms.topic: conceptual
-ms.date: 05/02/2023
+ms.date: 10/16/2024
 ms.author: cherylmc
 ms.custom: template-concept
 ---
@@ -80,11 +80,11 @@ The following diagram shows an example of Azure VPN NAT configurations:
 
 The diagram shows an Azure VNet and two on-premises networks, all with address space of 10.0.1.0/24. To connect these two networks to the Azure VNet and VPN gateway, create the following rules:
 
-* IngressSNAT rule 1: This rule translates the on-premises address space 10.0.1.0/24 to 100.0.2.0/24.
+* IngressSNAT rule 1: This rule translates the on-premises address space 10.0.1.0/24 192.168.2.0/24.
 
-* IngressSNAT rule 2: This rule translates the on-premises address space 10.0.1.0/24 to 100.0.3.0/24.
+* IngressSNAT rule 2: This rule translates the on-premises address space 10.0.1.0/24 to 192.168.3.0/24.
 
-* EgressSNAT rule 1: This rule translates the VNet address space 10.0.1.0/24 to 100.0.1.0/24.
+* EgressSNAT rule 1: This rule translates the VNet address space 10.0.1.0/24 to 192.168.1.0/24.
 
 In the diagram, each connection resource has the following rules:
 
@@ -98,11 +98,11 @@ In the diagram, each connection resource has the following rules:
 
 Based on the rules associated with the connections, here are the address spaces for each network:
 
-| Network  | Original    | Translated   |
-| ---      | ---         | ---          |
-| VNet     | 10.0.1.0/24 | 100.0.1.0/24 |
-| Branch 1 | 10.0.1.0/24 | 100.0.2.0/24 |
-| Branch 2 | 10.0.1.0/24 | 100.0.3.0/24 |
+| Network  | Original    | Translated     |
+| ---      | ---         | ---            |
+| VNet     | 10.0.1.0/24 | 192.168.1.0/24 |
+| Branch 1 | 10.0.1.0/24 | 192.168.2.0/24 |
+| Branch 2 | 10.0.1.0/24 | 192.168.3.0/24 |
 
 The following diagram shows an IP packet from Branch 1 to VNet, before and after the NAT translation:
 

articles/vpn-gateway/media/nat-overview/nat-packet.png

@@ -2,7 +2,7 @@
  author: cherylmc
  ms.service: azure-vpn-gateway
  ms.topic: include
- ms.date: 01/23/2024
+ ms.date: 10/16/2024
  ms.author: cherylmc
 ---
 ### Is NAT supported on all Azure VPN Gateway SKUs?
@@ -57,8 +57,8 @@ In either case, you don't need destination network address translation (DNAT) ru
 
 You need to create one NAT rule for each prefix, because each NAT rule can include only one address prefix for NAT. For example, if the address space for the local network gateway consists of 10.0.1.0/24 and 10.0.2.0/25, you can create two rules:
 
-* **IngressSNAT** rule 1: Map 10.0.1.0/24 to 100.0.1.0/24.
-* **IngressSNAT** rule 2: Map 10.0.2.0/25 to 100.0.2.0/25.
+* **IngressSNAT** rule 1: Map 10.0.1.0/24 to 192.168.1.0/24.
+* **IngressSNAT** rule 2: Map 10.0.2.0/25 to 192.168.2.0/25.
 
 The two rules must match the prefix lengths of the corresponding address prefixes. The same guideline applies to **EgressSNAT** rules for the VNet address space.