Skip to content

Commit efe40ff

Browse files
committed
feedback updates
1 parent bb0df88 commit efe40ff

File tree

3 files changed

+10
-18
lines changed

3 files changed

+10
-18
lines changed

articles/migrate/cost-estimation.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,12 @@ ms.custom: engagement-fy24
99
monikerRange: migrate
1010
---
1111

12-
# Cost estimation
12+
# Cost estimation of Assessment in Azure Migrate
1313

1414
Azure Migrate assessments provide you with an estimated cost of hosting the recommended targets on Azure. These costs are identified for each right-sized target on Azure. The cost estimates are dependent on the rates in the specified region, any applicable offers, and the licensing program selected by you.
1515

16+
This article describes Azure Migrate assessments estimate hosting costs for recommended targets on Azure, based on region rates, applicable offers, and selected licensing programs.
17+
1618
## Pricing settings
1719

1820
The following assessment attributes affect your cost estimates:

articles/migrate/how-to-review-sql-assessment.md

Lines changed: 0 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -21,22 +21,6 @@ The deployment involves selecting an Azure SQL deployment type that is highly co
2121
> [!NOTE]
2222
> Migrating instances to SQL Server on Azure VM is the preferred approach for migrating SQL Server instances. When SQL Server credentials are unavailable, the Azure SQL assessment provides right-sized lift-and-shift, recommendations, specifically suggesting a move to SQL Server on Azure VM.
2323
24-
**Migrate all instances to Azure SQL Managed Instance**:
25-
26-
This strategy provides readiness and cost estimates for migrating all SQL Server instances to Azure SQL Managed Instance. There's no storage cost for the first 32-GB instance per month, with another storage costs applied in 32-GB increments. [Learn More](https://azure.microsoft.com/pricing/details/azure-sql-managed-instance/single/).
27-
28-
This strategy provides readiness and cost estimates for migrating all SQL Server instances to Azure SQL Managed Instance. There's no storage cost for the first 32-GB instance per month, with other storage costs applied in 32-GB increments.
29-
30-
**Migrate all instances to SQL Server on Azure VM**:
31-
This strategy offers readiness and cost estimates for migrating all SQL Server instances to SQL Server on Azure VM.
32-
33-
**Migrate all servers to SQL Server on Azure VM**:
34-
This strategy shows how to rehost SQL Server on Azure VM and review the associated readiness and cost estimates. Even when SQL Server credentials are unavailable, this report provides right-sized lift-and-shift, recommendations for migrating *SQL Server on Azure VM*. The readiness and sizing logic aligns with Azure VM assessment type.
35-
36-
**Migrate all SQL databases to Azure SQL Database**:
37-
38-
This strategy outlines how to migrate individual databases to Azure SQL Database, including readiness, and cost estimates. A minimum of 5-GB storage cost is added in the cost with another storage costs applied in 1-GB increments. [Learn More](https://azure.microsoft.com/pricing/details/azure-sql-database/single/)
39-
4024
## Azure readiness for SQL workloads
4125

4226
Azure SQL readiness for SQL instances and databases is based on a feature compatibility check with SQL Server on Azure VM, Azure SQL Database, and Azure SQL Managed Instance. The assessment evaluates the features currently used by the source SQL Server workloads such as SQL Agent jobs, linked servers, and the user database schemas (including tables, views, triggers, stored procedures, etc.) to identify potential compatibility issues.

articles/migrate/resource-tagging.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,8 @@ In any cloud transformation journey, a comprehensive current-state analysis of t
3535

3636
## Add tags to workloads
3737

38+
To add tags, follow these steps:
39+
3840
1. Select the workload(s) that you intend to tag from the inventory.
3941

4042
2. Select **Tags** > **Add and edit tags**.
@@ -43,10 +45,12 @@ In any cloud transformation journey, a comprehensive current-state analysis of t
4345

4446
## View tags
4547

46-
Choose the workload for which you wish to view the tags assigned.
48+
To view tags, select the workload for which you wish to view the tags assigned.
4749

4850
## Filter using tags
4951

52+
To filter using tags, follow these steps:
53+
5054
1. Select **Add filter** button beside the search bar.
5155

5256
2. Select the tag key that you want to filter with.
@@ -55,6 +59,8 @@ Choose the workload for which you wish to view the tags assigned.
5559

5660
## Import tags
5761

62+
To import using tags, follow these steps:
63+
5864
1. Select **Tags > Import tags**
5965

6066
2. Choose the file with the tags that you want to import.

0 commit comments

Comments
 (0)