Skip to content

Commit 44ecd91

Browse files
Latest revisions
1 parent 98144c9 commit 44ecd91

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/migration/migrate-from-aws.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ landingContent:
3131
url: migrate-compute-from-aws.md
3232
- text: Migrate databases from AWS to Azure
3333
url: migrate-databases-from-aws.md
34+
- text: Migrate networking from AWS to Azure
35+
url: migrate-networking-from-aws.md
3436
- text: Migrate storage from AWS to Azure
3537
url: migrate-storage-from-aws.md
3638
- text: Migrate security from AWS to Azure

articles/migration/migrate-security-from-aws.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -11,19 +11,17 @@ ms.collection:
1111
---
1212
# Migrate security services from Amazon Web Services (AWS)
1313

14-
-- TODO: Need revision --
15-
This article describes scenarios that you can use to migrate Amazon Web Services (AWS) security services to Microsoft Azure and Microsoft Entra. These cloud services provide foundational elements necessary for services built on top of them. The migration process involves transitioning services while focusing on maintaining or enhancing functionality
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.
1615

17-
-- TODO: Need context for security --
18-
These scenarios cover common tasks like creating and maintaining users, enforcing multifactor authentication, managing device access, managing applications and secrets, and configuring other security tools.
16+
These scenarios might cover tasks like migrating your security and information and event management (SIEM) solution to Azure.
1917

2018
## Migration scenarios
2119

2220
Use the following migration guides as examples to help structure your migration strategy.
2321

2422
| Scenario | Key services | Description |
2523
|--|--|--|
26-
| [Migrate your SIEM in AWS to Microsoft Sentinel](/azure/sentinel/migration) | SIEM data in AWS -> Microsoft Sentinel | Discover the reasons for migrating from a legacy SIEM, and learn how to plan out the different phases of your migration. |
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. |
2725

2826
## Related workload components
2927

@@ -34,4 +32,4 @@ Security services make up only part of your cloud workload. Explore other compon
3432
- [Storage](migrate-storage-from-aws.md)
3533
- [Networking](migrate-networking-from-aws.md)
3634

37-
Migrating security scenarios require identity to be a central service. Compare AWS identity services used in the workload to their closest Azure counterparts.
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

Comments
 (0)