Changes

Author: Karthigasree

articles/migrate/concepts-assessment-calculation.md

@@ -195,14 +195,14 @@ Assessments also determine readiness of the recommended target for Microsoft Def
 - 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
+   - 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**.
 
@@ -356,6 +356,9 @@ Cost is calculated using the following logic:
 
 Assessment calculates the total monthly storage costs by aggregating the storage costs of all servers. Currently, the calculation doesn't consider offers specified in the assessment settings.
 
+### Security Cost
+For servers recommended for Azure VM, if they're ready to run Defender for Server, the Defender for Server cost (Plan 2) per server for that region is added. The assessment aggregates the cost across all servers to calculate the total monthly security cost.
+
 Costs are displayed in the currency specified in the assessment settings.
 
 ## Next steps

articles/migrate/concepts-azure-sql-assessment-calculation.md

@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.service: azure-migrate
 ms.topic: conceptual
-ms.date: 03/15/2023
+ms.date: 08/02/2023
 ms.custom: engagement-fy23
 ---
 
@@ -100,6 +100,7 @@ High availability and disaster recovery properties | **Disaster recovery region*
 High availability and disaster recovery properties | **Multi-subnet intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you want asynchronous data replication where some replication delays are tolerable. This allows higher durability using geo-redundancy. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you desire the data replication to be synchronous and no data loss due to replication delay is allowable. This setting allows assessment to leverage built-in high availability options in Azure SQL Databases and Azure SQL Managed Instances, and availability zones and zone-redundancy in Azure Virtual Machines to provide higher availability. In the event of failover, no data is lost.  
 High availability and disaster recovery properties | **Internet Access** | Defaulted to Available.<br/><br/> Select **Available** if you allow outbound Internet access from Azure VMs. This allows the use of [Cloud Witness](https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/hadr-cluster-quorum-configure-how-to?view=azuresql&tabs=powershell) which is the recommended approach for Windows Server Failover Clusters in Azure Virtual Machines. <br/><br/> Select **Not available** if the Azure VMs have no outbound Internet access. This requires the use of a Shared Disk as a witness for Windows Server Failover Clusters in Azure Virtual Machines. 
 High availability and disaster recovery properties | **Async commit mode intent** | Defaulted to Disaster recovery. <br/><br/> Select **Disaster recovery** if you're using asynchronous commit availability mode to enable higher durability for the data without affecting performance. In the event of failover, data that hasn't yet been replicated may be lost. <br/><br/> Select **High availability** if you're using asynchronous commit data availability mode to improve availability and scale out read traffic. This setting allows assessment to leverage built-in high availability features in Azure SQL Databases, Azure SQL Managed Instances, and Azure Virtual Machines to provide higher availability and scale out.  
+Security | **Security** | Defaulted to Yes, with Microsoft Defender for Cloud. <br/><br/> 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 SQL MI/DB with Microsoft Defender for Cloud.   
 
 [Review the best practices](best-practices-assessment.md) for creating an assessment with Azure Migrate.
 
@@ -138,6 +139,14 @@ If you select the target deployment type as **Recommended** in the Azure SQL ass
 > [!NOTE]
 > In the recommended deployment strategy, if the source SQL Server is good fit for all three deployment targets- SQL Server on Azure VM, Azure SQL Managed Instance and Azure SQL Database, the assessment recommends a specific option that optimizes your cost and fits within the size and performance boundaries.
 
+### Security Readiness
+
+If the database/instance is marked as Ready for the target deployment type Azure SQL DB/MI, it is automatically considered Ready for Microsoft Defender for SQL. 
+If the database/instance is marked as Ready for the target deployment type SQL Server on Azure VM, it is considered Ready for Microsoft Defender for SQL if it is running any of these versions -  
+- SQL Server versions 2012, 2014, 2016, 2017, 2019, 2022
+- For all other versions, it is marked as Ready with Conditions
+
+
 ## Calculate sizing
 
 ### Instances to Azure SQL MI and Databases to Azure SQL DB configuration