Updates and image edits

Author: v-sreedevank

articles/migrate/how-to-create-azure-vmware-solution-assessment.md

@@ -144,7 +144,7 @@ You can select  **Sizing assumptions** to understand the assumptions that went i
 
 1. In **Azure readiness**, verify whether servers are ready for migration to AVS.
 
-2. Review the server status:
+2. [Review](concepts-azure-vmware-solution-assessment-calculation.md#server-properties) the server status:
     - **Ready for AVS**: The server can be migrated as-is to Azure (AVS) without any changes. It starts in AVS with full AVS support.
     - **Ready with conditions**: There might be some compatibility issues, for example, internet protocol or deprecated OS in VMware and need to be remediated before migrating to Azure VMware Solution. To fix any readiness problems, follow the remediation guidance the assessment suggests.
     - **Not ready for AVS**: The VM won't start in AVS. For example, if the on-premises VMware VM has an external device attached such as a cd-rom the VMware vMotion operation fails (if using VMware vMotion).

articles/migrate/how-to-view-a-business-case.md

@@ -151,19 +151,24 @@ It covers cost components for on-premises and AVS, savings, and insights to unde
 #### [AVS (Azure VMware Solution)](#tab/avs-azure)
 
 This section contains the cost estimate by recommended target (Annual cost includes Compute, Storage, Network, labor components) and savings from Hybrid benefits.
-- AVS cost estimate:
-  **Estimated AVS cost**:  This card includes the total cost of ownership for hosting all workloads on AVS including the AVS nodes cost (which includes storage cost), networking, and labor cost. The node cost is computed by taking the most cost optimum AVS node SKU. The infrastructure settings used are as follows:
-    - The number and SKU of AVS hosts used in a business case aligns to the SKUs available in the given region and optimized to use the least number of nodes required to host all VMs ready to be migrated.
-    - Azure NetApp File (ANF) is used when it can be used to optimize the number of AVS hosts required. ANF Standard tier is used when the VMs have been imported using RVTools. For an Azure Migrate appliance-based business case, the tier of ANF used in the business case depends on the IOPS & throughput data for VMs. 
+
+#### AVS cost estimate
+
+**Estimated AVS cost**:  This card includes the total cost of ownership for hosting all workloads on AVS including the AVS nodes cost (which includes storage cost), networking, and labor cost. The node cost is computed by taking the most cost optimum AVS node SKU. The infrastructure settings used are as follows:
+    
+- The number and SKU of AVS hosts used in a business case aligns to the SKUs available in the given region and optimized to use the least number of nodes required to host all VMs ready to be migrated.
+- Azure NetApp File (ANF) is used when it can be used to optimize the number of AVS hosts required. ANF Standard tier is used when the VMs have been imported using RVTools. For an Azure Migrate appliance-based business case, the tier of ANF used in the business case depends on the IOPS & throughput data for VMs. 
     - CPU over-subscription of 4:1
     - Memory overcommit of 100% 
-    - Compression and deduplication factor of 1.5 
+    - Compression and deduplication factor of 1.5. You can learn more about this [here](concepts-azure-vmware-solution-assessment-calculation.md#whats-in-an-azure-vmware-solution-assessment). 
+
+**Compute and license cost**: This card shows the comparison of compute and license cost when using Azure hybrid benefit and without Azure hybrid benefit. 
+
+#### Savings and optimization:
+    
+**Savings with 3-year RI**: This card shows the node cost with 3-year RI.
 
-You can learn more about this [here](concepts-azure-vmware-solution-assessment-calculation.md#whats-in-an-azure-vmware-solution-assessment). 
-    - **Compute and license cost**: This card shows the comparison of compute and license cost when using Azure hybrid benefit and without Azure hybrid benefit. 
-- Savings and optimization:
-    - **Savings with 3-year RI**: This card shows the node cost with 3-year RI.
-    - **Savings with Azure Hybrid Benefit & Extended Security Updates**: This card displays the estimated maximum savings when using Azure hybrid benefit and with extended security updates over a period of one year.
+**Savings with Azure Hybrid Benefit & Extended Security Updates**: This card displays the estimated maximum savings when using Azure hybrid benefit and with extended security updates over a period of one year.
 
 :::image type="content" source="./media/how-to-view-a-business-case/avs-estimation-inline.png" alt-text="Screenshot of AVS estimation." lightbox="./media/how-to-view-a-business-case/avs-estimation-expanded.png":::
 
@@ -179,14 +184,14 @@ You can learn more about this [here](concepts-azure-vmware-solution-assessment-c
 ## On-premises with Azure Arc report 
 This section contains the cost and savings estimate by Arc-enabling your on-premises estate: 
 
-- Arc cost estimate
+#### Arc cost estimate
    - **Compute and license cost**: Estimated as a sum of total server hardware acquisition cost on-premises, software cost (Windows license, SQL license, Virtualization software cost), and maintenance cost, SQL license cost is assumed to be using pay-as-you-go model via Arc-enabled SQL Server. ESU licenses for Windows Server and SQL Server are also assumed to be paid via Azure through ESUs enabled by Azure Arc.
    - **Security and Management Cost**: Security cost is estimated as sum of total protection cost for general servers and SQL workloads using MDC via Azure Arc and management cost is estimated as sum of total management cost  for general servers.
    - **Storage, Network and facilities cost** : Storage cost is Cost per GB and can be customized in the assumptions. Network and facilities cost is considered same as that of current on-premises costs.
-- Arc savings
+#### Arc savings
    - **Estimated ESU savings**: This report includes the savings by paying ESUs monthly instead of annual licensing and deploying them seamlessly to your on-premises servers.
    - **IT Productivity Savings**: Azure Arc improves IT productivity by reducing the time they spend on routine activities. This report includes that and management savings.
-   - **Threat protection and Savings by using MDC**: The report also includes  the savings by using Microsoft Defender for Cloud to secure your on-premises server. You can mitigate threats 50% faster and improve your security posture with Microsoft Defender for cloud.
+   - **Threat protection and Savings using MDC**: The report also includes  the savings by using Microsoft Defender for Cloud to secure your on-premises server. You can mitigate threats 50% faster and improve your security posture with Microsoft Defender for cloud.
 
 :::image type="content" source="./media/how-to-view-a-business-case/azure-arc-inline.png" alt-text="Screenshot of comparison of on-premises servers with Arc and without Arc." lightbox="./media/how-to-view-a-business-case/azure-arc-expanded.png":::
 

articles/migrate/media/how-to-view-a-business-case/azure-arc-expanded.png

@@ -70,9 +70,9 @@ Run an assessment as follows:
    **Section** | **Setting** | **Details**
    | --- | --- | ---
    Target settings | **Target location** | The Azure region to which you want to migrate. Size and cost recommendations are based on the location that you specify.
-   Target settings | **Storage type** | Defaulted to **vSAN**. This is the default storage type for an AVS private cloud.
+   Target settings | **Storage type** | Defaulted to vSAN & ANF - Standard, ANF - Premium, and ANF - Ultra tiers. ANF will be used when external storage can reduce the cost by reducing the number of nodes required. ANF - Standard will be used by default when IOPS/throughput for storage is not provided. 
    Target settings | **Reserved instance** | Specify whether you want to use reserve instances for Azure VMware Solution nodes when you migrate your VMs. If you decide to use a reserved instance, you can't specify **Discount (%)**. [Learn more](/azure/azure-vmware/reserved-instance) about reserved instances.
-   VM size | **Node type** | Defaulted to **AV36**. Azure Migrate recommends the node needed to migrate the servers to AVS.
+   VM size | **Node type** | Defaulted to use all the nodes available in a given region.
    VM size | **FTT setting, RAID level** | Select the Failure to Tolerate and RAID combination. The selected FTT option, combined with the on-premises server disk requirement, determines the total vSAN storage required in AVS.
    VM size | **CPU Oversubscription** | Specify the ratio of virtual cores associated with one physical core in the AVS node. Oversubscription of greater than 4:1 might cause performance degradation, but can be used for web server type workloads.
    VM size | **Memory overcommit factor** | Specify the ratio of memory over commit on the cluster. A value of 1 represents 100% memory use, 0.5, for example, is 50%, and 2 would be using 200% of available memory. You can only add values from 0.5 to 10 up to one decimal place.

articles/migrate/media/how-to-view-a-business-case/azure-arc-inline.png

@@ -16,7 +16,7 @@ ms.custom: mvc, engagement-fy24
 
 ## Update (November 2024)
 
-- AVS assessments and Business case now support cost assessments with AV64 SKU and Azure NetApp Files (ANF) as an external storage option. [Learn more](how-to-create-azure-vmware-solution-assessment.md).
+- AVS assessments now support cost assessments with AV64 SKU and Azure NetApp Files (ANF) as an external storage option. [Learn more](how-to-create-azure-vmware-solution-assessment.md).
 - Support for cost of SKUs when porting on-premises VCF subscription to AVS.
 
 ## Update (October 2024)