Merge pull request #88617 from rayne-wiselman/rayneseptember16

fixing support issue

Author: PRMerger17

articles/migrate/best-practices-assessment.md

@@ -1,10 +1,10 @@
 ---
-title: Best practices for creating assessment with Azure Migrate Server Assessment | Microsoft Docs
+title: Best practices for creating assessment with Azure Migrate Server Assessment
 description: Provides tips for creating assessments with Azure Migrate Server Assessment.
 author: rayne-wiselman
 ms.service: azure-migrate
 ms.topic: conceptual
-ms.date: 07/15/2019
+ms.date: 09/16/2019
 ms.author: raynew
 ---
 
@@ -28,8 +28,8 @@ As an example, if you have an on-premises VM with four cores at 20% utilization,
 
 - **Performance-based assessment**:
     - Identifies effective cores and memory based on core (4 x 0.20 = 0.8), and memory (8 GB x 0.10 = 0.8) utilization.
-    - Applies the comfort factor specified in assessment properties (le'ts say 1.3x) to get the values to be used for sizing. 
-    - Recommends the nearest VM size in Azure that can support ~1.4 cores (0.8 x 1.3) and ~1.4 GB (0.8 x 1.3) memory.
+    - Applies the comfort factor specified in assessment properties (let's say 1.3x) to get the values to be used for sizing. 
+    - Recommends the nearest VM size in Azure that can support ~1.04 cores (0.8 x 1.3) and ~1.04 GB (0.8 x 1.3) memory.
 
 - **As-is (as on-premises) assessment**:
     -  Recommends a VM with four cores; 8 GB of memory.

articles/migrate/tutorial-prepare-hyper-v.md

@@ -5,7 +5,7 @@ author: rayne-wiselman
 manager: carmonm
 ms.service: azure-migrate
 ms.topic: tutorial
-ms.date: 07/24/2019
+ms.date: 09/16/2019
 ms.author: raynew
 ms.custom: mvc
 ---
@@ -124,7 +124,7 @@ Run the script as follows:
 
 1. Make sure you have PowerShell version 4.0 or later installed on the Hyper-V host.
 2. Download the script from the [Microsoft Download Center](https://aka.ms/migrate/script/hyperv). The script is cryptographically signed by Microsoft.
-3. Validate the script integrity using either MD5 or SHA256 hash files. Run this command to generate the hash for the script:
+3. Validate the script integrity using either MD5 or SHA256 hash files. Hashtag values are below. Run this command to generate the hash for the script:
     ```
     C:\>CertUtil -HashFile <file_location> [Hashing Algorithm]
     ```
@@ -133,19 +133,20 @@ Run the script as follows:
     C:\>CertUtil -HashFile C:\Users\Administrators\Desktop\ MicrosoftAzureMigrate-Hyper-V.ps1
     SHA256
     ```
-    
-    Hash values are:
-    Hash | Value
-    --- | ---
-    **MD5** | 0ef418f31915d01f896ac42a80dc414e
-    **SHA256** | 0ad60e7299925eff4d1ae9f1c7db485dc9316ef45b0964148a3c07c80761ade2
-
 
 4.	After validating the script integrity, run the script on each Hyper-V host with this PowerShell command:
     ```
     PS C:\Users\Administrators\Desktop> MicrosoftAzureMigrate-Hyper-V.ps1
     ```
 
+#### Hashtag values
+
+Hash values are:
+
+| **Hash** | **Value** |
+| --- | --- |
+| **MD5** | 0ef418f31915d01f896ac42a80dc414e |
+| **SHA256** | 0ad60e7299925eff4d1ae9f1c7db485dc9316ef45b0964148a3c07c80761ade2 |
 
 ### Verify Hyper-V host settings
 

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

@@ -128,8 +128,8 @@ Block blobs | No | No
 Encryption at rest (SSE)| Yes | Yes
 Premium storage | Yes | Yes
 Import/export service | No | No
-Azure Storage firewalls for virtual networks configured on target storage/cache storage account (used to store replication data) | No | No
-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
+Azure storage accounts with firewall enabled | No  | Yes. For target storage and cache.
+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
 
 
 ## Azure compute features

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

@@ -53,21 +53,21 @@ New features for Azure VM disaster recovery are summarized in the table.
 **Cleanup after failback** | After failing over to the secondary Azure, and then failing back to the primary region, Site Recovery automatically cleans up machines in the secondary region. There's no need to manually delete VMS and NICs.
 **Test failover retains IP address** | You can now retain the IP address of the source VM during a disaster recovery drill, and pick a static IP address for a test failover.
 
-## VMware/physical server disaster recovery
+### VMware/physical server disaster recovery
 
 Features added this month are summarized in the table.
 
 **Feature** | **Details**
 --- | ---
 New process server alerts | We've added new process server alerts. [Learn more](vmware-physical-azure-monitor-process-server.md). 
 
-## Hyper-V disaster recovery
+### Hyper-V disaster recovery
 
 Features added this month are summarized in the table.
 
 **Feature** | **Details**
 --- | ---
-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. 
+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.
 
 
 ## Updates (August 2019)