MDC updates

Author: Karthigasree

articles/migrate/concepts-assessment-calculation.md

@@ -6,7 +6,7 @@ ms.author: rajosh
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: conceptual
-ms.date: 11/24/2022
+ms.date: 08/02/2023
 ms.custom: engagement-fy23
 ---
 
@@ -109,7 +109,7 @@ Calculations occur in these three stages:
 
 1. **Calculate Azure readiness**: Assess whether servers are suitable for migration to Azure.
 1. **Calculate sizing recommendations**: Estimate compute, storage, and network sizing.
-1. **Calculate monthly costs**: Calculate the estimated monthly compute and storage costs for running the servers in Azure after migration.
+1. **Calculate monthly costs**: Calculate the estimated monthly compute, storage, and security costs for running the servers in Azure after migration.
 
 Calculations are in the preceding order. A server moves to a later stage only if it passes the previous one. For example, if a server fails the Azure readiness stage, it's marked as unsuitable for Azure. Sizing and cost calculations aren't done for that server.
 
@@ -134,6 +134,7 @@ Here's what's included in an Azure VM assessment:
 **VM uptime** | The duration in days per month and hours per day for Azure VMs that won't run continuously. Cost estimates are based on that duration.<br><br> The default values are 31 days per month and 24 hours per day.
 **Azure Hybrid Benefit** | Specifies whether you have software assurance and are eligible for [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-use-benefit/). If the setting has the default value "Yes," Azure prices for operating systems other than Windows are considered for Windows VMs.
 **EA subscription** | Specifies that an Enterprise Agreement (EA) subscription is used for cost estimation. Takes into account the discount applicable to the subscription. <br><br> Leave the settings for reserved instances, discount (%) and VM uptime properties with their default settings.
+**Security** | Specifies whether you want to assess readiness and cost for security tooling on Azure. If the setting has the default value **Yes, with Microsoft Defender for Cloud**, it will assess security readiness and costs for your Azure VM with Microsoft Defender for Cloud.   
 
 
 [Review the best practices](best-practices-assessment.md) for creating an assessment with Azure Migrate.
@@ -188,6 +189,24 @@ Other operating systems like Oracle Solaris, Apple macOS, and FreeBSD | Azure do
 OS specified as **Other** in vCenter Server | Azure Migrate can't identify the OS in this case. | Unknown readiness. Ensure that Azure supports the OS running inside the VM.
 32-bit operating systems | The server might start in Azure, but Azure might not provide full support. | Conditionally ready for Azure. Consider upgrading to a 64-bit OS before migrating to Azure.
 
+### Security Readiness
+Assessments also determine readiness of the recommended target for Microsoft Defender for Servers. A server is marked as Ready for Microsoft Defender for Servers if it satisfies the following conditions:
+- Minimum 2 vCores (4 vCores preferred)
+- Minimum 1 GB RAM (4 GB preferred)
+- 2 GB of disk space
+- Runs any of the following Operating Systems:
+   - Windows Server – 2008 R2, 2012 R2, 2016, 2019, 2022
+   - Red Hat Enterprise Linux Server – 7.2+, 8+, 9+
+   - Ubuntu – 16.04, 18.04, 20.04, 22.04
+   - SUSE Linux Enterprise Server – 12, 15+
+   - Debian – 9, 10, 11
+   - Oracle Linux – 7.2+, 8
+   - CentOS Linux – 7.2+
+   - Amazon Linux – 2
+- For other operating systems, it is marked as **Ready with Conditions**.
+If a server is not ready to be migrated to Azure, it is marked as **Not Ready for Microsoft Defender for Servers**.
+
+
 ## Calculating sizing
 
 After the server is marked as ready for Azure, the assessment makes sizing recommendations in the Azure VM assessment. These recommendations identify the Azure VM and disk SKU. Sizing calculations depend on whether you're using as-is on-premises sizing or performance-based sizing.