Merge pull request #220730 from v-ksreedevan/07Dec-Fixes

Edits in live

Author: v-dirichards

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

@@ -5,7 +5,7 @@ author: rashijoshi
 ms.author: rajosh
 ms.manager: ronai
 ms.topic: conceptual
-ms.date: 11/30/2022
+ms.date: 12/07/2022
 ms.custom: references_regions
 ---
 
@@ -34,75 +34,79 @@ Business case creates assessments in the background, which could take some time
 
 ## Build business case 
 
-## How do I build a business case?
+### 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.
 
+### Why is the Build business case feature disabled?
 
-### Why can’t I build business case from my project?
-
-You won't be able to create a Business case if your project is in one of the 5 project regions:
-East Asia, Germany West Central, Japan West, Norway East, Switzerland North.
-
-To verify in an existing project:
-
-1. You can use the https://portal.azure.com/ URL to get started.
+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
 
-2. In Azure Migrate, Go to **Servers, databases and webapps** migration goal.
+### Why can’t I build business case from my project?
 
-3. On the Azure Migrate: Discovery and assessment tool, select **Overview**.
+You will not be able to create a business case if your project is in one of the 6 project regions:
 
-4. Under project details, select **Properties**.
+East Asia, Germany West Central, Japan West, Korea Central, Norway East, and Switzerland North.
 
