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: CloudAppSecurityDocs/release-notes.md
+15-15Lines changed: 15 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ For news about earlier releases, see [Archive of past updates for Microsoft Defe
33
33
34
34
The new Applications page in Microsoft Defender XDR provides a unified inventory of all SaaS and connected OAuth applications across your environment. This view helps streamline application discovery, monitoring, and risk assessment.
35
35
36
-
For more details, see [Application inventory overview](applications-inventory.md).
36
+
For more information, see [Application inventory overview](applications-inventory.md).
37
37
38
38
### New and improved Cloud App Catalog page
39
39
@@ -94,7 +94,7 @@ For more information, see:
94
94
95
95
The new *Permissions filter and export capabilities allow you to quickly identify apps with specific permissions to access Microsoft 365.
96
96
97
-
You can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights enable you to get deeper visibility into apps accessing emails using legacy EWS API.
97
+
You can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights enables you to get deeper visibility into apps accessing emails using legacy EWS API.
98
98
99
99
We're also expanding the coverage of privilege level feature for all popular Microsoft first-party API permissions. The enhanced coverage of privilege level classification enables you to view and monitor apps with powerful permissions into legacy and other non-Graph APIs that have access to Microsoft 365.
100
100
@@ -151,7 +151,7 @@ For more information, see:
151
151
152
152
The Enterprise application 'Microsoft Defender for Cloud Apps – Session Controls' is used internally by the Conditional Access App Control service.
153
153
Ensure there's no CA policy restricting access to this application.
154
-
For policies that restrict all or certain applications, please ensure this application is listed as an exception or confirm that the blocking policy is deliberate.
154
+
For policies that restrict all or certain applications, ensure this application is listed as an exception or confirm that the blocking policy is deliberate.
155
155
156
156
For more information, see [Sample: Create Microsoft Entra ID Conditional Access policies for use with Defender for Cloud Apps](session-policy-aad.md#sample-create-microsoft-entra-id-conditional-access-policies-for-use-with-defender-for-cloud-apps).
157
157
@@ -167,7 +167,7 @@ For more information, see:
167
167
### SaaS Security initiative in Exposure Management
168
168
169
169
[Microsoft Security Exposure Management](/security-exposure-management/) offers a focused, metric-driven way of tracking exposure in specific security areas using security [initiatives](/security-exposure-management/initiatives). The "SaaS security initiative" provides a centralized location for all best practices related to SaaS security, categorized into 12 measurable metrics. These metrics are designed to assist in effectively managing and prioritizing the large number of security recommendations.
170
-
This capability is General Availability (Worldwide) - Note Microsoft Security Exposure Management data and capabilities are currently unavailable in U.S Government clouds - GCC, GCC High and DoD
170
+
This capability is General Availability (Worldwide) - Note Microsoft Security Exposure Management data and capabilities are currently unavailable in U.S Government clouds - GCC, GCC High, and DoD
171
171
172
172
For more information, see [SaaS security initiative](saas-security-initiative.md).
173
173
@@ -185,13 +185,13 @@ For more information, see [filters on app governance](/defender-cloud-apps/app-g
185
185
186
186
### Visibility into privilege level for popular Microsoft first-party APIs (Preview)
187
187
188
-
Defender for Cloud Apps users who use app governance can now gain visibility into privilege level for all popular Microsoft first-party API permissions. The enhanced coverage of privilege level classification will enable you to view and monitor apps with powerful permissions into legacy and other non-Graph APIs that have access to Microsoft 365.
188
+
Defender for Cloud Apps users who use app governance can now gain visibility into privilege level for all popular Microsoft first-party API permissions. The enhanced coverage of privilege level classification enables you to view and monitor apps with powerful permissions into legacy and other non-Graph APIs that have access to Microsoft 365.
189
189
190
190
For more information, see [OAuth app permission related details on app governance](/defender-cloud-apps/app-governance-visibility-insights-view-apps#getting-detailed-information-on-an-app).
191
191
192
192
### Granular data usage insights into EWS API access (Preview)
193
193
194
-
Defender for Cloud Apps users who use app governance can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights will enable you to get deeper visibility into apps accessing emails using legacy EWS API.
194
+
Defender for Cloud Apps users who use app governance can now get granular insights into data accessed by apps using legacy EWS API alongside Microsoft Graph. The enhanced coverage of data usage insights enable you to get deeper visibility into apps accessing emails using legacy EWS API.
195
195
196
196
For more information, see [OAuth app data usage insights on app governance](/defender-cloud-apps/app-governance-visibility-insights-view-apps#getting-detailed-information-on-an-app).
197
197
@@ -200,7 +200,7 @@ For more information, see [OAuth app data usage insights on app governance](/def
200
200
### New anomaly data in advanced hunting CloudAppEvents table
201
201
202
202
Defender for Cloud Apps users who use advanced hunting in the Microsoft Defender portal, can now utilize the new *LastSeenForUser* and *UncommonForUser* columns for queries and detections rules.
203
-
The new columns are designed to assist you to better __identify uncommon activities__ that may appear suspicious, and allow you to create more accurate custom detections, as well as investigate any suspicious activities that arise.
203
+
The new columns are designed to assist you to better __identify uncommon activities__ that might appear suspicious, and allow you to create more accurate custom detections, and investigate any suspicious activities that arise.
204
204
205
205
For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/microsoft-365/security/defender/advanced-hunting-cloudappevents-table).
206
206
@@ -221,13 +221,13 @@ For more information, see [Advanced Hunting "CloudAppEvents" Data schema](/micro
221
221
222
222
## September 2024
223
223
224
-
### Enforce Edge in-browser when accessing business apps
224
+
### Enforce Microsoft Edge in-browser when accessing business apps
225
225
226
-
Administrators who understand the power of Edge in-browser protection, can now require their users to use Edge when accessing corporate resources.
226
+
Administrators who understand the power of Microsoft Edge in-browser protection, can now require their users to use Microsoft Edge when accessing corporate resources.
227
227
228
-
A primary reason is security, since the barrier to circumventing session controls using Edge is much higher than with reverse proxy technology.
228
+
A primary reason is security, since the barrier to circumventing session controls using Microsoft Edge is higher than with reverse proxy technology.
229
229
230
-
For more information, see [Enforce Edge in-browser protection when accessing business apps](in-browser-protection.md#enforce-microsoft-edge-browser-protection-when-accessing-business-apps).
230
+
For more information, see [Enforce Microsoft Edge in-browser protection when accessing business apps](in-browser-protection.md#enforce-microsoft-edge-browser-protection-when-accessing-business-apps).
231
231
232
232
### Connect Mural to Defender for Cloud Apps (Preview)
233
233
@@ -242,13 +242,13 @@ For more information, see:
242
242
243
243
### Removing the ability to email end users about blocked actions
244
244
245
-
Effective October 1st, 2024, we will discontinue the feature that notifies end users via email when their action is blocked by session policies.
245
+
Effective October 1, 2024, we'll discontinue the feature that notifies end users via email when their action is blocked by session policies.
246
246
247
247
This option ensures that if a user's action is blocked, they get both a browser message and an email notification.
248
248
249
249
Admins can no longer configure this setting when creating new session policies.
250
250
251
-
Existing session policies with this setting will not trigger email notifications to end users when a block action occurs.
251
+
Existing session policies with this setting won't trigger email notifications to end users when a block action occurs.
252
252
253
253
End users will continue to receive the block message directly through the browser and will stop receiving block notification via email.
254
254
@@ -287,7 +287,7 @@ For more information, see [Configure custom URL for MDA block pages](mde-govern.
287
287
288
288
### In-browser protection for macOS users and newly supported policies (Preview)
289
289
290
-
Edge browser users from macOS who are scoped to session policies are now protected with in-browser protection.
290
+
Microsoft Edge browser users from macOS who are scoped to session policies are now protected with in-browser protection.
291
291
292
292
The following session policies are now supported:
293
293
@@ -298,7 +298,7 @@ The following session policies are now supported:
298
298
299
299
See [In-browser protection](in-browser-protection.md).
300
300
301
-
In-browser protection is supported with the last 2 stable versions of Edge (for example, if the newest Edge is 126, in-browser protection works for v126 and v125).
301
+
In-browser protection is supported with the last two stable versions of Microsoft Edge (for example, if the newest Microsoft Edge is 126, in-browser protection works for v126 and v125).
302
302
303
303
See [Microsoft Edge releases](/deployedge/microsoft-edge-release-schedule#microsoft-edge-releases).
0 commit comments