Merge pull request #235538 from rashi-ms/SQLBizCaseUpdates

April updates to business case

Author: v-regandowner

articles/migrate/common-questions-business-case.md

@@ -42,19 +42,17 @@ Business case creates assessments in the background, which could take some time
 
 ### How do I build a business case?
 
-Currently, you can create a Business case on servers and workloads discovered using a lightweight Azure Migrate appliance in your VMware environment. The appliance discovers on-premises servers and workloads. It then sends server metadata and performance data to Azure Migrate.
+Currently, you can create a Business case on servers and workloads discovered using a lightweight Azure Migrate appliance in your VMware, Hyper-V and Physical/Baremetal environment. The appliance discovers on-premises servers and workloads. It then sends server metadata and performance data to Azure Migrate.
 
 ### Why is the Build business case feature disabled?
 
-The **Build business case** feature will be enabled only when you have discovery performed using an Azure Migrate appliance for servers and workloads in a VMware environment. The Business case feature is not supported for servers and/or workloads discovered only from any of the discovery sources below:
-- Servers and/or SQL Server deployments from Hyper-V environment
-- Servers imported via .csv templates
+The **Build business case** feature will be enabled only when you have discovery performed using an Azure Migrate appliance for servers and workloads in your VMware, Hyper-V and Physical/Baremetal environment. The Business case feature is not supported for servers and/or workloads imported via a .csv file.
 
 ### Why can’t I build business case from my project?
 
-You will not be able to create a business case if your project is in one of the 6 project regions:
+You will not be able to create a business case if your project is in one of the 3 project regions:
 
-East Asia, Germany West Central, Japan West, Korea Central, Norway East, and Switzerland North.
+Germany West Central, East Asia and Switzerland North.
 
 To verify in an existing project:
 1. You can use the https://portal.azure.com/ URL to get started
@@ -64,17 +62,17 @@ To verify in an existing project:
 5. Check the Project location.
 6. The Business case feature is not supported in the following regions:
 
-    koreacentral, eastasia, germanywestcentral, japanwest, norwayeast, switzerlandnorth
+    Germany West Central, East Asia and Switzerland North.
 
 ### Why can't I change the currency during business case creation?
-Currently, the currency is defaulted to USD. 
+Currently, the currency is defaulted to USD.
 
 ### What does the different migration strategies mean?
 **Migration Strategy** | **Details** | **Assessment insights**
 --- | --- | ---
 **Azure recommended to minimize cost** | You can get the most cost efficient and compatible target recommendation in Azure across Azure IaaS and Azure PaaS targets |  For SQL Servers, sizing and cost comes from the *Recommended report* with optimization strategy- minimize cost from Azure SQL assessment.<br/><br/> For web apps, sizing and cost comes from Azure App Service assessment is picked.<br/><br/> For general servers, sizing and cost comes from Azure VM assessment.
 **Migrate to all IaaS (Infrastructure as a Service)** | You can get a quick lift and shift recommendation to Azure IaaS. | For SQL Servers, sizing and cost comes from the *Instance to SQL Server on Azure VM* report.<br/><br/> For general servers and servers hosting web apps, sizing and cost comes from Azure VM assessment.
-**Modernize to PaaS (Platform as a Service)** | You can get a PaaS preferred recommendation that means, the logic identifies workloads best fit for PaaS targets.<br/><br/> General servers are recommended with a quick lift and shift recommendation to Azure IaaS. |  For SQL Servers, sizing and cost comes from the *Instance to Azure SQL MI* report.<br/><br/> For web apps, sizing and cost comes from Azure App Service assessment. For general servers, sizing and cost comes from Azure VM assessment.
+**Modernize to PaaS (Platform as a Service)** | You can get a PaaS preferred recommendation that means, the logic identifies workloads best fit for PaaS targets.<br/><br/> General servers are recommended with a quick lift and shift recommendation to Azure IaaS. |  For SQL Servers, sizing and cost comes from the *Recommended report* with optimization strategy - *Modernize to PaaS* from Azure SQL assessment.<br/><br/> For web apps, sizing and cost comes from Azure App Service assessment. For general servers, sizing and cost comes from Azure VM assessment.
 
 > [!NOTE]
 > Although the Business case picks Azure recommendations from certain assessments, you won't be able to access the assessments directly. To deep dive into sizing, readiness and Azure cost estimates, you can create respective assessments for the servers or workloads.

