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/migration/migrate-to-azure.md
+8-8Lines changed: 8 additions & 8 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
2
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.
4
4
author: robbyatmicrosoft
5
5
ms.author: robbymillsap
6
6
ms.date: 03/24/2025
@@ -10,7 +10,7 @@ ms.custom: migration
10
10
11
11
# Migrate workloads to Azure from other cloud platforms
12
12
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.
14
14
15
15
> [!IMPORTANT]
16
16
>
@@ -20,7 +20,7 @@ Migration to Azure typically involves replatforming the workload, which includes
20
20
21
21
## Prerequisites for workload migrations
22
22
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:
24
24
25
25
- 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).
26
26
@@ -32,7 +32,7 @@ In the next phase, the workload team plans and implements the migration. They as
32
32
33
33
This collection applies to the following workload roles and functions at the team level.
34
34
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.
36
36
37
37
-**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.
38
38
@@ -46,7 +46,7 @@ Start your learning journey based on your source platform:
46
46
> [Migrate a workload from AWS](./migrate-from-aws.yml)
47
47
48
48
> [!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)
50
50
51
51
This collection also includes guidance that applies to all platforms. All sections include such platform-agnostic guidance for convenience.
52
52
@@ -56,6 +56,6 @@ In addition to content, you can explore specialized tools to assist with migrati
56
56
57
57
|Tool|Purpose|
58
58
|---|---|
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