Rashi's changes

Author: v-ksreedevan

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

@@ -6,7 +6,7 @@ ms.author: rajosh
 ms.manager: ronai
 ms.topic: conceptual
 ms.date: 11/30/2022
-
+ms.custom: references_regions
 ---
 
 # Business case (preview) - Common questions
@@ -20,7 +20,7 @@ This article answers common questions about business case in Azure Migrate. If y
 
 ### Why is the export gesture disabled?
 
-Business case export in .xlsx file will be supported soon.
+Currently, Business case export in .xlsx file is not supported.
 
 ### What is the difference between an assessment and a business case?
 
@@ -59,7 +59,7 @@ To verify in an existing project:
     - Eastasia, germanywestcentral, japanwest, norwayeast, switzerlandnorth
 
 ### Why can't I change the currency during business case creation?
-Currently, the currency is defaulted to USD. Support for other currencies will be added soon.
+Currently, the currency is defaulted to USD. 
 
 ### What does the different migration strategies mean?
 **Migration Strategy** | **Details** | **Assessment insights**

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

@@ -124,7 +124,7 @@ Cost components for running on-premises servers. For TCO calculations, a one yea
 |     | 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_.|
-| 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. (It's taken as an industry standard as cost per GB per month for NAS is ~$1.67 & SAN is $2.3. As Azure Migrate can't differentiate between SAN & NAS, average of $2 is taken). |
+| 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. |

articles/migrate/how-to-build-a-business-case.md

@@ -45,8 +45,8 @@ 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. 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. 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.
+**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. 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. <br\><br\> For general servers, sizing and cost comes from Azure VM assessment. <br\><br\> 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.
 
 ## Build a business case
 
@@ -81,81 +81,5 @@ There are three types of migration strategies that you can choose while building
 
     ![Screenshot of the refresh button.](./media/how-to-build-a-business-case/refresh.png)
 
