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/centralized-issue-tracking.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ The Action Center can be accessed directly from the Azure Migrate dashboard, pro
29
29
30
30

31
31
32
-
-**Comprehensive issue tracking:** Users can see detailed information for each issue, including **severity level, affected workloads, affected features,** and **timestamps**. Each issue is accompanied by specific messages, allowing users to understand the nature of the problem and respond accordingly. Users can also sort and filter issues based on **severity, affected workload(s), timestamps**, and other parameters, enabling efficient prioritization of tasks and quick identification of high-severity issues that require immediate attention. Moreover, users can also have a view by affected workloads, where they can identify different issues by workloads.
32
+
-**Comprehensive issue tracking:** Users can see detailed information for each issue, including **severity level, affected workloads, affected features,** and **timestamps**. Each issue is accompanied by specific messages, allowing users to understand the nature of the problem and respond accordingly. Users can also sort and filter issues based on **severity, affected workload(s), timestamps**, and other parameters, enabling efficient prioritization of tasks and quick identification of high-severity issues that require immediate attention. Users can also have a view by affected workloads, where they can identify different issues by workloads.
33
33
34
34
[](./media/centralized-issue-tracking/view-affected-workloads-expanded.png#lightbox)
Copy file name to clipboardExpand all lines: articles/migrate/how-to-create-assessment.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,9 @@ monikerRange: migrate
13
13
14
14
# Create an Azure VM assessment
15
15
16
-
This article explains how to create an Azure VM assessments. For more information on general Azure Migrate assessment concepts, refer to the [assessment overview](concepts-assessment-overview.md). To quickly migrate your on-premises or public cloud servers to Azure using lift and shift, create an Azure VM assessment to check readiness, cost, and get migration advice for your workloads.
16
+
This article explains how to create an Azure VM assessments. For detailes information on general Azure Migrate assessment concepts, see [assessment overview](concepts-assessment-overview.md).
17
+
18
+
To quickly migrate your on-premises or public cloud servers to Azure using lift and shift, create an Azure VM assessment to check readiness, cost, and get migration advice for your workloads.
17
19
18
20
> [!Note]
19
21
> All assessments you create with Azure Migrate are a point-in-time snapshot of data. The assessment results are subject to change based on aggregated server performance data collected or change in the source configuration.
@@ -31,17 +33,17 @@ Once you have discovered your servers, identify if you want to create an As-is o
31
33
32
34
## Create an assessment
33
35
34
-
To create an assessment, follow the steps:
36
+
To create an assessment, follow these steps:
35
37
36
-
1.To create an Azure VM assessment, go to **Infrastructure** tab and select all the VMs you would like to assess.
38
+
1.Go to **Infrastructure** tab and select all the VMs you want to assess.
37
39
1. You can apply column based or custom tags-based filters to identify and add VMs to the scope of your assessment.
38
-
1. After you have selected all the servers, select **Create assessment**.
40
+
After you have selected all the servers, select **Create assessment**.
39
41
1. Provide a friendly name for the assessment. You see a query that you used to select the servers on the previous screen. Review the number of servers added and the query used before moving ahead. If you want to add more servers to the assessment, select **Add workloads**. Once you have added all the servers to the assessment scope, select **Next**.
40
-
1. You can customize the assessment properties to fit your requirements. Specify the general properties for **Target region**, **Default environment**, **Pricing options**, **Saving options**, and **Sizing criteria**. [Learn more](assessment-report.md).
42
+
You can customize the assessment properties to fit your requirements. Specify the general properties for **Target region**, **Default environment**, **Pricing options**, **Saving options**, and **Sizing criteria**. [Learn more](assessment-report.md).
41
43
1. Select **Next** to navigate to the Azure VM specific assessment properties.
42
44
1. Select **Edit defaults**:
43
45
1. To review and customize server-specific settings.
44
-
1.For Azure VM to review the settings for Azure VM assessment. [Learn more](assessment-properties.md).
46
+
1.Review Azure VM settings for the Azure VM assessment. [Learn more](assessment-properties.md).
45
47
1. Select **Save** if you customized any property.
46
48
1. In **Review + create assessment**, review the assessment details, and select **Create Assessment** to run the assessment.
47
49
1. After the assessment is created, view the assessment in **Decide and plan** > **Assessments** > **Workloads**.
Copy file name to clipboardExpand all lines: articles/migrate/review-azure-vmware-solution-assessment.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ You can select **Sizing assumptions** to understand the assumptions that went i
27
27
28
28
1. In **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select the number next to **Azure VMware Solution**.
29
29
30
-
1. In **Assessments**, select an assessment to open it. For example, estimations and costs:
30
+
1. In **Assessments**, select an assessment to open it. *For example*, estimations and costs:
31
31
32
32
:::image type="content" source="./media/tutorial-assess-vmware-azure-vmware-solution/avs-assessment-summary-inline.png" alt-text="Screenshot of AVS Assessment summary." lightbox="./media/tutorial-assess-vmware-azure-vmware-solution/avs-assessment-summary-expanded.png":::
33
33
@@ -39,11 +39,11 @@ You can select **Sizing assumptions** to understand the assumptions that went i
39
39
40
40
2. Review the server status:
41
41
-**Ready for AVS**: The server can be migrated as-is to Azure (AVS) without any changes. It will start in AVS with full AVS support.
42
-
-**Ready with conditions**: There might be some compatibility issues, for example, internet protocol or deprecated OS in VMware, and need to be remediated before migrating to Azure VMware Solution. To fix any readiness issues, follow the remediation guidance the assessment suggests.
43
-
-**Not ready for AVS**: The VM will not start in AVS. For example, if the on-premises VMware VM has an external device attached such as a cd-rom the VMware vMotion operation will fail (if using VMware vMotion).
42
+
-**Ready with conditions**: There might be some compatibility issues, for example, Internet protocol or deprecated OS in VMware, and need to be remediated before migrating to Azure VMware Solution. To fix any readiness issues, follow the remediation guidance the assessment suggests.
43
+
-**Not ready for AVS**: The VM will not start in AVS. *For example*, if the on-premises VMware VM has an external device attached such as a CD-ROM the VMware vMotion operation will fail (if using VMware vMotion).
44
44
-**Readiness unknown**: Azure Migrate couldn't determine the readiness of the server because of insufficient metadata collected from the on-premises environment.
45
45
46
-
3. Review the Suggested tool:
46
+
3. Review the suggested tool:
47
47
-**VMware HCX Advanced or Enterprise**: For VMware vSphere VMs, VMware Hybrid Cloud Extension (HCX) solution is the suggested migration tool to migrate your on-premises workload to your Azure VMware Solution (AVS) private cloud. [Learn More](../azure-vmware/configure-vmware-hcx.md).
48
48
-**Unknown**: For servers imported via a CSV or RVTools file, the default migration tool is unknown. Though for VMware vSphere VMs, it's suggested to use the VMware Hybrid Cloud Extension (HCX) solution.
49
49
@@ -61,7 +61,7 @@ This view shows the estimated cost of running servers in Azure VMware Solution.
61
61
62
62
2. You can review monthly storage cost estimates. This view shows aggregated storage costs for the assessed group, split over different types of storage disks.
63
63
64
-
3. You can drilldown to see details for specific servers.
64
+
3. You can drill-down to see details for specific servers.
Copy file name to clipboardExpand all lines: articles/migrate/review-sql-assessment.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,12 @@ This article describes the various components of a SQL assessment and how you ca
19
19
Follow these steps to view the assessment that you created.
20
20
21
21
1. In **Servers, databases and web apps** > **Azure Migrate: Discovery and assessment**, select the number next to Azure SQL assessment.
22
-
2. Select the assessment name, which you wish to view. For example, estimations and costs.
22
+
2. Select the assessment name, which you wish to view. *For example*, estimations and costs.
23
23
24
24
:::image type="content" source="./media/tutorial-assess-sql/assessment-sql-summary-inline.png" alt-text="Screenshot of Overview of SQL assessment." lightbox="./media/tutorial-assess-sql/assessment-sql-summary-expanded.png":::
25
25
26
-
3. Review the assessment summary. You can also edit the assessment settings or recalculate the assessment.
26
+
3. Review the assessment summary.
27
+
You can also edit the assessment settings or recalculate the assessment.
27
28
28
29
### Discovered entities
29
30
@@ -33,7 +34,7 @@ This indicates the number of SQL servers, instances, and databases that were ass
33
34
34
35
This indicates the different migration strategies that you can consider for your SQL deployments. You can review the readiness for target deployment types and the cost estimates for SQL Servers/Instances/Databases that are marked ready or ready with conditions:
35
36
36
-
-**Recommended deployment**This strategy involves selecting an Azure SQL deployment type that is both highly compatible with your SQL instance and cost-effective. By migrating to a Microsoft-recommended target, you can significantly reduce your overall migration effort. If your instance is prepared for SQL Server on Azure VM, Azure SQL Managed Instance, and Azure SQL Database, it is advisable to choose the deployment type that presents the fewest migration readiness issues and offers the best cost-efficiency.
37
+
-**Recommended deployment**: Azure SQL deployment offers the best compatibility and cost-effectiveness for your SQL instance. Choosing a Microsoft-recommended target minimizes migration effort. If your instance supports SQL Server on Azure VM, Azure SQL Managed Instance, and Azure SQL Database, the most cost-effective and migration-ready option is recommended. This includes readiness checks and monthly cost estimates for instances marked as *Ready or Ready* with conditions.
37
38
38
39
You can see the SQL Server instance readiness for different recommended deployment targets and monthly cost estimates for SQL instances marked *Ready* and *Ready with conditions*.
39
40
@@ -81,15 +82,15 @@ You can review readiness reports for different migration strategies:
Recommended | MI readiness (Azure SQL MI), VM readiness (SQL Server on Azure VM), DB readiness (Azure SQL DB).
85
-
Instances to Azure SQL MI | MI readiness (Azure SQL Managed Instance)
86
-
Instances to SQL Server on Azure VM | VM readiness (SQL Server on Azure VM).
87
-
Servers to SQL Server on Azure VM | Azure VM readiness (SQL Server on Azure VM).
88
-
Databases to Azure SQL DB | DB readiness (Azure SQL Database)
85
+
Recommended | MI readiness (Azure SQL MI), VM readiness (SQL Server on Azure VM), DB readiness (Azure SQL DB).|
86
+
|Instances to Azure SQL MI | MI readiness (Azure SQL Managed Instance)|
87
+
|Instances to SQL Server on Azure VM | VM readiness (SQL Server on Azure VM).|
88
+
|Servers to SQL Server on Azure VM | Azure VM readiness (SQL Server on Azure VM).|
89
+
|Databases to Azure SQL DB | DB readiness (Azure SQL Database)|
89
90
90
91
1. Review the readiness for the assessed SQL instances/SQL Servers/Databases:
91
92
-**Ready**: The instance/server is ready to be migrated to SQL Server on Azure VM/Azure SQL MI/Azure SQL DB without any migration issues or warnings.
92
-
- Ready: The instance is ready to be migrated to Azure VM/Azure SQL MI/Azure SQL DB without any migration issues but has some migration warnings that you need to review. You can select the hyperlink to review the migration warnings and the recommended remediation guidance.
93
+
- Ready: The instance is ready to be migrated to Azure VM/Azure SQL MI/Azure SQL DB without any migration issues but has some migration warnings that you need to review. Select **Ready**to review the migration warnings and the recommended remediation guidances.
93
94
-**Ready with conditions**: The instance/server has one or more migration issues for migrating to Azure VM/Azure SQL MI/Azure SQL DB. You can select the hyperlink and review the migration issues and the recommended remediation guidance.
94
95
-**Not ready**: The assessment could not find a SQL Server on Azure VM/Azure SQL MI/Azure SQL DB configuration meeting the desired configuration and performance characteristics. Select the hyperlink to review the recommendation to make the instance/server ready for the desired target deployment type.
95
96
-**Unknown**: Azure Migrate can't assess readiness, because the discovery is in progress or there are issues during discovery that need to be fixed from the notifications blade. If the issue persists, contact [Microsoft support](https://support.microsoft.com).
0 commit comments