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
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/upcoming-changes.md
+1-44Lines changed: 1 addition & 44 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Important changes coming to Microsoft Defender for Cloud
3
3
description: Upcoming changes to Microsoft Defender for Cloud that you might need to be aware of and for which you might need to plan
4
4
ms.topic: overview
5
-
ms.date: 05/02/2023
5
+
ms.date: 05/07/2023
6
6
---
7
7
8
8
# Important upcoming changes to Microsoft Defender for Cloud
@@ -19,7 +19,6 @@ If you're looking for the latest release notes, you can find them in the [What's
19
19
| Planned change | Estimated date for change |
20
20
|--|--|
21
21
|[Deprecation of legacy compliance standards across cloud environments](#deprecation-of-legacy-compliance-standards-across-cloud-environments)| April 2023 |
22
-
|[Multiple changes to identity recommendations](#multiple-changes-to-identity-recommendations)| May 2023 |
23
22
|[Release of containers Vulnerability Assessment powered by Microsoft Defender Vulnerability Management (MDVM) in Defender CSPM](#release-of-containers-vulnerability-assessment-powered-by-microsoft-defender-vulnerability-management-mdvm-in-defender-cspm)| May 2023 |
24
23
|[Renaming container recommendations powered by Qualys](#renaming-container-recommendations-powered-by-qualys)| May 2023 |
25
24
|[DevOps Resource Deduplication for Defender for DevOps](#devops-resource-deduplication-for-defender-for-devops)| June 2023 |
@@ -35,48 +34,6 @@ We're announcing the full deprecation of support of [PCI DSS](/azure/compliance/
35
34
36
35
Learn how to [Customize the set of standards in your regulatory compliance dashboard](update-regulatory-compliance-packages.md).
37
36
38
-
#### Deprecation of identity recommendations V1
39
-
40
-
The following security recommendations will be deprecated as part of this change:
41
-
42
-
| Recommendation | Assessment Key |
43
-
|--|--|
44
-
| MFA should be enabled on accounts with owner permissions on subscriptions | 94290b00-4d0c-d7b4-7cea-064a9554e681 |
45
-
| MFA should be enabled on accounts with write permissions on subscriptions | 57e98606-6b1e-6193-0e3d-fe621387c16b |
46
-
| MFA should be enabled on accounts with read permissions on subscriptions | 151e82c5-5341-a74b-1eb0-bc38d2c84bb5 |
47
-
| External accounts with owner permissions should be removed from subscriptions | c3b6ae71-f1f0-31b4-e6c1-d5951285d03d |
48
-
| External accounts with write permissions should be removed from subscriptions | 04e7147b-0deb-9796-2e5c-0336343ceb3d |
49
-
| External accounts with read permissions should be removed from subscriptions | a8c6a4ad-d51e-88fe-2979-d3ee3c864f8b |
50
-
| Deprecated accounts with owner permissions should be removed from subscriptions | e52064aa-6853-e252-a11e-dffc675689c2 |
51
-
| Deprecated accounts should be removed from subscriptions | 00c6d40b-e990-6acf-d4f3-471e747a27c4 |
52
-
53
-
We recommend updating custom scripts, workflows, and governance rules to correspond with the V2 recommendations.
54
-
55
-
We've improved the coverage of the V2 identity recommendations by scanning all Azure resources (rather than just subscriptions) which allows security administrators to view role assignments per account. These changes may result in changes to your Secure Score throughout the GA process.
56
-
57
-
### Multiple changes to identity recommendations
58
-
59
-
**Estimated date for change: May 2023**
60
-
61
-
We announced previously the [availability of identity recommendations V2 (preview)](release-notes-archive.md#extra-recommendations-added-to-identity), which included enhanced capabilities.
62
-
63
-
As part of these changes, the following recommendations will be released as General Availability (GA) and replace the V1 recommendations that are set to be deprecated.
64
-
65
-
#### General Availability (GA) release of identity recommendations V2
66
-
67
-
The following security recommendations will be released as GA and replace the V1 recommendations:
68
-
69
-
|Recommendation | Assessment Key|
70
-
|--|--|
71
-
|Accounts with owner permissions on Azure resources should be MFA enabled | 6240402e-f77c-46fa-9060-a7ce53997754 |
72
-
|Accounts with write permissions on Azure resources should be MFA enabled | c0cb17b2-0607-48a7-b0e0-903ed22de39b |
73
-
| Accounts with read permissions on Azure resources should be MFA enabled | dabc9bc4-b8a8-45bd-9a5a-43000df8aa1c |
74
-
| Guest accounts with owner permissions on Azure resources should be removed | 20606e75-05c4-48c0-9d97-add6daa2109a |
75
-
| Guest accounts with write permissions on Azure resources should be removed | 0354476c-a12a-4fcc-a79d-f0ab7ffffdbb |
76
-
| Guest accounts with read permissions on Azure resources should be removed | fde1c0c9-0fd2-4ecc-87b5-98956cbc1095 |
77
-
| Blocked accounts with owner permissions on Azure resources should be removed | 050ac097-3dda-4d24-ab6d-82568e7a50cf |
78
-
| Blocked accounts with read and write permissions on Azure resources should be removed | 1ff0b4c9-ed56-4de6-be9c-d7ab39645926 |
79
-
80
37
### Release of containers Vulnerability Assessment powered by Microsoft Defender Vulnerability Management (MDVM) in Defender CSPM
0 commit comments