Merge pull request #247101 from Karthigasree/02Aug-MDCUpdates

MDC updates

Author: prmerger-automator[bot]

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.
@@ -153,7 +154,7 @@ To calculate readiness, the assessment reviews the server properties and operati
 
 For an Azure VM Assessment, the assessment reviews the following properties of an on-premises VM to determine whether it can run on Azure VMs.
 
-Property | Details | Azure readiness status
+**Property** | **Details** | **Azure readiness status**
 --- | --- | ---
 **Boot type** | Azure supports UEFI boot type for OS mentioned [here](./common-questions-server-migration.md#which-operating-systems-are-supported-for-migration-of-uefi-based-machines-to-azure)| Not ready if the boot type is UEFI and Operating System running on the VM is: Windows Server 2003/Windows Server 2003 R2/Windows Server 2008/Windows Server 2008 R2
 **Cores** | Each server must have no more than 128 cores, which is the maximum number an Azure VM supports.<br><br> If performance history is available, Azure Migrate considers the utilized cores for comparison. If the assessment settings specify a comfort factor, the number of utilized cores is multiplied by the comfort factor.<br><br> If there's no performance history, Azure Migrate uses the allocated cores to apply the comfort factor. | Ready if the number of cores is within the limit
@@ -188,6 +189,25 @@ 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 has the following:
+- 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, the server 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.
@@ -337,6 +357,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
@@ -247,6 +256,7 @@ This section provides guidance to configure the target resource and steps to mig
 
 ## Calculate monthly costs
 After sizing recommendations are complete, Azure SQL assessment calculates the compute and storage costs for the recommended Azure SQL configurations using an internal pricing API. It aggregates the compute and storage cost across all instances to calculate the total monthly compute cost. 
+
 ### Compute cost
 - To calculate the compute cost for an Azure SQL configuration, the assessment considers the following properties:
     - Azure Hybrid Benefit for SQL and Windows licenses
@@ -269,6 +279,11 @@ After sizing recommendations are complete, Azure SQL assessment calculates the c
     - A minimum of 5 GB storage cost is added in the cost estimate and additional storage cost is added for storage in 1 GB increments. [Learn More](https://azure.microsoft.com/pricing/details/sql-database/single/).
 - **Azure SQL Managed Instance**
     - There's no storage cost added for the first 32 GB/instance/month storage and additional storage cost is added for storage in 32 GB increments. [Learn More](https://azure.microsoft.com/pricing/details/azure-sql/sql-managed-instance/single/).
+
+### Security cost
+
+For SQL Server instances and DBs recommended for SQL Server on Azure VM, Azure SQL MI or Azure SQL DB, if they're ready to run Defender for SQL, the Defender for SQL per SQL Server instance for that region is added. For DBs recommended to Azure SQL DB, cost is rolled up at instance level.
+
         
 ## Next steps
 - [Review](best-practices-assessment.md) best practices for creating assessments. 

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

@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.topic: conceptual
 ms.service: azure-migrate
-ms.date: 03/03/2023
+ms.date: 08/02/2023
 ms.custom: engagement-fy23
 ---
 
@@ -62,6 +62,7 @@ Here's what's included in Azure App Service assessment properties:
 **Currency** | The billing currency for your account.
 **Discount (%)** | Any subscription-specific discounts you receive on top of the Azure offer. The default setting is 0%.
 **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 App Service deployment with Microsoft Defender for Cloud.  
 
 [Review the best practices](best-practices-assessment.md) for creating an assessment with Azure Migrate.
 
@@ -77,6 +78,10 @@ Azure App Service readiness for web apps is based on feature compatibility check
 1. If there are any compatibility issues that may block the migration to a specific target deployment type, the readiness is marked as **Not ready** with **issue** details and recommended remediation guidance.
 1. If the discovery is still in progress or there are any discovery issues for a web app, the readiness is marked as **Unknown** as the assessment couldn't compute the readiness for that web app.
 
+### Security readiness
+If the web app is marked as **Ready** or **Ready with conditions** for Azure App Service, it is marked as **Ready** for Microsoft Defender for App Service.
+
+
 ## Calculate sizing
 
 ### Azure App Service SKU
@@ -112,6 +117,10 @@ P1v3  | 16
 > [!NOTE]
 > Your App Service plan can be scaled up and down at any time. [Learn more](../app-service/overview-hosting-plans.md#what-if-my-app-needs-more-capabilities-or-features).
 
+### Security cost
+For web apps that have been recommended to App Service plans, the security cost is calculated per App Service plan that has been recommended.
+
+
 ## Next steps
 - [Review](best-practices-assessment.md) best practices for creating assessments.
 - Learn how to run an [Azure App Service assessment](how-to-create-azure-app-service-assessment.md).