Merge pull request #206743 from flang-msft/fxl---Redis-version-4-retirement-announcement-14956957

fxl - what's new proposal for Redis 6 default change in November

Author: v-ccolin

articles/azure-cache-for-redis/TOC.yml

@@ -248,6 +248,8 @@
   items:
   - name: Azure Cache for Redis FAQs
     href: cache-faq.yml
+  - name: Retirements from Azure Cache for Redis
+    href: cache-retired-features.md
   - name: Videos
     href: https://www.youtube.com/results?search_query=azure+redis+cache
   - name: Microsoft Q&A question page

articles/azure-cache-for-redis/cache-faq.yml

@@ -7,8 +7,8 @@ metadata:
   ms.author: franlanglois
   ms.service: cache
   ms.topic: faq
-  ms.date: 09/08/2022
-  
+  ms.date: 09/29/2022
+
 title: Azure Cache for Redis FAQ
 summary: |
   Learn the answers to common questions, patterns, and best practices for Azure Cache for Redis.

articles/azure-cache-for-redis/cache-retired-features.md

@@ -0,0 +1,56 @@
+---
+title: What's been retired from Azure Cache for Redis?
+titleSuffix: Azure Cache for Redis
+description: Information on retirements from Azure Cache for Redis
+author: flang-msft
+
+ms.author: franlanglois
+ms.service: cache
+ms.topic: conceptual
+ms.date: 09/29/2022
+
+---
+
+# Retirements
+
+## Redis version 4
+
+On June 30, 2023, we'll retire version 4 for Azure Cache for Redis instances. Before that date, you need to upgrade any of your cache instances to version 6.
+
+- All cache instances running Redis version 4 after June 30, 2023 will be upgraded automatically.
+- All cache instances running Redis version 4 that have geo-replication enabled will be upgraded automatically after August 30, 2023.
+
+We recommend that you upgrade your caches on your own to accommodate your schedule and the needs of your users to make the upgrade as convenient as possible.
+
+The open-source Redis version 4 was released several years ago and is now retired. Version 4 no longer receives critical bug or security fixes from the community. Azure Cache for Redis offers open-source Redis as a managed service on Azure. To stay in sync with the open-source offering, we'll also retire version 4.
+<!-- Can we be more specific about when open-source Redis 4 was retired -->
+
+Microsoft continues to backport security fixes from recent versions to version 4 until retirement. We encourage you to upgrade your cache to version 6 sooner, so you can use the rich feature set that Redis version 6 has to offer. For more information, See the Redis 6 GA announcement for more details.
+
+To upgrade your version 4 Azure Cache for Redis instance, see our [Upgrade an existing Redis 4 cache to Redis 6](cache-how-to-version.md#upgrade-an-existing-redis-4-cache-to-redis-6. If your cache instances have geo-replication enabled, you’re required to unlink the caches before upgrade.
+
+### Important upgrade timelines
+
+From now through 30 June 2023, you can continue to use existing Azure Cache for Redis version 4 instances. Retirement will occur in following stages, so you have the maximum amount of time to upgrade.
+
+| Date    | Description |
+|-------- |-------------|
+| November 1. 2022 | Beginning November 1, 2022, all the versions of Azure Cache for Redis REST API, PowerShell, Azure CLI, and Azure SDK will create Redis instances using Redis version 6 by default. If you need a specific Redis version for your cache instance, see [Redis 6 becomes default for new cache instances](cache-whats-new.md#redis-6-becomes-default-for-new-cache-instances). |
+| March 1, 2023 | Beginning March 1, 2023, you won't be able to create new Azure Cache for Redis instances using Redis version 4. Also, you won’t be able to create new geo-replication links between cache instances using Redis version 4.|
+| June 30, 2023 | After June 30 2023, any remaining version 4 cache instances, which don't have geo-replication links, will be automatically upgraded to version 6.|
+| August 30, 2023 |After August 30, 2023, any remaining version 4 cache instances, which have geo-replication links, will be automatically upgraded to version 6. This upgrade operation will require unlinking and relinking the caches and customers could experience geo-replication link down time. |
+
+### Version 4 caches on cloud services
+
+If your cache instance is affected by the Cloud Service retirement, you're unable to upgrade to Redis 6 until after you migrate to a cache built on virtual machine scale set. In this case, send mail to [email protected], and we'll help you with the migration.
+
+For more information on what to do if your cache is on Cloud Services (classic), see [Azure Cache for Redis on Cloud Services (classic)](cache-faq.yml#what-should-i-do-with-any-instances-of-azure-cache-for-redis-that-depend-on-cloud-services--classic-).
+
+### How to check if a cache is running on version 4?
+
+You check the Redis version of your cache instance by selecting **Properties** from the resource menu in the Azure Cache for Redis portal.
+
+## Next steps
+<!-- Add a context sentence for the following links -->
+- [What's new](cache-whats-new.md)
+- [Azure Cache for Redis FAQ](cache-faq.yml)

articles/azure-cache-for-redis/cache-whats-new.md

@@ -5,15 +5,26 @@ author: flang-msft
 
 ms.author: franlanglois
 ms.service: cache
-ms.topic: reference
-ms.date: 09/01/2022
+ms.topic: conceptual
+ms.date: 09/29/2022
 
 ---
 
 # What's New in Azure Cache for Redis
 
 ## September 2022
 
+### Upgrade your Azure Cache for Redis instances to use Redis version 6 by June 30, 2023
+
+On June 30, 2023, we'll retire version 4 for Azure Cache for Redis instances. Before that date, you need to upgrade any of your cache instances to version 6.
+
+- All cache instances running Redis version 4 after June 30, 2023 will be upgraded automatically.
+- All cache instances running Redis version 4 that have geo-replication enabled will be upgraded automatically after August 30, 2023.
+
+We recommend that you upgrade your caches on your own to accommodate your schedule and the needs of your users to make the upgrade as convenient as possible.
+
+For more information, see [Retirements](cache-retired-features.md).
+
 ### Support for managed identity in Azure Cache for Redis
 
 Authenticating storage account connections using managed identity has now reached General Availability (GA).
@@ -79,15 +90,15 @@ The default version of Redis that is used when creating a cache can change over
 
 As of May 2022, Azure Cache for Redis rolls over to TLS certificates issued by DigiCert Global G2 CA Root. The current Baltimore CyberTrust Root expires in May 2025, requiring this change.
 
-We expect that most Azure Cache for Redis customers won't be affected. However, your application might be affected if you explicitly specify a list of acceptable certificate authorities (CAs), known as *certificate pinning*.
+We expect that most Azure Cache for Redis customers won't be affected. However, your application might be affected if you explicitly specify a list of acceptable certificate authorities (CAs), known as _certificate pinning_.
 
 For more information, read this blog that contains instructions on [how to check whether your client application is affected](https://techcommunity.microsoft.com/t5/azure-developer-community-blog/azure-cache-for-redis-tls-upcoming-migration-to-digicert-global/ba-p/3171086). We recommend taking the actions recommended in the blog to avoid cache connectivity loss.
 
 ### Active geo-replication for Azure Cache For Redis Enterprise GA
 
 Active geo-replication for Azure Cache for Redis Enterprise is now generally available (GA).
 
-Active geo-replication is a powerful tool that enables Azure Cache for Redis clusters to be linked together for seamless active-active replication of data. Your applications can write to one Redis cluster and your data is automatically copied to the other linked clusters, and vice versa. For more information, see this [post](https://aka.ms/ActiveGeoGA) in the *Azure Developer Community Blog*.
+Active geo-replication is a powerful tool that enables Azure Cache for Redis clusters to be linked together for seamless active-active replication of data. Your applications can write to one Redis cluster and your data is automatically copied to the other linked clusters, and vice versa. For more information, see this [post](https://aka.ms/ActiveGeoGA) in the _Azure Developer Community Blog_.
 
 ## January 2022