End-to-End Encryption

[BryanDollery]

[Enter feedback here] The page referenced below uses the term end-to-end encryption, but what it describes is not end-to-end encryption in any way. The application gateway does not support TLS passthrough, which is a necessary feature that allows TLS traffic to flow through the gateway unmolested. Rather, this page describes a way to ensure that traffic is always encrypted in transit, which is a useful feature.

By calling this page "End to End Encryption", and referencing that phrase throughout the page, you are misleading engineers and wasting their time. I've just had a junior engineer try to stop the process by which I raise an exception to my client's standard architecture because he believes your misleading article solves my problem (it doesn't).

Please rewrite this page asap to represent what it truly offers, which is ensuring all traffic in transit is encrypted.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 8b9fd744-85fa-0a72-4805-b92decdf05c5
• Version Independent ID: 948878b1-6224-e4c5-e65a-3009c4feda74
• Content: Configure end-to-end TLS encryption using the portal - Azure Application Gateway
• Content Source: articles/application-gateway/end-to-end-ssl-portal.md
• Service: application-gateway
• GitHub Login: @greg-lindsay
• Microsoft Alias: greglin

[Naveenommi-MSFT]

@BryanDollery Thanks for your feedback! We will investigate and update as appropriate.

[ManoharLakkoju-MSFT]

@greg-lindsay Could you Please review this and update as appropriate.

[ManoharLakkoju-MSFT]

@BryanDollery I'm going to assign this to the document author so they can take a look at it accordingly

[greg-lindsay]

Thanks for the comment. I will address this with the product team. This is internal work item #240846 #please-close