Skip to content

Commit db1316d

Browse files
authored
internalEncryption
1 parent 0b9aac9 commit db1316d

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

articles/app-service/environment/app-service-app-service-environment-custom-settings.md

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: stefsch
55

66
ms.assetid: 1d1d85f3-6cc6-4d57-ae1a-5b37c642d812
77
ms.topic: tutorial
8-
ms.date: 01/16/2018
8+
ms.date: 12/19/2019
99
ms.author: stefsch
1010
ms.custom: mvc
1111
ms.custom: seodec18
@@ -53,6 +53,19 @@ Alternatively, you can update the App Service Environment by using [Azure Resour
5353
However you submit the change, it takes roughly 30 minutes multiplied by the number of front ends in the App Service Environment for the change to take effect.
5454
For example, if an App Service Environment has four front ends, it will take roughly two hours for the configuration update to finish. While the configuration change is being rolled out, no other scaling operations or configuration change operations can take place in the App Service Environment.
5555

56+
## Enable Internal Encryption
57+
58+
The App Service Environment operates as a black box system where you cannot see the internal components or the communication within the system. To enable higher throughput, encryption is not enabled by default between internal components. The system is secure as the traffic is completely inaccessible to being monitored or accessed. If you have a compliance requirement though that requires complete encryption of the data path from end to end, there is a way to enable this with a clusterSetting.
59+
60+
"clusterSettings": [
61+
{
62+
"name": "InternalEncryption",
63+
"value": "1"
64+
}
65+
],
66+
67+
After the InternalEncryption clusterSetting is enabled, there can be an impact to your system performance. When you make the change to enable InternalEncryption, your ASE will be in an unstable state until the change is fully propagated. Complete propagation of the change can take as long as a maintenance upgrade of your ASE.
68+
5669
## Disable TLS 1.0 and TLS 1.1
5770

5871
If you want to manage TLS settings on an app by app basis, then you can use the guidance provided with the [Enforce TLS settings](../configure-ssl-bindings.md#enforce-tls-versions) documentation.

0 commit comments

Comments
 (0)