Skip to content

Commit 6f02934

Browse files
fixing support issue
1 parent 88ff851 commit 6f02934

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

articles/site-recovery/hyper-v-azure-support-matrix.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,8 +128,8 @@ Block blobs | No | No
128128
Encryption at rest (SSE)| Yes | Yes
129129
Premium storage | Yes | Yes
130130
Import/export service | No | No
131-
Azure Storage firewalls for virtual networks configured on target storage/cache storage account (used to store replication data) | No | No
132-
Modifying storage account | No. The target Azure storage account can't be modified after enabling replication. To modify, disable and then reenabled disaster recovery. | No
131+
Azure storage accounts with firewall enabled | No | Yes. For target storage and cache.
132+
Modify storage account | No. The target Azure storage account can't be modified after enabling replication. To modify, disable and then reenable disaster recovery. | No
133133

134134

135135
## Azure compute features

articles/site-recovery/site-recovery-whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -67,7 +67,7 @@ Features added this month are summarized in the table.
6767

6868
**Feature** | **Details**
6969
--- | ---
70-
Storage account | Site Recovery now supports the use of a storage account with role-based access control (RBAC) enabled. [Learn more](../storage/common/storage-account-manage.md#access-control) about access control for storage accounts.
70+
Storage account | Site Recovery now supports the use of storage accounts with firewall enabled for Hyper-V to Azure disaster recovery. You can select firewall-enabled storage accounts as a target account, or for cache storage. If you use firewall-enabled account, make sure that you enable the option to allow trusted Microsoft services.
7171

7272

7373
## Updates (August 2019)

0 commit comments

Comments
 (0)