Merge pull request #97189 from damendo/patch-1

Updating parameters

Author: PRMerger20

articles/network-watcher/network-watcher-diagnose-on-premises-connectivity.md

@@ -38,7 +38,7 @@ You want to configure a site-to-site connection between Azure and on-premises us
 
 Detailed step by step guidance for configuring a Site-to-Site configuration can be found by visiting: [Create a VNet with a Site-to-Site connection using the Azure portal](../vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal.md).
 
-One of the critical configuration steps is configuring the IPsec communication parameters, any misconfiguration leads to loss of connectivity between the on-premises network and Azure. Currently Azure VPN Gateways are configured to support the following IPsec parameters for Phase 1. Note, as mentioned earlier these settings cannot be modified.  As you can see in the table below, the encryption algorithms supported by Azure VPN Gateway are AES256, AES128, and 3DES.
+One of the critical configuration steps is configuring the IPsec communication parameters, any misconfiguration leads to loss of connectivity between the on-premises network and Azure. Currently Azure VPN Gateways are configured to support the following IPsec parameters for Phase 1. As you can see in the table below, the encryption algorithms supported by Azure VPN Gateway are AES256, AES128, and 3DES.
 
 ### IKE phase 1 setup
 
@@ -49,7 +49,7 @@ One of the critical configuration steps is configuring the IPsec communication p
 | Authentication Method |Pre-Shared Key |Pre-Shared Key |
 | Encryption Algorithms |AES256 AES128 3DES |AES256 3DES |
 | Hashing Algorithm |SHA1(SHA128) |SHA1(SHA128), SHA2(SHA256) |
-| Phase 1 Security Association (SA) Lifetime (Time) |28,800 seconds |10,800 seconds |
+| Phase 1 Security Association (SA) Lifetime (Time) |28,800 seconds |28,800 seconds |
 
 As a user, you would be required to configure your FortiGate, a sample configuration can be found on [GitHub](https://github.com/Azure/Azure-vpn-config-samples/blob/master/Fortinet/Current/fortigate_show%20full-configuration.txt). Unknowingly you configured your FortiGate to use SHA-512 as the hashing algorithm. As this algorithm is not a supported algorithm for policy-based connections, your VPN connection does work.