|
2 | 2 | title: Turn off Key-based access on cache accounts. |
3 | 3 | description: Learn how to turn off Key-based access on cache accounts. |
4 | 4 | services: site-recovery |
5 | | -author: swbela |
| 5 | +author: swapnilbel |
6 | 6 | ms.service: azure-site-recovery |
7 | 7 | ms.topic: concept-article |
8 | 8 | ms.date: 10/09/2025 |
9 | | -ms.author: swbela_microsoft |
| 9 | +ms.author: swbela |
10 | 10 |
|
11 | 11 | # Customer intent: Turn off key-based authentication on cache account used by Azure Site Recovery. |
12 | 12 | --- |
13 | 13 |
|
14 | 14 | # Turn off key based access on cache account |
15 | | -Previously, key-based access was required for cache storage accounts used by Azure Site Recovery (ASR). ASR now supports cache accounts with key-based authentication disabled. This article explains how to turn off key-based access without disrupting replication. |
| 15 | +Previously, key-based access was required for cache storage accounts used by Azure Site Recovery. Azure Site Recovery now supports cache accounts with key-based authentication disabled. This article explains how to turn off key-based access without disrupting replication. |
16 | 16 |
|
17 | 17 | ## Prerequisites |
18 | 18 | Before proceeding, ensure the following: |
19 | | -* [Enable Managed Identity on the Recovery Services Vault](https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints#enable-the-managed-identity-for-the-vault) |
| 19 | +* [Enable Managed Identity on the Recovery Services Vault](https://learn.microsoft.com/azure/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints#enable-the-managed-identity-for-the-vault) |
20 | 20 |
|
21 | | -* [Grant access to Recovery services vault managed identity to read-write to cache account](https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints#grant-required-permissions-to-the-vault) |
| 21 | +* [Grant access to Recovery services vault managed identity to read-write to cache account](https://learn.microsoft.com/azure/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints#grant-required-permissions-to-the-vault) |
22 | 22 |
|
23 | 23 | ## Turn off key-based access on storage accounts |
24 | 24 | For higher security of Azure storage, we recommend you to turn off of key-based authentication. |
25 | 25 |
|
26 | 26 | ### Scenario 1 |
27 | | -If the Recovery Services Vault already has a managed identity enabled, follow the steps in the [Related Content](#Related-content). |
| 27 | +If the Recovery Services Vault already has a managed identity enabled, follow the steps in the [Related Content](#related-content). |
28 | 28 |
|
29 | 29 | ### Scenario 2 |
30 | | -If the vault lacked a managed identity when VMs were initially protected, you can add it afterward. Once prerequisites are met, you can safely disable key-based access on the cache account. |
| 30 | +If the vault lacked a managed identity when virtual machines were initially protected, you can add it afterward. Once prerequisites are met, you can safely disable key-based access on the cache account. |
31 | 31 |
|
32 | 32 |
|
33 | 33 | > [!NOTE] |
34 | | -> Replication will continue without interruption if prerequisites are completed before disabling key-based access. Do not disable and re-enable protection for existing VMs or servers after completing prerequisites. |
| 34 | +> Replication continues without interruption if prerequisites are completed before disabling key-based access. Don't disable and re-enable protection for existing VMs or servers after completing prerequisites. |
35 | 35 |
|
36 | 36 | ## Related content |
37 | | -- [Disable shared key authorization on cache accounts](https://learn.microsoft.com/en-us/azure/storage/common/shared-key-authorization-prevent?tabs=portal#disable-shared-key-authorization) |
| 37 | +- [Disable shared key authorization on cache accounts](https://learn.microsoft.com/azure/storage/common/shared-key-authorization-prevent?tabs=portal#disable-shared-key-authorization) |
0 commit comments