You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/migrate/common-questions-business-case.md
+18-13Lines changed: 18 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title: Questions about business case in Azure Migrate
3
-
description: Get answers to common questions about business case in Azure Migrate.
2
+
title: Questions about Business case in Azure Migrate
3
+
description: Get answers to common questions about Business case in Azure Migrate.
4
4
author: rashijoshi
5
5
ms.author: rajosh
6
6
ms.manager: ronai
@@ -11,7 +11,7 @@ ms.custom: references_regions
11
11
12
12
# Business case (preview) - Common questions
13
13
14
-
This article answers common questions about business case in Azure Migrate. If you have other questions, check these resources:
14
+
This article answers common questions about Business case in Azure Migrate. If you have other questions, check these resources:
15
15
16
16
-[General questions](resources-faq.md) about Azure Migrate.
17
17
- Questions about the [Azure Migrate appliance](common-questions-appliance.md).
@@ -26,22 +26,22 @@ Currently, Business case export in .xlsx file is not supported.
26
26
27
27
An assessment helps you understand the readiness, sizing and Azure cost estimates (only compute and storage) of a particular source and targets. It's useful in understanding *How to migrate to Azure*.
28
28
29
-
A business case helps you understand on-premises cost estimates, Azure cost estimates and potential savings (TCO and YoY). It helps you understand *Why Azure?* and helps understand the quick wins and unique Azure Benefits.
29
+
A Business case helps you understand on-premises cost estimates, Azure cost estimates and potential savings (TCO and YoY). It helps you understand *Why Azure?* and helps understand the quick wins and unique Azure Benefits.
30
30
31
31
### Why is my business case in computing status?
32
32
33
-
Business case creates assessments in the background, which could take some time depending on the number of servers, SQL servers and web apps present in your project. It could take somewhere between 15 mins to 3 hours for the business case to get computed. If it's still stuck in computing status, create a support request.
33
+
Business case creates assessments in the background, which could take some time depending on the number of servers, SQL servers and web apps present in your project. It could take somewhere between 15 mins to 3 hours for the Business case to get computed. If it's still stuck in computing status, create a support request.
34
34
35
-
## Build Business case
35
+
## Build business case
36
36
37
37
## How do I build a business case?
38
38
39
-
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.
39
+
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.
40
40
41
41
42
42
### Why can’t I build business case from my project?
43
43
44
-
You won't be able to create a business case if your project is in one of the 5 project regions:
44
+
You won't be able to create a Business case if your project is in one of the 5 project regions:
45
45
East Asia, Germany West Central, Japan West, Norway East, Switzerland North.
46
46
47
47
To verify in an existing project:
@@ -69,8 +69,8 @@ Currently, the currency is defaulted to USD.
69
69
**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.
70
70
71
71
> [!NOTE]
72
-
> 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.
73
-
## Business Case recommendation
72
+
> 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.
73
+
## Business case recommendation
74
74
75
75
76
76
### I can't see some servers and SQL instances
@@ -79,14 +79,14 @@ Multiple possibilities:
79
79
80
80
- Discovery hasn't completed - Wait for the discovery to get completed (recommended to wait at least 24 hours).
81
81
- Check and resolve any discovery issues.
82
-
- Changes to discovery happened after creating the business case.
82
+
- Changes to discovery happened after creating the Business case.
83
83
84
84
To fetch latest discovery data, recalculate by selecting **Recalculate** button, or changing the assumptions and selecting **Save**.
85
85
86
86
87
87
### Why are all or some of the servers marked as unknown in the utilization insights?
88
88
89
-
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.
89
+
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.
90
90
91
91
### Was the readiness taken into consideration in the recommendations?
92
92
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.
@@ -100,4 +100,9 @@ To deep dive into sizing, readiness and Azure cost estimates, you can create res
100
100
101
101
102
102
### Does the Azure SQL recommendation logic include SQL consolidation?
103
-
No, it does not include SQL consolidation.
103
+
No, it does not include SQL consolidation.
104
+
105
+
## Next steps
106
+
[Learn more](how-to-build-a-business-case.md) about how to build a Business case.
107
+
[Learn more](how-to-view-a-business-case.md) about how to review the Business case reports.
0 commit comments