When attempting to save a cloud flow that includes the Advanced Hunting action from the Microsoft Defender ATP connector, the following error message appears and the save fails:
The response from API 'wdatp' operation 'AdvancedHuntingSchema' with status code '200' does not contain a valid OpenAPI schema object.
Although an HTTP status code of 200 (successful response) is being returned, Power Automate is unable to correctly interpret it as a valid OpenAPI schema, blocking the flow from being saved.
Based on the error message, it appears that the response (HTTP 200) returned by the wdatp connector's AdvancedHuntingSchema API may no longer conform to the OpenAPI schema specification that Power Automate expects.
Given that this same error now occurs even on flows that previously saved without issue, and that flows not using the wdatp connector are unaffected, the likely cause is either a change in the schema definition on the wdatp connector side (i.e., the Defender for Endpoint API side) or a change in the schema validation logic on the Power Automate platform side.
In any case, I believe this is a bug, but I am not sure whether it is specific to my environment or a widespread issue affecting users globally.

Report
All responses (
Answers (