articles/migrate/concepts-business-case-calculation.md

@@ -38,12 +38,14 @@ There are three types of migration strategies that you can choose while building
 --- | --- | ---
 **Azure recommended to minimize cost** | You can get the most cost efficient and compatible target recommendation in Azure across Azure IaaS and Azure PaaS targets. |  For SQL Servers, sizing and cost comes from the *Recommended report* with optimization strategy - minimize cost from Azure SQL assessment.<br/><br/> For web apps, sizing and cost comes from Azure App Service assessment is picked. <br/><br/>For general servers, sizing and cost comes from Azure VM assessment.
 **Migrate to all IaaS (Infrastructure as a Service)** | You can get a quick lift and shift recommendation to Azure IaaS. | For SQL Servers, sizing and cost comes from the *Instance to SQL Server on Azure VM* report. <br/><br/>For general servers and servers hosting web apps, sizing and cost comes from Azure VM assessment.
-**Modernize to PaaS (Platform as a Service)** | You can get a PaaS preferred recommendation that means, the logic identifies workloads best fit for PaaS targets. <br/><br/>General servers are recommended with a quick lift and shift recommendation to Azure IaaS. |  <br/><br/>For SQL Servers, sizing and cost comes from the *Instance to Azure SQL MI* report. <br/><br/>For web apps, sizing and cost comes from Azure App Service assessment. For general servers, sizing and cost comes from Azure VM assessment. Although the Business case picks Azure recommendations from certain assessments, you won't be able to access the assessments directly. To deep dive into sizing, readiness, and Azure cost estimates, you can create respective assessments for the servers or workloads.
+**Modernize to PaaS (Platform as a Service)** | You can get a PaaS preferred recommendation that means, the logic identifies workloads best fit for PaaS targets. <br/><br/>General servers are recommended with a quick lift and shift recommendation to Azure IaaS. | For SQL Servers, sizing and cost comes from the *Recommended report* with optimization strategy - *Modernize to PaaS* from Azure SQL assessment.<br/><br/> For web apps, sizing and cost comes from Azure App Service assessment. For general servers, sizing and cost comes from Azure VM assessment. 
+ 
+Although the Business case picks Azure recommendations from certain assessments, you won't be able to access the assessments directly. To deep dive into sizing, readiness, and Azure cost estimates, you can create respective assessments for the servers or workloads.
 
 
 ## How do I build a business case?
 
-Currently, you can create a Business case on servers and workloads discovered using a lightweight Azure Migrate appliance in your VMware environment. The appliance discovers on-premises servers and workloads. It then sends server metadata and performance data to Azure Migrate.
+Currently, you can create a Business case on servers and workloads discovered using a lightweight Azure Migrate appliance in your VMware, Microsoft Hyper-V and Physical/ Bare-metal environments as well as IaaS services of other public cloud. The appliance discovers on-premises servers and workloads. It then sends server metadata and performance data to Azure Migrate.
 
 ## How do I use the appliance?
 
@@ -53,19 +55,26 @@ If you're deploying an Azure Migrate appliance to discover on-premises servers,
 1. For your first Business case, create an Azure project and add the Discovery and assessment tool to it.
 1. Deploy a lightweight Azure Migrate appliance. The appliance continuously discovers on-premises servers and sends server metadata and performance data to Azure Migrate. Deploy the appliance as a VM. You don't need to install anything on servers that you want to assess.
 
-After the appliance begins server discovery, you can start building your Business case. Follow our tutorials for [VMware](./tutorial-discover-vmware.md) to try out these steps.
+After the appliance begins server discovery, you can start building your Business case. Follow our tutorials for [VMware](./tutorial-discover-vmware.md) or [Hyper-V](tutorial-discover-hyper-v.md) or [Physical/Bare-metal or other clouds](tutorial-discover-physical.md) to try out these steps.
 
