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
+9-5Lines changed: 9 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,15 +16,19 @@ This content collection is curated to help workload teams plan and implement the
16
16
>
17
17
> Some migration scenarios are out of scope for this collection. It doesn't cover on-premises to Azure migrations, full datacenter migrations, or region relocations. It also doesn't address workloads that concurrently run on multiple clouds.
18
18
19
-
Migration to Azure typically involves replatforming the workload, which includes transitioning both the infrastructure and management layer from the source cloud provider to Azure. During the migration process, you need to find the best match for your source components on Azure. Not all components have direct equivalents. To accomplish your business objectives, you might need to redesign the architecture or revisit code to maintain functionality. This collection provides valuable insights into such cloud-to-cloud transitions because it compares workload components and services, and includes example migration scenarios.
19
+
Migration to Azure typically involves _replatforming the workload_, which includes transitioning both the infrastructure and management layer from the source cloud provider to Azure. To prepare for the migration process, you need to find the best match for your source components on Azure. Keep in mind that not all components have direct equivalents. You'll need to redesign the architecture or revisit code to maintain functionality and accomplish your business objectives. This collection offers comparisons of the typical workload components and platform services, and includes example migration scenarios.
20
20
21
21
## Prerequisites for workload migrations
22
22
23
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
-
- 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).
25
+
- Learn about terms used in Azure and how the concepts relate to one another.
26
+
27
+
[**Azure fundamental concepts**](/azure/cloud-adoption-framework/ready/considerations/fundamental-concepts)
26
28
27
-
- To develop your organization's migration plan and identify the types of workloads that you should migrate, see the training module, [Use the Cloud Adoption Framework Migrate methodology to migrate your workload to the cloud](/training/modules/cloud-adoption-framework-migrate/).
29
+
- Complete the learning objectives in the training module to develop your organization's migration plan and identify the types of workloads that need to be migrated.
30
+
31
+
[**Learn about the Cloud Adoption Framework Migrate methodology**](/training/modules/cloud-adoption-framework-migrate/)
28
32
29
33
In the next phase, the workload team plans and implements the migration. They assess the current workload design, prepare a solution in Azure, make necessary code changes, and perform the migration.
30
34
@@ -38,7 +42,7 @@ This collection applies to the following workload roles and functions at the tea
38
42
39
43
## Content layout
40
44
41
-
The migration guide content is organized by platform, starting with your source platform. Each platform includes comparison articles. To get started, compare the capabilities of your workload and its services with their closest Azure counterparts. These articles also include example scenarios and service-level migration guides to illustrate the comparisons.
45
+
The migration guide content is categorized by the source platform on which your workload currently runs. Each category includes comparison articles. To get started, compare the capabilities of your workload and its services with their closest Azure counterparts. These articles also include example scenarios and service-level migration guides to illustrate the comparisons.
42
46
43
47
Start your learning journey based on your source platform:
44
48
@@ -48,7 +52,7 @@ Start your learning journey based on your source platform:
48
52
> [!div class="nextstepaction"]
49
53
> [Migrate a workload from GCP](./migrate-from-google-cloud.yml)
50
54
51
-
This collection also includes guidance that applies to all platforms. All sections include such platform-agnostic guidance for convenience.
55
+
This collection also includes articles that apply to all platforms. All sections include such platform-agnostic articles for convenience.
0 commit comments