Skip to content

Commit de949f5

Browse files
Incorporate feedback.
1 parent b1b8ecc commit de949f5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/application-gateway/application-gateway-backend-health-troubleshooting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -241,7 +241,7 @@ Learn more about [Application Gateway probe matching](https://docs.microsoft.com
241241
**Message:** The server certificate used by the backend is not signed by
242242
a well-known Certificate Authority (CA). Whitelist the backend on the Application Gateway by uploading the root certificate of the server certificate used by the backend.
243243
244-
**Cause:** End-to-end TLS with Application Gateway v2 requires the
244+
**Cause:** End-to-end SSL with Application Gateway v2 requires the
245245
backend server's certificate to be verified in order to deem the server Healthy.
246246
For a TLS/SSL certificate to be trusted, that certificate of the backend
247247
server must be issued by a CA that's included in the trusted
@@ -281,7 +281,7 @@ backend does not match the trusted root certificate added to the
281281
application gateway. Ensure that you add the correct root certificate to
282282
whitelist the backend
283283
284-
**Cause:** End-to-end TLS with Application Gateway v2 requires the
284+
**Cause:** End-to-end SSL with Application Gateway v2 requires the
285285
backend server's certificate to be verified in order to deem the server Healthy.
286286
For a TLS/SSL certificate to be trusted, the backend
287287
server certificate must be issued by a CA that's included in the trusted store of Application Gateway. If the certificate wasn't issued by a trusted CA (for example, a self-signed certificate was used), users should upload the issuer's certificate to Application Gateway.

0 commit comments

Comments
 (0)