-We recommend that you wait at least a day after starting discovery before you build a Business case so that enough performance/resource utilization data points are collected. Also, review the notifications/resolve issues blades on Azure Migrate hub to identify any discovery related issues prior to Business case computation. It will ensure that the IT estate in your datacenter is represented more accurately and the Business case recommendations will be more valuable.
+We recommend that you wait at least a day after starting discovery before you build a Business case so that enough performance/resource utilization data points are collected. Also, review the notifications/resolve issues blades on Azure Migrate hub to identify any discovery related issues prior to Business case computation. It ensures that the IT estate in your datacenter is represented more accurately and the Business case recommendations are more valuable.
 
 ## What data does the appliance collect?
 
-If you're using the Azure Migrate appliance, learn about the metadata and performance data that's collected for [VMware](discovered-metadata.md#collected-metadata-for-vmware-servers).
+If you're using the Azure Migrate appliance, learn about the metadata and performance data that's collected for:
+- [VMware](discovered-metadata.md#collected-metadata-for-vmware-servers).
+- [Hyper-V](discovered-metadata.md#collected-metadata-for-hyper-v-servers)
+- [Physical](discovered-metadata.md#collected-data-for-physical-servers)
 
 ## How does the appliance calculate performance data?
 
 If you use the appliance for discovery, it collects performance data for compute settings with these steps:
 
-1. The appliance collects a real-time sample point. For VMware VMs, a sample point is collected every 20 seconds.
+1. The appliance collects a real-time sample point.
+    - **VMware VMs**: A sample point is collected every 20 seconds.
+    - **Hyper-V VMs**: A sample point is collected every 30 seconds.
+    - **Physical servers**: A sample point is collected every five minutes.
+
 1. The appliance combines the sample points to create a single data point every 10 minutes for VMware and Hyper-V servers, and every 5 minutes for physical servers. To create the data point, the appliance selects the peak values from all samples. It then sends the data point to Azure.
 1. The assessment service stores all the 10-minute data points for the last month.
 1. When you create a Business case, multiple assessments are triggered in the background.
@@ -116,14 +125,15 @@ Cost components for running on-premises servers. For TCO calculations, an annual
 | Compute | Hardware | Server Hardware (Host machines) | Total hardware acquisition cost is calculated using a cost per core linear regression formula: Cost per core = 16.232*(Hyperthreaded core: memory in GB ratio) + 113.87. Hyperthreaded cores = 2*(cores) 
 |     | Software - SQL Server licensing | License cost | Calculated per two core pack license pricing of 2019 Enterprise or Standard. |
 |     |     | Software Assurance | Calculated per year as in settings. |
-|     | Software - Windows Server licensing | License cost | Calculated per two corepack license pricing of Windows Server. |
+|     | Software - Windows Server licensing | License cost | Calculated per two core pack license pricing of Windows Server. |
 |     |     | Software Assurance | Calculated per year as in settings. |
-|     | Virtualization software | Virtualization Software (VMware license cost + support + management software cost) | License cost for vSphere Standard license + Production support for vSphere Standard license + Management software cost for VSphere Standard + production support cost of management software. _Not included- other hypervisor software cost_ or  _Antivirus / Monitoring Agents_.|
+|     | Virtualization software for servers running in VMware environment | Virtualization Software (VMware license cost + support + management software cost) | License cost for vSphere Standard license + Production support for vSphere Standard license + Management software cost for VSphere Standard + production support cost of management software. _Not included- other hypervisor software cost_ or  _Antivirus / Monitoring Agents_.|
+|     | Virtualization software for servers running in Microsoft Hyper-V environment| Virtualization Software (management software cost + software assurance) | Management software cost for System Center + software assurance. _Not included- other hypervisor software cost_ or  _Antivirus / Monitoring Agents_.|
 | Storage | Storage Hardware |     | The total storage hardware acquisition cost is calculated by multiplying the Total volume of storage attached to  per GB cost. Default is USD 2 per GB per month. |
 |     | Storage Maintenance |     | Default is 10% of storage hardware acquisition cost. |
 | Network | Network Hardware and software | Network equipment (Cabinets, switches, routers, load balancers etc.) and software | As an industry standard and used by sellers in Business cases, it's a % of compute and storage cost. Default is 10% of storage and compute cost. |
 |     | Maintenance | Maintenance | Defaulted to 15% of network hardware and software cost. |
-| Facilities | Facilities & Infrastructure | DC Facilities – Lease and Power | Facilities cost has not been added by default in the on-premises cost calculations. Any lease/colocation/power cost specified here will be included as part of the Business case. |
+| Facilities | Facilities & Infrastructure | DC Facilities – Lease and Power | Facilities cost hasn't been added by default in the on-premises cost calculations. Any lease/colocation/power cost specified here will be included as part of the Business case. |
 | Labor | Labor | IT admin | DC admin cost = ((Number of virtual machines) / (Avg. # of virtual machines that can be managed by a full-time administrator)) * 730 * 12 |
 
 #### Azure cost
@@ -138,7 +148,7 @@ Cost components for running on-premises servers. For TCO calculations, an annual
 |     | Storage (PaaS) | N/A | N/A |
 | Network | Network Hardware and software | Network equipment (Cabinets, switches, routers, load balancers etc.) and software | As an industry standard and used by sellers in Business cases, it's a % of compute and storage cost. Default is 10% of storage and compute cost. |
 |     | Maintenance | Maintenance | Defaulted to 15% of network hardware and software cost. |
-| Facilities | Facilities & Infrastructure | DC Facilities - Lease and Power | Facilities cost is not applicable for Azure cost. |
+| Facilities | Facilities & Infrastructure | DC Facilities - Lease and Power | Facilities cost isn't applicable for Azure cost. |
 | Labor | Labor | IT admin | DC admin cost = ((Number of virtual machines) / (Avg. # of virtual machines that can be managed by a full-time administrator)) * 730 * 12 |
 
 ### Year on Year costs
@@ -159,12 +169,12 @@ Cost components for running on-premises servers. For TCO calculations, an annual
 | Server Depreciation | (Total server hardware acquisition cost)/(Depreciable life) | Depreciable life = 4 years |     |
 | Storage Depreciation | (Total storage hardware acquisition cost)/(Depreciable life) | Depreciable life = 4 years |     |
 | Fit out and Networking Equipment | (Total network hardware acquisition cost)/(Depreciable life) | Depreciable life = 5 years |     |
-| License Amortization | (License cost for VMware + Windows Server + SQL Server + Linux OS)/(Depreciable life) | Depreciable life = 5 years | VMware licenses won't be retained; Windows + SQL. Licenses will be retained based on AHUB option in Azure). |
+| License Amortization | (virtualization cost + Windows Server + SQL Server + Linux OS)/(Depreciable life) | Depreciable life = 5 years | VMware licenses are not retained; Windows, SQL and Hyper-V management software licenses are retained based on AHUB option in Azure).|
 | **Operating Asset Expense (OPEX) (B)** |     |     |     |
 | Network maintenance | Per year |     |     |
 | Storage maintenance | Per year | Power draw per Server, Average price per KW per month based on location. |     |
-| License Support | License support cost for VMware + Windows Server + SQL Server + Linux OS |     | VMware licenses won't be retained; Windows + SQL. licenses will be retained based on AHUB option in Azure). |
-| Datacenter Admin cost | Number of people * costs per hour for one hour | Cost per hour based on location. |     |
+| License Support | License support cost for virtualization + Windows Server + SQL Server + Linux OS |     | VMware licenses are not retained; Windows, SQL and Hyper-V management software licenses are retained based on AHUB option in Azure). |
+| Datacenter Admin cost | Number of people * hourly cost * 730 hours | Cost per hour based on location. |     |
 
 #### Future state (on-premises + Azure)
 
@@ -176,7 +186,7 @@ It assumes that the customer does a phased migration to Azure with following % o
 
 You can override the above values in the assumptions section of the Business case.
 
- In Azure, there is no CAPEX, the yearly Azure cost is an OPEX
+ In Azure, there's no CAPEX, the yearly Azure cost is an OPEX
 
 |  **Component**  | **Year 0** | **Year 1** | **Year 2** | **Year 3** | **Year 4** |
 --- | --- | --- | --- | --- | --- |