Skip to content

Commit 6e5bbf7

Browse files
Update articles/defender-for-cloud/upcoming-changes.md
Co-authored-by: David Curwin <[email protected]>
1 parent 38d5261 commit 6e5bbf7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/defender-for-cloud/upcoming-changes.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ Following that, plan your migration plan according to your organization requirem
120120

121121
- If the following features are required in your organization: File Integrity Monitoring (FIM), Endpoint Protection recommendations, OS misconfigurations (security baselines recommendations), you can start retiring from MMA in April 2024 when an alternative will be delivered in GA (preview versions will be available earlier). 
122122

123-
- If the features mentioned above are required in your organization, and Azure Monitor agent (AMA) is required for other services as well, you can start migrating from MMA to AMA in April 2024. Alternately -use both MMA and AMA to get all features GA, then remove MMA in April 2024. 
123+
- If the features mentioned above are required in your organization, and Azure Monitor agent (AMA) is required for other services as well, you can start migrating from MMA to AMA in April 2024. Alternatively, use both MMA and AMA to get all GA features, then remove MMA in April 2024. 
124124

125125
- If the features mentioned above are not required, and Azure Monitor agent (AMA) is required for other services you can start migrating from MMA to AMA now. However, notice that the preview Defender for Servers capabilities over AMA will be deprecated in April 2024. 
126126

0 commit comments

Comments
 (0)