Skip to content

Commit 2eb73c5

Browse files
author
Hanaa Musa
committed
Enhancements
1 parent 8c727dc commit 2eb73c5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/migrate/common-questions-discovery-assessment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ When you create an assessment in Azure, based on performance duration and perfor
6969

7070
Import-based assessments are assessments created with machines that are imported into Azure Migrate using a CSV file. Only four fields are mandatory to import: Server name, cores, memory, and operating system. Here are some things to note:
7171
- The readiness criteria is less stringent in import-based assessments on the boot type parameter. If the boot type isn't provided, it is assumed the machine has BIOS boot type and the machine is not marked as **Conditionally Ready**. In assessments with discovery source as appliance, the readiness is marked as **Conditionally Ready** if the boot type is missing. This difference in readiness calculation is because users may not have all information on the machines in the early stages of migration planning when import-based assessments are done.
72-
- Performance-based import assessments use the utilization value provided by the user for right-sizing calculations. In assessments with discovery source as appliance, the chosen percentile value is picked from the performance data collected by the appliance.
72+
- Performance-based import assessments use the utilization value provided by the user for right-sizing calculations. Since the utilization value is provided by the user, the **Performance history** and **Percentile utilization** options are disabled in the assessment properties. In assessments with discovery source as appliance, the chosen percentile value is picked from the performance data collected by the appliance.
7373

7474
## What is dependency visualization?
7575

0 commit comments

Comments
 (0)