Recent Logic Apps Failures with Defender ATP Steps – "TimeGenerated" No Longer Recognized

Hi everyone,

I’ve recently encountered an issue with Logic Apps failing on Defender ATP steps. Requests containing the TimeGenerated parameter no longer work—the column seems to be unrecognized. My code hasn’t changed at all, and the same queries run successfully in Defender 365’s Advanced Hunting.

For example, this basic KQL query:

DeviceLogonEvents 
| where TimeGenerated >= ago(30d)
| where LogonType != "Local" 
| where DeviceName !contains ".fr" 
| where DeviceName !contains "shared-"
| where DeviceName !contains "gdc-" 
| where DeviceName !contains "mon-"
| distinct DeviceName

Now throws the error:
Failed to resolve column or scalar expression named 'TimeGenerated'. Fix semantic errors in your query.

Removing TimeGenerated makes the query work again, but this isn’t a viable solution. Notably, the identical query still functions in Defender 365’s Advanced Hunting UI.

This issue started affecting a Logic App that runs weekly—it worked on May 11th but failed on May 18th.

Questions:

1. Has there been a recent schema change or deprecation of TimeGenerated in Defender ATP's KQL for Logic Apps?
2. Is there an alternative column or syntax we should use now?
3. Are others experiencing this?

Any insights or workarounds would be greatly appreciated!