Skip to content

Commit 5c57d85

Browse files
authored
Doc updates for GA annoucnement
New policies to be GA'ed soon https://azure.microsoft.com/en-us/updates/tls1-3-application-gateway-ga/preview/
1 parent a1dd7af commit 5c57d85

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/application-gateway/application-gateway-configure-listener-specific-ssl-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Before you proceed, here are some important points related to listener-specific
3030

3131
- We recommend using TLS 1.2 as this version will be mandated in the future.
3232
- You don't have to configure client authentication on an SSL profile to associate it to a listener. You can have only client authentication or listener-specific SSL policy configured, or both configured in your SSL profile.
33-
- Using a new Predefined or Customv2 policy enhances SSL security and performance for the entire gateway (SSL Policy and SSL Profile). Therefore, you cannot have different listeners on both old as well as new SSL (predefined or custom) policies.
33+
- Using a [2022 Predefined](./application-gateway-ssl-policy-overview.md#predefined-tls-policy) or Customv2 policy enhances SSL security and performance for the entire gateway (SSL Policy and SSL Profile). Therefore, you cannot have different listeners on both old as well as new SSL (predefined or custom) policies.
3434

3535
Consider this example, you are currently using SSL Policy and SSL Profile with "older" policies/ciphers. To use a "new" Predefined or Customv2 policy for any one of them will also require you to upgrade the other configuration. You may use the new predefined policies, or customv2 policy, or combination of these across the gateway.
3636

0 commit comments

Comments
 (0)