-## Review the business case
-There are four major reports that you need to review:
-- **Overview**: This report is an executive summary of the business case and covers:
-    - Potential savings (TCO).
-    - Estimated year on year cashflow savings based on the estimated migration completed that year.
-    - Savings from unique Azure benefits like Azure Hybrid Benefit.
-    - Discovery insights covering the scope of the business case.
-- **On-premises vs Azure**: This report covers the breakdown of the total cost of ownership by cost categories and insights on savings.
-- **Azure IaaS**: This report covers the Azure and on-premises footprint of the servers and workloads recommended for migrating to Azure IaaS.
-- **Azure PaaS**: This report covers the Azure and on-premises footprint of the workloads recommended for migrating to Azure PaaS.
-
-### View a business case
-1. In **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select the number below **Total migration business cases**.
-1. In **Business Case**, select a business case to open it. As an example (estimations and costs, for example, only): 
-
-   ![Screenshot of the Business Case Overview.](./media/how-to-build-a-business-case/overview.png)
-
-### Overview
-#### Potential savings
-This card covers your potential total cost of ownership savings based on the chosen migration strategy. It includes one year savings from compute, storage, network, labor, and facilities cost (based on assumptions) to help you envision how Azure benefits can turn into cost savings. You can see the insights of different cost categories in the **On-premises vs Azure** report.
-##### Estimated on-premises cost
-It covers the cost of running all the servers scoped in the business case using some of the industry benchmarks. It doesn't cover Facilities (lease/colocation/power) cost by default, but you can edit it in the on-premises cost assumptions section. It includes one time cost for some of the capital expenditures like hardware acquisition etc., and annual cost for other components that you might pay as operating expenses like maintenance etc.
-##### Estimated Azure cost
-It covers the cost of all servers and workloads that have been identified as ready for migration/modernization as per the recommendation. Refer the respective *Azure IaaS* and *Azure PaaS* report for details. The Azure cost is calculated based on the right sized Azure configuration, ideal migration target and most suitable pricing offers for your workloads. You can override the migration strategy, target location or other settings in the 'Azure cost' assumptions to see how your savings could change by migrating to Azure.
-#### YoY estimated current vs future state cost
-As you plan to migrate to Azure in phases, this line chart shows your cashflow per year based on the estimated migration completed that year. By default, it's assumed that you'll migrate 0% in the current year, 20% in Year 1, 50% in Year 2, and 100% in Year 3.
-- Current state cost shows how your net cashflow will be on-premises, given your infrastructure is growing 5% per year.
-- The future state cost shows how your net cashflow will be as you migrate some percentage to Azure per year as in the 'Azure cost' assumptions, while your infrastructure is growing 5% per year.
-#### Savings with Azure Hybrid Benefits
-Currently, this card shows a static percentage of max savings you could get with Azure hybrid Benefits. Soon, you'll be able to see actual license cost savings assuming all your licenses are convertible to Azure and the savings are from bringing the existing Windows and SQL Server licenses to Azure.
-#### Discovery insights
-It covers the total severs scoped in the business case computation, virtualization distribution, utilization insights and distribution of servers based on workloads running on them.
-##### Utilization insights
-It covers which servers are ideal for cloud, servers that can be decommissioned on-premises, and servers that can't be classified based on resource utilization/performance data:
-- Ideal for cloud: These servers are best fit for migrating to Azure and comprises of active and idle servers:
-    - Active servers: These servers delivered business value by being on and had their CPU and memory utilization above 5% and network utilization above 2%.
-    - 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 don't have adequate metrics available:
-    - Unknown: Many servers can land in this section if the discovery is still ongoing or has some unaddressed discovery issues.
-    
-### On-premises vs Azure
-It covers cost components for on-premises and Azure, savings, and insights to understand the savings better.
-
-![Screenshot of on-premises and Azure comparison.](./media/how-to-build-a-business-case/comparison.png)
-
-### Azure IaaS
-In Azure tab:
-- Cost estimate by recommended target (Annual cost and also includes Compute, Storage, Network, labor components) and savings from Hybrid benefits.
-- Azure VM:
-    - Estimated cost by savings options: This card includes compute cost for Azure VMs. It is recommended that all idle servers are migrated via Pay as you go Dev/Test and others (Active and unknown) are migrated using 3 year Reserved Instance to maximize savings.
-    - Recommended VM family: This card covers the VM sizes recommended. The ones marked Unknown are the VMs that have some readiness issues and no SKUs could be found for them.
-    - Recommended storage type: This card covers the storage cost distribution across different recommended storage types.
-- SQL Server on Azure VM:
-This section assumes instance to SQL Server on Azure VM migration recommendation, and the number of VMs here are the number of instances recommended to be migrated as SQL Server on Azure VM:
-    - Estimated cost by savings options: This card includes compute cost for SQL Server on Azure VMs. It is recommended that all idle servers are migrated via Pay as you go Dev/Test and others (Active and unknown) are migrated using 3 year Reserved Instance to maximize savings.
-    - Recommended VM family: This card covers the VM sizes recommended. The ones marked Unknown are the VMs that have some readiness issues and no SKUs could be found for them.
-    - Recommended storage type: This card covers the storage cost distribution across different recommended storage types.
-In on-premises tab:
-- On-premises footprint of the servers recommended to be migrated to Azure IaaS.
-- Contribution of Zombie servers in the on-premises cost.
-- Distribution of servers by OS, virtualization, and activity state.
-### Azure PaaS
-In Azure tab:
-- Cost estimate by recommended target (Annual cost and also includes Compute, Storage, Network, labor components) and savings from Hybrid benefits.
-- Azure SQL:
-    - Estimated cost by savings options: This card includes compute cost for Azure SQL MI.
-    - Distribution by recommended service tier.
-- Azure App Service:
-   - Estimated cost by savings options: This card includes Azure App Service Plans cost.
-   - Distribution by recommended plans.
-In on-premises tab:
-- On-premises footprint of the servers recommended to be migrated to Azure PaaS.
-- Contribution of Zombie SQL instances in the on-premises cost.
-- Distribution of SQL instances by SQL version and activity state.
 ## Next steps
-- [Learn more](concepts-business-case-calculation.md) about how business cases are calculated.
+- [Learn more](how-to-view-a-business-case.md) about how to review the business case reports.