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/caac-known-issues.md
+29Lines changed: 29 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -114,6 +114,35 @@ A user who starts a session in Edge with a profile other than his work profile,
114
114
115
115
If the URL points to a resource within the secured application, the user will be directed to the application's homepage in Edge.
116
116
117
+
### Outdated session policy enforcement with Edge
118
+
When a session policy is enforced using Edge in-browser protection and the user is later removed from the corresponding Conditional Access (CA) policy, the original session enforcement may still persist.
119
+
120
+
Example Scenario:
121
+
122
+
A user was originally assigned a CA policy for the Salesforce application, along with an Defender for Cloud apps session policy that blocked file downloads. As a result, downloads were blocked when the user accessed Salesforce in Edge.
123
+
124
+
Although the admin later removed the CA policy, the user still experiences the download block in Edge due to cached policy data.
125
+
126
+
Mitigation Options:
127
+
128
+
Option 1: Automatic cleanup
129
+
1. Reassign the user/app to the CA policy.
130
+
2. Remove the corresponding Defender for Cloud Apps session policy.
131
+
3. Have the user access the application using Edge, this will trigger the policy removal automatically.
132
+
4. Remove the CA policy again.
133
+
134
+
Option 2: Manual cleanup
135
+
1. Delete the cached policy file
136
+
- Go to: C:\Users\<username>\AppData\Local\Microsoft\Edge\
137
+
- Delete the file: mda_store.txt
138
+
139
+
2. Remove the work profile in Edge
140
+
- Open Microsoft Edge.
141
+
- Navigate to Profile Settings.
142
+
- Delete the work profile associated with the outdated session policy.
143
+
144
+
These steps will force a policy refresh and resolve enforcement issues related to outdated session policies.
145
+
117
146
## Related content
118
147
119
148
-[Conditional Access app control in Microsoft Defender for Cloud Apps](proxy-intro-aad.md)
Copy file name to clipboardExpand all lines: defender-xdr/advanced-hunting-defender-use-custom-rules.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,9 +65,9 @@ For example, to get the first 10 rows of data from the `StormEvents` table store
65
65
### Use arg() operator for Azure Resource Graph queries
66
66
The `arg()` operator can be used to query across deployed Azure resources like subscriptions, virtual machines, CPU, storage, and the like.
67
67
68
-
This feature was previously only available in log analytics in Microsoft Sentinel. In the Microsoft Defender portal, the `arg()` operator works over Microsoft Sentinel data (that is, Defender XDR tables aren't supported). This allows users to use the operator in advanced hunting without needing to manually open a Microsoft Sentinel window.
68
+
This feature was previously only available in the Logs feature in Microsoft Sentinel. In the Microsoft Defender portal, the `arg()` operator works to combine Azure Resource Graph (arg) queries with Microsoft Sentinel tables (that is, Defender XDR tables aren't supported). This allows users to make the cross-service query in advanced hunting without manually opening a Microsoft Sentinel window.
69
69
70
-
Note that queries using the `arg()` operator return the first 1,000 records only. Read [Query data in Azure Resource Graph by using arg()](/azure/azure-monitor/logs/azure-monitor-data-explorer-proxy#query-data-in-azure-resource-graph-by-using-arg-preview) for more details.
70
+
For more information, see [Query data in Azure Resource Graph by using arg()](/azure/azure-monitor/logs/azure-monitor-data-explorer-proxy#query-data-in-azure-resource-graph-by-using-arg-preview).
71
71
72
72
In the query editor, enter *arg("").* followed by the Azure Resource Graph table name.
73
73
@@ -78,14 +78,12 @@ For example:
78
78
You can also, for instance, filter a query that searches over Microsoft Sentinel data based on the results of an Azure Resource Graph query:
79
79
80
80
```Kusto
81
-
arg("").Resources
82
-
| where type == "microsoft.compute/virtualmachines" and properties.hardwareProfile.vmSize startswith "Standard_D"
83
-
| join (
84
-
Heartbeat
85
-
| where TimeGenerated > ago(1d)
86
-
| distinct Computer
87
-
)
88
-
on $left.name == $right.Computer
81
+
arg("").Resources
82
+
| where type=="microsoft.compute/virtualmachines" | extend name = tolower(name)
83
+
| join (
84
+
BehaviorAnalytics
85
+
| where isnotempty(SourceDevice) and InvestigationPriority > 2 | extend SourceDevice = tolower(SourceDevice)
86
+
) on $left.name == $right.SourceDevice
89
87
```
90
88
91
89
@@ -141,4 +139,4 @@ You can view all your user-defined rules—both custom detection rules and analy
141
139
142
140
143
141
For multiworkspace organizations that have onboarded multiple workspaces to Microsoft Defender, you can now view the **Workspace ID** column and filter by workspace.
0 commit comments