Skip to content

Commit d1d377c

Browse files
Merge pull request #4499 from MicrosoftDocs/main
[AutoPublish] main to live - 07/15 10:32 PDT | 07/15 23:02 IST
2 parents adeec68 + cc02a70 commit d1d377c

File tree

3 files changed

+39
-12
lines changed

3 files changed

+39
-12
lines changed

ATPDocs/identity-inventory.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ The **Identities** list offers a consolidated view of identities across Active D
7676

7777
- __Last updated__ – The timestamp of the most recent update to the identity's attributes in Active Directory.
7878

79-
Nondefault columns: Email and Microsoft Entra ID risk level.  
79+
Nondefault columns: Email, Microsoft Entra ID risk level and Cloud ID.
8080

8181
> [!TIP]
8282
> To see all columns, you likely need to do one or more of the following steps:

CloudAppSecurityDocs/caac-known-issues.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -114,6 +114,35 @@ A user who starts a session in Edge with a profile other than his work profile,
114114

115115
If the URL points to a resource within the secured application, the user will be directed to the application's homepage in Edge.
116116

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+
117146
## Related content
118147

119148
- [Conditional Access app control in Microsoft Defender for Cloud Apps](proxy-intro-aad.md)

defender-xdr/advanced-hunting-defender-use-custom-rules.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -65,9 +65,9 @@ For example, to get the first 10 rows of data from the `StormEvents` table store
6565
### Use arg() operator for Azure Resource Graph queries
6666
The `arg()` operator can be used to query across deployed Azure resources like subscriptions, virtual machines, CPU, storage, and the like.
6767

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.
6969

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).
7171

7272
In the query editor, enter *arg("").* followed by the Azure Resource Graph table name.
7373

@@ -78,14 +78,12 @@ For example:
7878
You can also, for instance, filter a query that searches over Microsoft Sentinel data based on the results of an Azure Resource Graph query:
7979

8080
```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
8987
```
9088

9189

@@ -141,4 +139,4 @@ You can view all your user-defined rules—both custom detection rules and analy
141139

142140

143141
For multiworkspace organizations that have onboarded multiple workspaces to Microsoft Defender, you can now view the **Workspace ID** column and filter by workspace.
144-
142+

0 commit comments

Comments
 (0)