diff --git a/generator/ServiceModels/apigateway/apigateway-2015-07-09.docs.json b/generator/ServiceModels/apigateway/apigateway-2015-07-09.docs.json
index cdbfc6cec6d6..af652c04bb20 100644
--- a/generator/ServiceModels/apigateway/apigateway-2015-07-09.docs.json
+++ b/generator/ServiceModels/apigateway/apigateway-2015-07-09.docs.json
@@ -247,7 +247,7 @@
         "SdkConfigurationProperty$required": "<p>A boolean flag of an SdkType configuration property to indicate if the associated SDK configuration property is required (<code>true</code>) or not (<code>false</code>).</p>",
         "Stage$cacheClusterEnabled": "<p>Specifies whether a cache cluster is enabled for the stage.</p>",
         "Stage$tracingEnabled": "<p>Specifies whether active tracing with X-ray is enabled for the Stage.</p>",
-        "TlsConfig$insecureSkipVerification": "<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for <code>HTTP</code> and <code>HTTP_PROXY</code> integrations.</p>"
+        "TlsConfig$insecureSkipVerification": "<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for <code>HTTP</code> and <code>HTTP_PROXY</code> integrations.</p> <important> <p>Enabling <code>insecureSkipVerification</code> isn't recommended, especially for integrations with public HTTPS endpoints. If you enable <code>insecureSkipVerification</code>, you increase the risk of man-in-the-middle attacks.</p> </important>"
       }
     },
     "CacheClusterSize": {
diff --git a/generator/ServiceModels/apigateway/apigateway-2015-07-09.normal.json b/generator/ServiceModels/apigateway/apigateway-2015-07-09.normal.json
index f7f981624a89..bb06a09a7408 100644
--- a/generator/ServiceModels/apigateway/apigateway-2015-07-09.normal.json
+++ b/generator/ServiceModels/apigateway/apigateway-2015-07-09.normal.json
@@ -6536,7 +6536,7 @@
       "members":{
         "insecureSkipVerification":{
           "shape":"Boolean",
-          "documentation":"<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for <code>HTTP</code> and <code>HTTP_PROXY</code> integrations.</p>"
+          "documentation":"<p>Specifies whether or not API Gateway skips verification that the certificate for an integration endpoint is issued by a supported certificate authority. This isn’t recommended, but it enables you to use certificates that are signed by private certificate authorities, or certificates that are self-signed. If enabled, API Gateway still performs basic certificate validation, which includes checking the certificate's expiration date, hostname, and presence of a root certificate authority. Supported only for <code>HTTP</code> and <code>HTTP_PROXY</code> integrations.</p> <important> <p>Enabling <code>insecureSkipVerification</code> isn't recommended, especially for integrations with public HTTPS endpoints. If you enable <code>insecureSkipVerification</code>, you increase the risk of man-in-the-middle attacks.</p> </important>"
         }
       },
       "documentation":"<p>Specifies the TLS configuration for an integration.</p>"
diff --git a/sdk/src/Services/APIGateway/Generated/Model/TlsConfig.cs b/sdk/src/Services/APIGateway/Generated/Model/TlsConfig.cs
index 90e09d45b0a3..24d69d7d019b 100644
--- a/sdk/src/Services/APIGateway/Generated/Model/TlsConfig.cs
+++ b/sdk/src/Services/APIGateway/Generated/Model/TlsConfig.cs
@@ -46,6 +46,13 @@ public partial class TlsConfig
         /// hostname, and presence of a root certificate authority. Supported only for <code>HTTP</code>
         /// and <code>HTTP_PROXY</code> integrations.
         /// </para>
+        ///  <important> 
+        /// <para>
+        /// Enabling <code>insecureSkipVerification</code> isn't recommended, especially for integrations
+        /// with public HTTPS endpoints. If you enable <code>insecureSkipVerification</code>,
+        /// you increase the risk of man-in-the-middle attacks.
+        /// </para>
+        ///  </important>
         /// </summary>
         public bool InsecureSkipVerification
         {