Skip to content

Commit bffb3c6

Browse files
authored
Merge pull request #297439 from Court72/seo-migrate-articles
Quality check: Convert and edit AWS Lambda to Azure Functions Migration Guide
2 parents df4a785 + 187040a commit bffb3c6

File tree

6 files changed

+39
-13
lines changed

6 files changed

+39
-13
lines changed

.openpublishing.redirection.json

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6759,5 +6759,30 @@
67596759
"redirect_url": "/azure/sentinel/work-with-stix-objects-indicators",
67606760
"redirect_document_id": false
67616761
},
6762+
{
6763+
"source_path_from_root": "/articles/azure-functions/migration.md",
6764+
"redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads-overview",
6765+
"redirect_document_id": false
6766+
},
6767+
{
6768+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-assess.md",
6769+
"redirect_url": "/azure/azure-functions/migration/assess-lambda-workloads",
6770+
"redirect_document_id": false
6771+
},
6772+
{
6773+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-discover.md",
6774+
"redirect_url": "/azure/azure-functions/migration/discover-lambda-workloads",
6775+
"redirect_document_id": false
6776+
},
6777+
{
6778+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-migrate.md",
6779+
"redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads",
6780+
"redirect_document_id": false
6781+
},
6782+
{
6783+
"source_path": "articles/azure-functions/migration/lambda-functions-migration-overview.md",
6784+
"redirect_url": "/azure/azure-functions/migration/migrate-lambda-workloads-overview",
6785+
"redirect_document_id": false
6786+
},
67626787
]
67636788
}

articles/azure-functions/TOC.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -737,16 +737,16 @@
737737
- name: Migrate from AWS Lambda
738738
items:
739739
- name: Overview
740-
href: migration/lambda-functions-migration-overview.md
740+
href: migration/migrate-lambda-workloads-overview.md
741741
displayName: AWS Lambda, migration
742742
- name: Discover
743-
href: migration/lambda-functions-migration-discover.md
743+
href: migration/discover-lambda-workloads.md
744744
displayName: AWS Lambda, migration
745745
- name: Assess
746-
href: migration/lambda-functions-migration-assess.md
746+
href: migration/assess-lambda-workloads.md
747747
displayName: AWS Lambda, migration
748748
- name: Migrate
749-
href: migration/lambda-functions-migration-migrate.md
749+
href: migration/migrate-lambda-workloads.md
750750
displayName: AWS Lambda, migration
751751
- name: Upgrade runtime versions
752752
items:

articles/azure-functions/migration/lambda-functions-migration-assess.md renamed to articles/azure-functions/migration/assess-lambda-workloads.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Stage 2: Assess Workloads to Migrate from AWS Lambda to Azure Functions"
2+
title: Assess AWS Lambda Workloads to Migrate to Azure Functions
33
description: Learn how to map AWS Lambda features to Azure Functions and develop a plan for your AWS Lambda to Azure Functions migration.
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar
@@ -181,4 +181,4 @@ By the end of this stage, you've mapped AWS Lambda features and services to thei
181181
## Next step
182182

183183
> [!div class="nextstepaction"]
184-
> [Migrate stage](lambda-functions-migration-migrate.md)
184+
> [Migrate stage](migrate-lambda-workloads.md)

articles/azure-functions/migration/lambda-functions-migration-discover.md renamed to articles/azure-functions/migration/discover-lambda-workloads.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Stage 1: Discover Workloads to Migrate from AWS Lambda to Azure Functions"
2+
title: Discover AWS Lambda Workloads to Migrate to Azure Functions
33
description: Learn how to conduct a detailed discovery process to inventory current AWS Lambda workloads, including their configuration, dependencies, and usage patterns.
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar
@@ -11,7 +11,7 @@ ms.date: 03/18/2025
1111

1212
# Stage 1: Discover workloads to migrate from AWS Lambda to Azure Functions
1313

14-
In this stage, you conduct a detailed discovery process to evaluate existing AWS Lambda workloads, including their configuration, dependencies, and usage patterns.
14+
In this stage, you conduct a detailed discovery process to evaluate existing AWS Lambda workloads, including their configuration, dependencies, and usage patterns. The goal is to understand which AWS features and services your workload relies on.
1515

1616
## Evaluate your current workload
1717

@@ -36,6 +36,7 @@ Compile a comprehensive inventory of your AWS Lambda functions by using familiar
3636
- Identify virtual private cloud configurations, including subnets, security groups, and NAT gateway dependencies, if applicable.
3737

3838
### Tooling
39+
3940
- List the continuous integration and continuous delivery tools and deployment frameworks that each function uses, such as AWS SAM, Serverless Framework, or custom pipelines.
4041

4142
- Document build and packaging tools, including testing frameworks and staging workflows.
@@ -73,4 +74,4 @@ This detailed inventory is the foundation for the next stage, where you assess t
7374
## Next step
7475

7576
> [!div class="nextstepaction"]
76-
> [Assess stage](lambda-functions-migration-assess.md)
77+
> [Assess stage](assess-lambda-workloads.md)

articles/azure-functions/migration/lambda-functions-migration-overview.md renamed to articles/azure-functions/migration/migrate-lambda-workloads-overview.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ ms.date: 03/18/2025
1111

1212
# Migrate AWS Lambda to Azure Functions
1313

14-
This article provides an overview of how to migrate serverless applications from AWS Lambda to Azure Functions.
14+
This article provides an overview of how to migrate serverless applications from AWS Lambda to Azure Functions. Learn about Functions features, and understand the stages of migration so that you can migrate your workload efficiently.
1515

16-
## Introduction to Azure Functions
16+
## Introduction to Azure Functions
1717

1818
Azure Functions provides serverless compute resources in Azure by enabling you to run event-driven code without provisioning or managing infrastructure. The Flex Consumption hosting plan for Functions is equivalent to Lambda's consumption-based model. It provides network integration to meet enterprise governance needs alongside serverless implementation. AWS Lambda and Azure Functions share similar features like automatic resource provisioning, scaling, and pay-per-use pricing models. Functions also supports dedicated hosting modes, taking advantage of its highly portable runtime to run in various environments. Functions provides unique benefits, such as a versatile programming model that has rich triggers and bindings, scaling models, concurrency control, and runtime support.
1919
@@ -46,4 +46,4 @@ During this stage, you perform these steps to adapt function code, deploy and te
4646
Let's get started migrating your AWS Lambda code to Azure Functions:
4747

4848
> [!div class="nextstepaction"]
49-
> [Discover stage](lambda-functions-migration-discover.md)
49+
> [Discover stage](discover-lambda-workloads.md)

articles/azure-functions/migration/lambda-functions-migration-migrate.md renamed to articles/azure-functions/migration/migrate-lambda-workloads.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Stage 3: Migrate Workloads from AWS Lambda to Azure Functions"
2+
title: Migrate Workloads from AWS Lambda to Azure Functions
33
description: Learn about the steps to complete your AWS Lambda to Azure Functions migration, test performance, optimize operations, and implement monitoring.
44
author: MadhuraBharadwaj-MSFT
55
ms.author: mabhar

0 commit comments

Comments
 (0)