Skip to content

Commit 01060be

Browse files
committed
refined text
1 parent 5e520d3 commit 01060be

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

articles/azure-cache-for-redis/includes/cache-entra-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
ms.date: 08/16/2024
2+
ms.date: 12/17/2024
33

44
ms.topic: include
55
ms.custom:

articles/azure-cache-for-redis/includes/managed-redis-create.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
ms.date: 08/16/2024
2+
ms.date: 12/17/2024
33

44
ms.topic: include
55
ms.custom:
@@ -25,12 +25,12 @@ ms.custom:
2525
1. Select **Next: Networking** and select either a public or private endpoint.
2626

2727
1. Select **Next: Advanced**.
28-
29-
Configure any [Redis modules](../managed-redis/managed-redis-redis-modules.md) you wan to be add to the instance.
3028

31-
By default, for a new managed cache:
32-
- ** Access Keys Authentication** is disabled for security reasons.
29+
Configure any [Redis modules](../managed-redis/managed-redis-redis-modules.md) you wan to add to the instance.
30+
31+
By default, for a new managed cache:
3332
- Microsoft Entra ID is enabled.
33+
- - **Access Keys Authentication** is disabled for security reasons.
3434

3535
> [!IMPORTANT]
3636
> For optimal security, we recommend that you use Microsoft Entra ID with managed identities to authorize requests against your cache if possible. Authorization by using Microsoft Entra ID and managed identities provides superior security and ease of use over shared access key authorization. For more information about using managed identities with your cache, see [Use Microsoft Entra ID for cache authentication](/azure/azure-cache-for-redis/cache-azure-active-directory-for-authentication).
@@ -39,7 +39,7 @@ ms.custom:
3939

4040
:::image type="content" source="media/managed-redis-create/managed-redis-advanced-settings.png" alt-text="Screenshot that shows the Azure Managed Redis Advanced tab.":::
4141

42-
If you're using **Active geo-replication**, it must be configured during creation. For instructions on how do to this, see [Configure active geo-replication for Azure Managed Redis instances](../managed-redis/managed-redis-how-to-active-geo-replication.md).
42+
If you're using **Active geo-replication**, it must be configured during creation. For more information, see [Configure active geo-replication for Azure Managed Redis instances](../managed-redis/managed-redis-how-to-active-geo-replication.md).
4343

4444
> [!IMPORTANT]
4545
> You can't change the clustering policy of an Azure Managed Redis (preview) instance after you create it. If you're using [RediSearch](../managed-redis/managed-redis-redis-modules.md#redisearch), the Enterprise cluster policy is required, and `NoEviction` is the only eviction policy supported.

0 commit comments

Comments
 (0)