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
Please provide the following (and please check them off the list with [x]) before submitting this issue:
Expected behavior. Please provide links to the specific Microsoft Graph documentation you used to determine the expected behavior.
Actual behavior. Provide error codes, stack information, and a Fiddler capture of the request and response (please remove personally identifiable information before posting).
Steps to reproduce the behavior. Include your code, IDE versions, client library versions, and any other information that might be helpful to understand your scenario.
Expected behavior
Post call to run hunting queries should work as expected.
Actual behavior
Calls fail with the oDataError (using Graph v5 nuget) with code '400' and message 'Resource not found for segment 'security.runHuntingQuery''
Steps to reproduce the behavior
try {
var requestBody = new RunHuntingQueryPostRequestBody() { Query = "" };
var queryResults = await new GraphServiceClient().Security.SecurityRunHuntingQuery.PostAsync(requestBody, cancellationToken: cancellationToken).ConfigureAwait(false);
}
catch (oDataError error) {
}
The text was updated successfully, but these errors were encountered:
Please provide the following (and please check them off the list with [x]) before submitting this issue:
Expected behavior
Post call to run hunting queries should work as expected.
Actual behavior
Calls fail with the oDataError (using Graph v5 nuget) with code '400' and message 'Resource not found for segment 'security.runHuntingQuery''
Steps to reproduce the behavior
try {
var requestBody = new RunHuntingQueryPostRequestBody() { Query = "" };
var queryResults = await new GraphServiceClient().Security.SecurityRunHuntingQuery.PostAsync(requestBody, cancellationToken: cancellationToken).ConfigureAwait(false);
}
catch (oDataError error) {
}
The text was updated successfully, but these errors were encountered: