Does Microsoft Graph API Query support for Sharepoint on-premise Agent Connector

Nguyen Thi Ngoc Xuan 0 Reputation points
2026-11-18T14:05:50.39+00:00

I have some data in SharePoint On premises. Based on the Microsoft document, I used Agent Connector to index them. Then I tried some ways, grant recommended permissions to query the indexed data through Graph Explorer (https://graph.microsoft.com/v1.0/search/query). However, it doesn't work. Please help me!!

This is the bug enter image description here

{ "error": { "code": "BadRequest", "message": "An exception occurred", "target": "", "details": [ { "code": "BadRequest", "message": ", ", "target": "", "details": [ { "code": "BadRequest", "target": "", "details": [ { "code": "BadRequest", "target": "", "details": [ { "code": "GetConnectionSettingAsyncFailed", "message": "No connection setting found for the requested connections", "target": "", "serviceName": "Xap", "moduleName": "ResolveConnectionSettingPlugin", "contactTeam": "3sdri", "httpCode": 400 } ], "moduleName": "ConnectorSettingPreprocessingWorkflow", "httpCode": 400 } ], "moduleName": "ConnectorSettingPreprocessingWorkflow", "httpCode": 400 }, { "code": "InternalServerError", "message": "The call failed, please try again.", "target": "", "details": [ { "code": "InternalServerError", "message": "The call failed, please try again.", "target": "", "details": [ { "code": "ResolvingCandidatePropertiesValidationFailed", "message": "The call failed, please try again.", "target": "", "serviceName": "Xap", "moduleName": "ResolveManagedPropertiesPlugin", "contactTeam": "3sdri", "httpCode": 500 } ], "moduleName": "FlexibleSchemaSettingWorkflow", "httpCode": 500 }, { "code": "InternalServerError", "message": "The call failed, please try again.", "target": "", "details": [ { "code": "CreateSchemaScopeForConnectorRequestFailed", "message": "The call failed, please try again.", "target": "", "serviceName": "Xap", "moduleName": "FlexibleSchemaSettingsHelper", "contactTeam": "3sdri", "httpCode": 500 } ], "moduleName": "FlexibleSchemaSettingWorkflow", "httpCode": 500 }, { "code": "InternalServerError", "message": "The call failed, please try again.", "target": "", "details": [ { "code": "BuildFlexibleSchemaSettingItemPluginEmptySettings", "message": "The call failed, please try again.", "target": "", "serviceName": "Xap", "moduleName": "BuildFlexibleSchemaSettingItemPlugin", "contactTeam": "3sdri", "httpCode": 500 } ], "moduleName": "FlexibleSchemaSettingWorkflow", "httpCode": 500 } ], "moduleName": "FlexibleSchemaSettingWorkflow", "httpCode": 500 }, { "code": "BadRequest", "target": "", "details": [ { "code": "BadRequest", "target": "", "details": [ { "code": "PreprocessingFailure:Invalid Connector provider Request", "message": "Preprocessing failure detected in entity request", "target": "", "serviceName": "Xap", "moduleName": "ScdPreprocessingValidatorPlugin", "contactTeam": "3sdri", "httpCode": 400 } ], "moduleName": "ConnectorsPreprocessingMergerWorkflow", "httpCode": 400 } ], "moduleName": "ConnectorsPreprocessingMergerWorkflow", "httpCode": 400 } ], "moduleName": "ConnectorDiagnosticsMergerPlugin", "httpCode": 400 } ], "moduleName": "TopLevelWorkflowBase", "httpCode": 400 }, "Instrumentation": { "TraceId": "550eaca1-0853-738c-a0f1-7bc0136f9119" } }
Microsoft Security | Microsoft Graph
0 comments No comments

2 answers

Sort by: Most helpful
  1. Nguyen Thi Ngoc Xuan 0 Reputation points
    2026-11-18T15:03:23.9966667+00:00

    Hi @Liora , Thank you so much for supporting me. Base on ur recommendation:

    • I checked the agent connector in Microsoft 365, it indexed successfully. I set up the connector like this guide . https://learn.microsoft.com/en-us/microsoft-365/copilot/connectors/connector-agent
    • Then I try the graph explorer, list all available connectors. The SharePoint on-premises connector appears.
    • I also searched some document about this cases. No document states that they don't support it. Additionally, there is not much clear documentation for this situation. User's image

    Was this answer helpful?

    0 comments No comments

  2. Liora 3,775 Reputation points Independent Advisor
    2026-11-18T14:40:43.44+00:00

    Dear @Ngoc Xuan,

    Thank you for providing the request payload and error details.

    Based on the error:

    GetConnectionSettingAsyncFailed
    No connection setting found for the requested connections
    

    and

    PreprocessingFailure: Invalid Connector provider Request
    

    this does not appear to be a permissions issue in Graph Explorer. Instead, Microsoft Graph Search is unable to resolve the connection specified in:

    "/external/connections/OnPremisesSharePoint2611180233"
    

    I would recommend verifying the following:

    • Confirm that the connector has completed indexing successfully and that the content is searchable through Microsoft Search or Microsoft Copilot.
    • Verify that OnPremisesSharePoint2611180233 is the correct and active connection identifier exposed by the connector configuration.
    • Review the Agent Connector documentation to confirm whether the connector type you deployed supports querying content through: POST /v1.0/search/query using: "entityTypes": ["externalItem"]

    The error suggests that Graph Search cannot locate a valid external connection definition for the connection referenced in contentSources.

    Since this question is specifically related to Microsoft Graph Search API behavior and connector supportability, I would also recommend posting the same question in the Microsoft Graph community/forum. The Graph-focused community and engineers are more likely to have experience with the interaction between Agent Connectors, Graph Connectors, and the /search/query endpoint.

    I hope this information helps point you in the right direction.

    Warm regards,  


    If the answer is helpful, please select "Yes, accept answer". If you have any questions or new updates, please feel free to comment below.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.