Skip to content

Commit 796eb79

Browse files
Apply suggestions from code review
Co-authored-by: Page Writer <[email protected]>
1 parent 392a4b0 commit 796eb79

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/migration/migrate-to-azure.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Migrate Workloads to Azure
3-
description: Learn how to migrate workloads from AWS and Google Cloud to Azure, including planning, implementation, and optimization strategies.
3+
description: Learn about migration resources that might help you transition workloads from AWS and Google Cloud to Azure.
44
author: robbyatmicrosoft
55
ms.author: robbymillsap
66
ms.date: 03/24/2025
@@ -10,7 +10,7 @@ ms.custom: migration
1010

1111
# Migrate workloads to Azure from other cloud platforms
1212

13-
The Azure migration guide collection helps workload teams plan and implement their workload migration. It includes guidance for migrations from cloud platforms, like Amazon Web Services (AWS) and Google Cloud, to Microsoft Azure. This guidance assumes that, after you complete your migration to Azure, you decommission the workload on the source platform.
13+
This content collection is curated to help workload teams plan and implement their workload migration. It covers migrations from cloud platforms, like Amazon Web Services (AWS) and Google Cloud Platform (GCP), to Microsoft Azure. The expected outcome is that, after you complete your migration to Azure, you decommission the workload on the source platform.
1414

1515
> [!IMPORTANT]
1616
>
@@ -20,7 +20,7 @@ Migration to Azure typically involves replatforming the workload, which includes
2020

2121
## Prerequisites for workload migrations
2222

23-
Before you migrate workloads, ensure that you commit your organization to Azure and establish your adoption approach. We recommend that you understand the fundamental Azure concepts and have an active Azure enrollment. To achieve these goals, explore the following Cloud Adoption Framework for Azure resources:
23+
Workloads should be migrated only after the organization is committed to Azure and have established their approach for adopting Azure. Before migrating workloads, we recommend that you understand the fundamental concepts on Azure and have an active Azure enrollment. Explore these Cloud Adoption Framework (CAF) resources to achieve these goals:
2424

2525
- To learn about terms in Azure and how the concepts relate to one another, see [Azure fundamental concepts](/azure/cloud-adoption-framework/ready/considerations/fundamental-concepts).
2626

@@ -32,7 +32,7 @@ In the next phase, the workload team plans and implements the migration. They as
3232

3333
This collection applies to the following workload roles and functions at the team level.
3434

35-
- **Workload architects** who redesign various architecture aspects and validate the overall architecture to ensure that it continues to meet business requirements. Architects address gaps by considering the workload's specific characteristics and business constraints.
35+
- **Workload architects** who might redesign various architecture aspects and validate the overall architecture to ensure that it continues to meet business requirements. Architects address gaps by considering the workload's specific characteristics and business constraints.
3636

3737
- **Workload team members** who need to understand how their responsibilities change during the migration process and after migration. For example, database administrators who manage scripts and perform daily backups on Amazon Relational Database Service must adapt to performing the same tasks on Azure SQL Database.
3838

@@ -46,7 +46,7 @@ Start your learning journey based on your source platform:
4646
> [Migrate a workload from AWS](./migrate-from-aws.yml)
4747
4848
> [!div class="nextstepaction"]
49-
> [Migrate a workload from Google Cloud](./migrate-from-google-cloud.yml)
49+
> [Migrate a workload from GCP](./migrate-from-google-cloud.yml)
5050
5151
This collection also includes guidance that applies to all platforms. All sections include such platform-agnostic guidance for convenience.
5252

@@ -56,6 +56,6 @@ In addition to content, you can explore specialized tools to assist with migrati
5656

5757
|Tool|Purpose|
5858
|---|---|
59-
|[Azure Migrate and Modernize](/azure/migrate/migrate-services-overview)| Analyze and assess migration assets, primarily infrastructure, applications, and data components. |
60-
|Azure Well-Architected Review assessment of the source platform, if available|Review and measure the business goals of your architecture on the source platform. This assessment helps you establish a baseline for your expectations on Azure.|
61-
|[Azure Well-Architected Review assessment](/assessments/azure-architecture-review/)| Evaluate your architecture decisions to identify any regressions from the source baseline. Also explore optimization opportunities to maximize performance on Azure.|
59+
|[Azure Migrate and Modernize](/azure/migrate/migrate-services-overview)| Discover and assess migration assets, primarily infrastructure, applications, and data components. |
60+
|Well-Architected Review assessment of the source platform, if available| Review and measure the business goals of your architecture on the source platform. This assessment helps you establish a baseline for your expectations on Azure.|
61+
|[Azure Well-Architected Review assessment](/assessments/azure-architecture-review/)| Evaluate your architecture decisions to identify any regressions from the source baseline. Also explore optimization opportunities to get the best on Azure.|

0 commit comments

Comments
 (0)