Merge pull request #101539 from JonCole/master

Redis TLS retirement - add dates for national clouds

Author: PRMerger10

articles/azure-cache-for-redis/cache-remove-tls-10-11.md

@@ -16,8 +16,8 @@ There's an industry-wide push toward the exclusive use of Transport Layer Securi
 
 As a part of this effort, we'll be making the following changes to Azure Cache for Redis:
 
-* Starting on January 13, 2020 we will configure the default minimum TLS version to be 1.2 for newly created cache instances.  Existing cache instances won't be updated at this point.  You'll be allowed to [change the minimum TLS version](cache-configure.md#access-ports) back to 1.0 or 1.1 for backward compatibility, if needed.  This change can be done through the Azure portal or other management APIs.
-* Starting on March 31, 2020 we'll stop supporting TLS versions 1.0 and 1.1. After this change, your application will be required to use TLS 1.2 or later to communicate with your cache.
+* **Phase 1:** We'll configure the default minimum TLS version to be 1.2 for newly created cache instances.  Existing cache instances won't be updated at this point.  You'll be allowed to [change the minimum TLS version](cache-configure.md#access-ports) back to 1.0 or 1.1 for backward compatibility, if needed.  This change can be done through the Azure portal or other management APIs.
+* **Phase 2:** We'll stop supporting TLS versions 1.0 and 1.1. After this change, your application will be required to use TLS 1.2 or later to communicate with your cache.
 
 Additionally, as a part of this change, we'll be removing support for older, insecure cypher suites.  Our supported cypher suites will be restricted to the following when the cache is configured with a minimum TLS version of 1.2.
 
@@ -26,6 +26,15 @@ Additionally, as a part of this change, we'll be removing support for older, ins
 
 This article provides general guidance about how to detect dependencies on these earlier TLS versions and remove them from your application.
 
+The dates when these changes take effect are:
+
+| Cloud               | Phase 1 Start Date | Phase 2 Start Date |
+|---------------------|--------------------|--------------------|
+| Azure (global)      |  January 13, 2020  | March 31, 2020     |
+| Azure Government    |  March 13, 2020    | May 11, 2020       |
+| Azure Germany       |  March 13, 2020    | May 11, 2020       |
+| Azure China         |  March 13, 2020    | May 11, 2020       |
+
 ## Check whether your application is already compliant
 
 The easiest way to find out whether your application will work with TLS 1.2 is to set the **Minimum TLS version** value to TLS 1.2 on a test or staging cache that it uses. The **Minimum TLS version** setting is in the [Advanced settings](cache-configure.md#advanced-settings) of your cache instance in the Azure portal. If the application continues to function as expected after this change, it's probably compliant. You might need to configure some Redis client libraries used by your application specifically to enable TLS 1.2, so they can connect to Azure Cache for Redis over that security protocol.