You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-whats-new.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: flang-msft
6
6
ms.author: franlanglois
7
7
ms.service: cache
8
8
ms.topic: conceptual
9
-
ms.date: 02/06/2023
9
+
ms.date: 03/28/2023
10
10
11
11
---
12
12
@@ -28,19 +28,19 @@ For more information, see [Configure active geo-replication](cache-how-to-active
28
28
29
29
### Flush operation for active geo-replicated caches (preview)
30
30
31
-
Caches using active geo-replication now include a built-in Flush operation that can be initiated at the control plane level. Use the Flush operation with your cache instead of `FLUSH ALL` and `FLUSH DB` operations, which are blocked by design for active geo-replicated caches.
31
+
Caches using active geo-replication now include a built-in _flush_ operation that can be initiated at the control plane level. Use the _flush_ operation with your cache instead of the`FLUSH ALL` and `FLUSH DB` operations, which are blocked by design for active geo-replicated caches.
32
32
33
-
For more information see [Flush operation](cache-how-to-active-geo-replication.md#flush-operation)
33
+
For more information, see [Flush operation](cache-how-to-active-geo-replication.md#flush-operation)
34
34
35
35
### Customer managed key (CMK) disk encryption (preview)
36
36
37
-
Redis data that is saved on disk can now be encrypted using customer managed keys (CMK) in the Enterprise and Enterprise Flash tiers. This adds an additional layer of control to the default disk encryption.
37
+
Redis data that is saved on disk can now be encrypted using customer managed keys (CMK) in the Enterprise and Enterprise Flash tiers. Using CMK adds another layer of control to the default disk encryption.
38
38
39
39
For more information, see [Enable disk encryption](cache-how-to-encryption.md)
40
40
41
41
### Connection event audit logs (preview)
42
42
43
-
Enterprise and Enterprise Flash tier caches can now log all connection, disconnection, and authentication events through diagnostic settings. This is helpful for security audits and for monitoring who has access to your cache resource.
43
+
Enterprise and Enterprise Flash tier caches can now log all connection, disconnection, and authentication events through diagnostic settings. Logging this information helps in security audits. You can also monitor who has access to your cache resource.
44
44
45
45
For more information, see [Enabling connection audit logs](cache-monitor-diagnostic-settings.md)
46
46
@@ -118,7 +118,7 @@ Beginning January 20, 2023, all versions of Azure Cache for Redis REST API, Powe
118
118
>
119
119
> The default Redis version that is used when creating a cache instance can vary because it is based on the latest stable version offered in Azure Cache for Redis.
120
120
121
-
If you need a specific version of Redis for your application, we recommend using latest artifact versions as shown in the table below. Then, choose the Redis version explicitly when you create the cache.
121
+
If you need a specific version of Redis for your application, we recommend using latest artifact versions as shown in the table. Then, choose the Redis version explicitly when you create the cache.
122
122
123
123
| Artifact | Version that supports specifying Redis version |
124
124
|---------|---------|
@@ -156,7 +156,7 @@ The default version of Redis that is used when creating a cache can change over
156
156
157
157
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.
158
158
159
-
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_.
159
+
We expect that most Azure Cache for Redis customers aren't affected. However, your application might be affected if you explicitly specify a list of acceptable certificate authorities (CAs), known as _certificate pinning_.
160
160
161
161
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.
0 commit comments