Provenance None is not supported for conversion to ContentSource - System.NotSupportedException - POST to graph.microsoft.com/v1.0/search/query

Question

I'm using graph API v1.0 to query our Sharepoint site
This worked back in December of 2020

The only mention of ContentSource/Provenance in the MS Docs mentions that ContentSource is only relevant when we're searching for externalItems (which we're not).

I'm sending this as my POST body (with <host> and <site-name> replaced with our info)
I've tried with and without the path value in the queryString (tried with just "a"), same results

{
    "requests": [
        {
            "entityTypes": [
                "listItem"
            ],
            "query": {
                "queryString": "a path:\"https://<host>/sites/<site-name>\""
            },
            "fields": [
                "Title",
                "Description",
                "Answer",
                "listId",
                "listItemId"
            ]
        }
    ]
}

Response: 500

{
    "error": {
        "code": "System.NotSupportedException",
        "message": "\r\n Provenance None is not supported for conversion to ContentSource",
        "innerError": {
            "date": "2021-03-15T18:21:00",
            "request-id": "22f77433-3f9e-441f-bccb-d362c7540f76",
            "client-request-id": "22f77433-3f9e-441f-bccb-d362c7540f76"
        }
    }
}

Answer 1

Hi @Lukas Anderson ,

I tested /search/query in Graph Explorer and it's working as expected per the test result:

Can you please try again later to see if it works ? Feel free to post update.

If the issue still exists in your side, then the issue is possibly related to the Service Incident in Microsoft 365: https://status.office365.com/
You may check the service health status of your tenant via: https://portal.office.com/adminportal/home#/servicehealth

Microsoft is working on this issue actively, and we will be getting back to you as soon as the issue is resolved.

Thanks
Best Regards

---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Unfortunately it's still happening after that incident
I've added more context (perhaps we're missing some header?) & the request IDs
I get the same behavior with and without the path value in the queryString

Answer 3

I get the same response in Graph Explorer