Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
The articles listed on this page outline scenarios for how to migrate networking services from Amazon Web Services (AWS) to Azure networking services.
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.
Component comparison
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.
Note
This comparison isn't an exact representation of the functionality that these services provide in your workload.
Migration guides
Use the following migration guides as examples to help structure your migration strategy.
| Scenario | Key services | Description |
|---|---|---|
| Connect AWS and Azure using a BGP-enabled VPN gateway | AWS virtual private gateway to Azure VPN gateway | Demonstrates how to set up a BGP-enabled connection between Azure and Amazon Web Services (AWS). |
Related workload components
Networking makes up only part of your workload. Explore other components that you might migrate: