Added Dedicated backend connection and certificate validation options in template for application Gateway Backend Settings (#35161)

Co-authored-by: Rajat Gupta <[email protected]>
Co-authored-by: Prajjwal Kamboj <[email protected]>

Author: 3 people

specification/network/resource-manager/Microsoft.Network/stable/2024-10-01/applicationGateway.json

@@ -1879,6 +1879,24 @@
           "type": "string",
           "description": "Path which should be used as a prefix for all HTTP requests. Null means no path will be prefixed. Default value is null."
         },
+        "dedicatedBackendConnection": {
+          "type": "boolean",
+          "description": "Enable or disable dedicated connection per backend server. Default is set to false."
+        },
+        "validateCertChainAndExpiry": {
+          "type": "boolean",
+          "default": true,
+          "description": "Verify or skip both chain and expiry validations of the certificate on the backend server. Default is set to true."
+        },
+        "validateSNI": {
+          "type": "boolean",
+          "default": true,
+          "description": "When enabled, verifies if the Common Name of the certificate provided by the backend server matches the Server Name Indication (SNI) value. Default value is true."
+        },
+        "sniName": {
+          "type": "string",
+          "description": "Specify an SNI value to match the common name of the certificate on the backend. By default, the application gateway uses the incoming request’s host header as the SNI. Default value is null."
+        },
         "provisioningState": {
           "readOnly": true,
           "$ref": "./network.json#/definitions/ProvisioningState",