-5. Check the Project location. If the project location is one of the below regions, we’d suggest you change the project or create a new one in another region in the geography using [this link](https://portal.azure.com/?feature.createprojectwithregion=true)
+To verify in an existing project:
+1. You can use the https://portal.azure.com/ URL to get started
+2. In Azure Migrate, go to **Servers, databases and webapps** > **Migration goals**.
+3. On the **Azure Migrate: Discovery and assessment** tool, select **Overview**.
+4. Under Project details, select **Properties**.
+5. Check the Project location.
+6. The Business case feature is not supported in the following regions:
 
-    - Eastasia, germanywestcentral, japanwest, norwayeast, switzerlandnorth
+    koreacentral, eastasia, germanywestcentral, japanwest, norwayeast, switzerlandnorth
 
 ### Why can't I change the currency during business case creation?
 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. For web apps, sizing and cost comes from Azure App Service assessment is picked. 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. 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. 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. For web apps, sizing and cost comes from Azure App Service assessment. For general servers, sizing and cost comes from Azure VM assessment.
+**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.
 
 > [!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.
+
 ## Business case recommendation
 
 
 ### I can't see some servers and SQL instances
 
 Multiple possibilities:
 
-- Discovery hasn't completed - Wait for the discovery to get completed (recommended to wait at least 24 hours).
+- Discovery hasn't completed - Wait for the discovery to complete. It is recommended to wait for at least 24 hours.
 - Check and resolve any discovery issues.
 - Changes to discovery happened after creating the Business case.
 
-To fetch latest discovery data, recalculate by selecting **Recalculate** button, or changing the assumptions and selecting **Save**.
+To fetch latest discovery data, recalculate by selecting the **Recalculate** button, or changing the assumptions and selecting **Save**.
 
 
 ### Why are all or some of the servers marked as unknown in the utilization insights?
 
-We couldn't collect sufficient data points to classify these servers. We recommend that you wait at least a day after starting discovery so that the Business case has enough utilization data points. Also, review the notifications/ resolve issues blades on Azure Migrate hub to identify any discovery related issues prior to Business case computation. Reviewing issues prior to building a Business case will ensure that the IT estate in your datacenter is represented more accurately.
+We couldn't collect sufficient data points to classify these servers. We recommend that you wait at least a day after starting discovery so that the Business case has enough utilization data points. Also, review the notifications/resolve issues blades on Azure Migrate hub to identify any discovery related issues prior to Business case computation. Reviewing issues prior to building a Business case will ensure that the IT estate in your datacenter is represented more accurately.
 
 ### Was the readiness taken into consideration in the recommendations?
-Yes, but 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.
+Yes, but 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.
 
 ### Why was I recommended this Azure target?
 Based on the migration strategy, this was the best recommended target. To understand detailed readiness and sizing, create an assessment and refer to the details.
 
 
 ### How do I get to know details for servers or workloads that aren't ready for Azure?
-To deep dive into sizing, readiness and Azure cost estimates, you can create respective assessments for the servers or workloads.
+To deep dive into sizing, readiness, and Azure cost estimates, you can create respective assessments for the servers or workloads.
 
 
 ### Does the Azure SQL recommendation logic include SQL consolidation?
 No, it does not include SQL consolidation.
 
 ## Next steps
-[Learn more](how-to-build-a-business-case.md) about how to build a Business case.
-[Learn more](how-to-view-a-business-case.md) about how to review the Business case reports.
+
+- [Learn more](how-to-build-a-business-case.md) about how to build a Business case.
+- [Learn more](how-to-view-a-business-case.md) about how to review the Business case reports.
 

articles/migrate/concepts-assessment-calculation.md

@@ -24,7 +24,7 @@ An assessment with the Discovery and assessment tool measures the readiness and
 
 There are three types of assessments you can create using Azure Migrate: Discovery and assessment.
 
-***Assessment Type** | **Details**
+**Assessment Type** | **Details**
 --- | ---
 **Azure VM** | Assessments to migrate your on-premises servers to Azure virtual machines. You can assess your on-premises servers in [VMware](how-to-set-up-appliance-vmware.md) and [Hyper-V](how-to-set-up-appliance-hyper-v.md) environment, and [physical servers](how-to-set-up-appliance-physical.md) for migration to Azure VMs using this assessment type.
 **Azure SQL** | Assessments to migrate your on-premises SQL servers from your VMware environment to Azure SQL Database or Azure SQL Managed Instance.

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

@@ -5,7 +5,7 @@ author: rashi-ms
 ms.author: rajosh
 ms.manager: ronai
 ms.topic: conceptual
-ms.date: 11/30/2022
+ms.date: 12/07/2022
 ---
 
 # Business case (preview) overview
@@ -36,9 +36,9 @@ There are three types of migration strategies that you can choose while building
 
 **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.
+**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. |  <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.
 
 
 ## How do I build a business case?
@@ -55,7 +55,7 @@ If you're deploying an Azure Migrate appliance to discover on-premises servers,
 
 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.
 
-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 will ensure that the IT estate in your datacenter is represented more accurately and the Business case recommendations will be more valuable.
 
 ## What data does the appliance collect?
 
@@ -65,7 +65,7 @@ If you're using the Azure Migrate appliance, learn about the metadata and perfor
 
 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. For VMware VMs, a sample point is collected every 20 seconds.
 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.
@@ -85,7 +85,7 @@ It covers which servers are ideal for cloud, servers that can be decommissioned
     - **Idle servers**: These servers were on but didn't deliver business value by having their CPU and memory utilization below 5% and network utilization below 2%.
 - **Decommission**: These servers were expected to deliver business value, but didn't and can be decommissioned on-premises and recommended to not migrate to Azure:
     - **Zombie**: The CPU, memory and network utilization were 0% with no performance data collection issues.
-- These servers were on but do not have adequate metrics available :
+- These servers were on but do not have adequate metrics available:
     - **Unknown**: Many servers can land in this section if the discovery is still ongoing or has some unaddressed discovery issues.
 
 ## What comprises a business case?
@@ -118,7 +118,7 @@ Cost components for running on-premises servers. For TCO calculations, a one yea
 |     |     | Software Assurance | Calculated per year as in settings. |
 |     | Software - Windows Server licensing | License cost | Calculated per two corepack 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 | 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_.|
 | 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. |
@@ -151,7 +151,7 @@ Cost components for running on-premises servers. For TCO calculations, a one yea
 | OPEX | Total OPEX (B) | Y1 OPEX = Total OPEX (B) * (1+server growth rate%) | Y2 OPEX = Y1 OPEX (B) * (1+server growth rate%) | Y3 OPEX = Y2 OPEX (B) * (1+server growth rate%) | Y4 OPEX = Y3 OPEX (B) * (1+server growth rate%) |
 | Status Quo Cash Flow | Y0 Cashflow  = Total CAPEX (A) + Total OPEX (B) | Y1 Cashflow= Y1 CAPEX+ Y1 OPEX | Y2 Cashflow= Y2 CAPEX + Y2 OPEX | Y3 Cashflow= Y3 CAPEX (A) + Y3 OPEX (B) | Y4 Cashflow= Y4 CAPEX (A) + Y4 OPEX (B) |
 
-**CAPEX & OPEX:**
+**CAPEX & OPEX**
 
 |   Component  | Sub component  | Assumptions | Azure retained |
  --- | --- | --- | --- |
@@ -178,7 +178,7 @@ You can override the above values in the assumptions section of the Business cas
 
  In Azure, there is no CAPEX, the yearly Azure cost is an OPEX
 
-|  Component  | **Year 0** | **Year 1** | **Year 2** | **Year 3** | **Year 4** |
+|  **Component**  | **Year 0** | **Year 1** | **Year 2** | **Year 3** | **Year 4** |
 --- | --- | --- | --- | --- | --- |
 | CAPEX | Total CAPEX (A) | Y1 CAPEX Azure =80%* (Y1 CAPEX On-premises) | Y2 CAPEX Azure =50%* (Y2 CAPEX On-premises) | Y3 CAPEX Azure =0%* (Y3 CAPEX On-premises) | Y4 CAPEX = 0%* (Y4 CAPEX On-premises) |
 | OPEX | Total OPEX (B) | Y1 OPEX Azure = 80%* (Y1 OPEX On-premises)+20%* (Azure Yearly cost) * (1+server growth rate%) | Y2 OPEX Azure = 50%* (Y2 OPEX On-premises)+50%* (Azure Yearly cost) * (1+server growth rate%) | Y3 OPEX Azure = 100%* (Azure Yearly cost) * (1+server growth rate%) | Y4 OPEX Azure = 100%* (Azure Yearly cost) * (1+server growth rate%) |