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
title: Migrate Networking from Amazon Web Services (AWS) to Azure
3
+
description: Learn about concepts, how-tos, and best practices for migrating networking services from Amazon Web Services (AWS) to Azure.
4
+
author: mbender-ms
5
+
ms.author: mbender
6
+
ms.reviewer: prwilk, chkittel
7
+
ms.date: 04/24/2025
8
+
ms.topic: conceptual
9
+
ms.collection:
10
+
- migration
11
+
- aws-to-azure
12
+
---
13
+
14
+
# Migrate networking from Amazon Web Services (AWS) to Azure
15
+
16
+
The articles listed on this page outline scenarios for how to migrate networking services from Amazon Web Services (AWS) to Azure networking services.
17
+
18
+
Networking services are foundational components of most enterprise workloads. The migration process moves these services while ensuring that they retain the same capabilities. Examples of networking services include virtual networks, load balancers, and firewalls that connect and protect critical data for various purposes. Whether it's to support custom applications, AI/ML training processes, business intelligence operations, or commercial off-the-shelf solutions, your networking infrastructure requires careful migration planning.
19
+
20
+
## Component comparison
21
+
22
+
Start the migration process by comparing the AWS networking service that's used in the workload with the closest Azure counterpart. The goal is to identify the most suitable Azure services for your workload. For more information, see [Comparing AWS and Azure networking services](/azure/architecture/aws-professional/networking).
23
+
24
+
> [!NOTE]
25
+
> This comparison isn't an exact representation of the functionality that these services provide in your workload.
26
+
27
+
## Migration guides
28
+
29
+
Use the following migration guides as examples to help structure your migration strategy.
30
+
31
+
| Scenario | Key services | Description |
32
+
|--|--|--|
33
+
|[Connect AWS and Azure using a BGP-enabled VPN gateway](/azure/vpn-gateway/vpn-gateway-howto-aws-bgp)| AWS virtual private gateway to Azure VPN gateway | Demonstrates how to set up a BGP-enabled connection between Azure and Amazon Web Services (AWS). |
34
+
35
+
## Related workload components
36
+
37
+
Networking makes up only part of your workload. Explore other components that you might migrate:
title: Migrate security services from Amazon Web Services (AWS)
3
+
description: Learn about replatforming security services from AWS to Microsoft Cloud to support the security requirements of the workload. Discover key similarities and differences between AWS and Microsoft.
4
+
ms.author: joflore
5
+
author: MicrosoftGuyJFlo
6
+
ms.date: 05/01/2025
7
+
ms.topic: conceptual
8
+
ms.collection:
9
+
- migration
10
+
- aws-to-azure
11
+
---
12
+
# Migrate security services from Amazon Web Services (AWS)
13
+
14
+
This article describes scenarios that you can use to migrate Amazon Web Services (AWS) security services to Microsoft Azure. These cloud services provide foundational security elements necessary for monitoring other services and applications built in the cloud. The migration process involves transitioning services while focusing on maintaining or enhancing functionality.
15
+
16
+
These scenarios might cover tasks like migrating your security and information and event management (SIEM) solution to Azure.
17
+
18
+
## Migration scenarios
19
+
20
+
Use the following migration guides as examples to help structure your migration strategy.
21
+
22
+
| Scenario | Key services | Description |
23
+
|--|--|--|
24
+
|[Migrate your SIEM in AWS to Microsoft Sentinel](/azure/sentinel/migration)| SIEM data in AWS -> Microsoft Sentinel | Plan the different phases of your SIEM data migration from AWS. |
25
+
26
+
## Related workload components
27
+
28
+
Security services make up only part of your cloud workload. Explore other components you might migrate:
29
+
30
+
-[Compute](migrate-compute-from-aws.md)
31
+
-[Databases](migrate-databases-from-aws.md)
32
+
-[Storage](migrate-storage-from-aws.md)
33
+
-[Networking](migrate-networking-from-aws.md)
34
+
35
+
Migrating security scenarios require identity to be a central service. Compare [AWS identity services](/azure/architecture/aws-professional/security-identity) used in the workload to their closest Azure counterparts.
0 commit comments