Microsoft Defender XDR: InitiatingProcessFolderPath changes to include file names
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Action date
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions we saw- Seen 5 Nov 2024
November 4, 2024→ November 18, 2024
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, safely structuredUpdated November 5, 2024: We have updated the rollout timeline below. Thank you for your patience.
Coming soon: Microsoft Defender for Endpoint will modify the InitiatingProcessFolderPath column across all relevant Advanced Hunting tables to include the initiating process file name. This message applies to Windows activity only.
When this will happen
General Availability (Worldwide): We will roll out to all Microsoft Defender for Endpoint customers on November 18, 2024 (previously November 4).
How this will affect your organization
Before this rollout, the InitiatingProcessFolderPath column is inconsistent across action types. Some columns include the file name, and other columns do not include the file name.
After the rollout, all Microsoft Defender for Endpoint action types across all tables will report the full path including the file name of the initiating process in the InitiatingProcessFolderPath column.
Consider the following example to be the new normal, InitiatingProcessFolderPath == c:\temp\file.exe
An example of a possible current implementation that will be retired with this change: InitiatingProcessFolderPath == c:\temp\
Custom detection rules and queries considering the InitiatingProcessFolderPath may be affected.
If you know your custom detection rules or Advanced Hunting queries include this column, please modify them to consider the new convention:
- To modify your custom detection rules, go to the Defender portal > Investigation & response > Hunting > Custom detection rules
- To modify other Advanced Hunting queries, go to the Defender portal > Investigation & response > Hunting > Advanced hunting
To learn more, go to the Shema reference button in the top right of the Advanced hunting page.
This change is on by default.
What you need to do to prepare
Before November 4, 2024, map your affected custom detection rules and KQL functions and prepare a fix. Where possible, we recommend updating your queries before the release.
This rollout will happen automatically by the specified date. You may want to notify your admins about this change and update any relevant documentation.
What changed
Between archive captures, newest first- Tags
Feature update, Admin impact→ Updated message, Feature update, Admin impact
Updated November 5, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Defender for Endpoint will modify the InitiatingProcessFolderPath column across … will roll out to all Microsoft Defender for Endpoint customers on November
4, 2024.18, 2024 (previously November 4). How this will affect your organization: Before this rollout, the InitiatingProcessFolderPath column …- Tags
- · first version seen
Related public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.